Thrustmaster Warthog combined joystick problem

[MadMonty]

Gents,

 

out of nowhere I ran into the following problem...

 

When using TM Warthog joystick and throttle without running a TARGET-profile, I used to have a separate joystick and a separate throttle in DCS.

 

When using TM Warthog joystick and throttle running a TARGET-profile, I used to have a combined controller in DCS.

 

But now, when I run my TARGET-profile, I have my combined controller plus a separate joystick and a separate throttle in DCS.

 

So most of the axes and buttons are occupied twice. E.g. pressing the autopilot button resolves in a key-command by the combined controller and a DX-command by the separate throttle.

 

I could delete all buttons and axes of the separate controllers in DCS, but that is not how it meant to be.

 

Any ideas?

 

I already reinstalled TARGET-software. Firmware is up to date...

 

Cheers,

 

Monty

[MadMonty]

OK, life is so simple.

 

Plugging the controllers out and in again, resolved the problem... Have done that before, so don´t ask what happened :doh:

 

 

EDIT: Problem is coming back, I have to unplug and replug the controllers... Any ideas why?

Edited February 3, 2017 by MadMonty

[Home Fries]

Thrustmaster makes great hardware and TARGET is great, but the FAST service that Thrustmaster uses as the device middleware (for TARGET) is unstable garbage. Many times, I find that simply rebooting the computer clears all of the crud that destabilizes FAST after a while (especially when starting and stopping TARGET profiles).

 

I'm not sure if the FAST service is responsible for the issues you're having, but it wouldn't surprise me at all.

Edited February 3, 2017 by Home Fries

[Thadiun Okona]

Do you have win10? If so, your os is most likely doing you the delightful favor of powering down usb devices it thinks you are not using via the USB Power Management system. There's a way to disable this 'feature', solution 2 here:

 

https://www.drivereasy.com/knowledge/fix-issue-after-upgrade-system-to-windows-10-usb-ports-dont-work/

[B2Blain]

I was able to isolate the problem to the rudders - by deleting the profile. I may have solved it by increasing the dead zone by a little more and that seemed to solve the issue. I still need to do a more thorough test.

 

Thanks for everyone's suggestions!

[MadMonty]

Do you have win10? If so, your os is most likely doing you the delightful favor of powering down usb devices it thinks you are not using via the USB Power Management system. There's a way to disable this 'feature', solution 2 here:

 

https://www.drivereasy.com/knowledge/fix-issue-after-upgrade-system-to-windows-10-usb-ports-dont-work/

 

Thanks for your help, but that made no difference to my problem. I am just wondering, since it came out of nowhere... It even makes no difference after a reboot and a first profile loading via Target...

[Thermal]

Gents,

 

But now, when I run my TARGET-profile, I have my combined controller plus a separate joystick and a separate throttle in DCS.

 

 

Do you have any "mode" commands in your profile?

 

Like this?

// Configure(&Joystick,MODE_FILTERED); // Filtered, can disable original in int EventHandle()

 

Does the issue happen with a plain, simple .tmc file running in the script editor?

[Rangoon]

Has anyone determined a solution for this? I am getting same symptoms. In Windows 10 "Game Controllers" I see both the "Thrustmaster Combined" controller and each individual controller ("F16 MFD 1" "F16 MFD 2" "Throttle - HOTAS Warthog" "Joystick - HOTAS Warthog"). This is after running a profile in the script editor. Prior to running the script I see only the discrete controllers. Of course in DCS, then, I see the same situation.

[txmtb]

Been seeing the same thing recently. Figuring it must be a windows update that caused it to start happening.

Also noticed a significant delay executing the script now as compared to before.

Edited October 12, 2017 by txmtb

[laumaya]

Been seeing the same thing recently. Figuring it must be a windows update that caused it to start happening.

Also noticed a significant delay executing the script now as compared to before.

 

I have the same problem.

[Pizzicato]

I have the same problem.

 

I'm suddenly having the exact same problem. Just suddenly started today. :no_sad:

[DD_Crash]

When you load a profile check the joystick controller tab at the bottom right to see the joysticks windows sees, if it shows Thrustmaster Combined and separate sticks then stop the profile and restart it (you might have to do it a couple of times)

[Pizzicato]

When you load a profile check the joystick controller tab at the bottom right to see the joysticks windows sees, if it shows Thrustmaster Combined and separate sticks then stop the profile and restart it (you might have to do it a couple of times)

 

Thanks for the tip, Crash. I’ll give that a go tonight and report back.

[PeaceSells]

I'm having the same problem, only I use the T16000M HOTAS intead of the Warthog. It happens all the time if I have Teamspeak on while I load a profile. Without Teamspeak it also happens, but not 100% of the time. Sometimes I can get rid of it by closing all programs, disconnecting and connecting the HOTAS, then opening TARGET again and loading the profile again. Sometimes I can't. I have no idea what's going on, I didn't have this issue before.

[Flow]

Bumping this thread. I have the same issue.

Every now & then, when I start my profile, I have the Thrustmaster combined input, and the stick & throttle still there too.

This is creating issues inside DCS.

Is there any solution that has been found ? I've been looking all over, but nothing was really conclusive.

I updated TARGET, made sure that windows cannot put the USB devices to sleep.

 

Help is appreciated :)

[SnapRoll]

I had the same problem since the Win10 Creators update got installed and then Thrustmasters DeviceManagementApp.exe had a problem with some Windows program.

 

The thing is I can’t quite remember but I now found this far back in my Windows System Log.

 

The application \Device\HarddiskVolume4\Program Files\WindowsApps\Microsoft.WindowsStore_...\WinStore.App.exe with process id 12220 stopped the removal or ejection for the device USB\VID_044F&PID_0404\00000040.

 

I think this is what it was, and since I removed the WinStoreApp I hand no more problems.

 

Check in your Windows log first…

[DD_Crash]

How did you remove the WinStoreApp ?

[Flow]

I kind of solved the issue by preventing all the Thrustmaster USB controllers to go to sleep.

Since that the issue seems gone

[Curly]

I had a similar issue, I found a solution on the BMS forums. I'll paste it here since you have to register to view their boards.

 

Issue:

The Teamspeak Joystick and Gamepad Addon prevents Thrustmaster's target software from working properly. The teamspeak addon prevents target from hiding the physical devices from windows, thus preventing target to function properly, even after Teamspeak is closed.

 

Solutions:

1, By removing the Gamepad / Joystick addon from teamspeak target works properly. 2, Hard reboot the system start target and run your profile before opening teamspeak. Both solutions have been tested effective on the latest version of target across multiple systems.

 

Background

Thurstmaster Target Principles of Operation: Target functions by creating a virtual control and hiding the physical devices (joysticks) from the system. This allows the user to program the joystick to any number of virtual functions, keyboard commands, axis modification, ect.

 

Since the Teamspeak Joystick and Game Pad addon prevents windows from hiding the physical devices, a profile will not work properly. You end up with phantom joystick buttons, ect. It fundamentally breaks target. The problem continues even when Teamspeak is closed. I don't think the joystick addon ever fully shuts itself down when target is closed. Disabling the addon doesn't seem to help either.

 

The problems began to appear a few patches ago when the addon was bundled with the basic install. It got worse with the latest release.

 

How to delete the Teamspeak Joystick Addon

Open Teamspeak, select tools->Options->addons (it's on the left sidebar), Select the Joystick and Game Pad addon and delete it. Restart teamspeak and run your profile.

 

If you need target and joystick push to talk, I would recommend Discord, it functions flawlessly with target.

[PeaceSells]

^^ That explains why I had so much problems with TARGET when I was using Teamspeak. It started when I started using the push-to-talk button in Teamspeak and never ended anymore. Nowadays I just don't use Teamspeak.

 

I guess TARGET doesn't really do a good job at hidding the controllers in Windows, does it?

[Thinder]

I have the same problem.

 

Same here. I only started to use my T16000 HOTAS combo yesterday and so far it's been a nightmare, to the point where the Stick is not even appearing in the event tester and device analyzer.

 

Windows starts related services just fine, it's just that it is Thrustmaster FAST service is not detected by the package, I don't use Teamspeak yet.

 

I have written a ticket to Thrustmaster support with a little detail: I had Error Code 0x000000E7 saying that Thrustmaster FAST service didn't start, when in fact it had and was running properly, I can't expect a reply before 15 days max du to the pandemic I'll keep you posted...

 

If there is an alternative way to set up this OTAS I'll use it.

Edited May 30, 2020 by Thinder

[Ant0ine]

If there is an alternative way to set up this OTAS I'll use it.

 

Vjoy+Joystick Gremlin.

[Thinder]

Vjoy+Joystick Gremlin.

 

Yeah, thanks!

 

I figured it out and have tested it in Strike fighter, it works just fine!

 

I didn't install Joystick Gremlin and I'm not sure it is needed, also, I used Strike Fighters 2 as Benchmark simply because I didn't finish to upgrade my PC, I received my new graphic card but there is no cable for it and I'm waiting for one to be delivered.

 

 

Once everything is running perfectly I'll be able to start DCS without crashing out, which is caused by my actual graphic card.

Edited May 30, 2020 by Thinder

[=Panther=]

This thread may help those with the combined controllers and or the long delay.

 

https://forums.eagle.ru/showthread.php?t=232737

 

In short Microsoft Windows Store is a culprit most of the time. There are a few ways to handle the store, depending on what you want to accomplish e.g. uninstall, kill it until restart, etc.

[dailey123]

Same here always had to do the plugging and unplugging part to get T.A.R.G.E.T scripts to run.

Or it wont see all the devices and wont run at all and is stuck in a loop it sucks xD.