Hi there.

I'm using a T.16000M joystick and it works perfectly in its normal mode.
But I'm facing a problem when loading a script configuration in Target.

What is happening is that sometimes (most of the times actually) it takes a little bit more to load the script, just a few seconds more, then when I check the Windows game controllers status I see

T.16000M, OK
Thrustmaster Combined, OK

The Target device analyzer also shows the 2 joystick active...

What is happening is that for whatever reason Windows is "not hiding" the T.16000M by keeping the Thrustmaster Combined virtual joystick only.
And on the Windows device settings page I see T.16000M Setup Incomplete. Restart Device.
This is very annoying because the physical joystick is still sending direct X input to programs, like Discoord for instance, it reads an input defined from the virtual joystick script + a DX input from the T.16000M in normal mode... When I restart it then it loads correctly and only the Thrustmaster Combined virtual joystick is active.

I'm using the latest 2018_FFD.exe drivers, and Target_v3018(328V2).exe software and I'm on Windows 10.
I don't really know when it started to act like this... any ideas of what might be causing this issue?

Thanks in advance.

I have seen several people report issues like this with TARGET over the years. I don't think there is any one solution to solve it except to completely remove and re-install TARGET and the drivers for your controllers. At least I have seen some people say they did that and the problem went away, but I'm not sure.

I tried to remove, re-install, use different USB ports, etc., but no luck...

The facts are these:

1) This is not a consistent behavior, I mean sometimes it just works as it should
2) When the problem occurs there are two "annoying ways" ways to solve it:
2.a) I unplug and re-plug the stick, this solves it 100% of times
2.b) Reboot the PC, most of the times it works, but not always, sometimes I need to reboot it twice

I tried this software USBDeview to make solution 2.a) simpler by running a bat file but it doesn't work; I have to physically connect and disconnect the stick.

Thrustmaster support says I should try it in another PC with USB 2.0 ports (mine are 3.0 and 3.1 but they were supposed to be backward compatible...)

I guess I have to live with it for the time being...

In case someone else is facing this kind of problem, I'm to inform that since I got TARGET to load upon Windows startup, I never faced the problem again.
This leads me to think that the issue might be caused by the loading order of the drivers. There might be some conflict with another device which I couldn't trace, but by loading TARGET automatically upon startup seems to get it to load properly at all times. Thrustmaster support suggested I should reinstall the OS. No way! Thanks to Drakoz and all involved in the development of a sigle script/multi profile solution, which was what actually made me set up Target to run upon windows start, now I have Target running smoothly all time, no issues. Thank you.

I have this issue with the Warthog. Unpluging and replugging my devices after reboot sets me good to go.

True, but after some time of unplugging and replugging your precious device and you start feeling the socket is not so tight as it used to be, you start questioning yourself why do I have to do this... try loading it on start up and see how your life change

I have now implemented this, it works... sort of... well it works but it's not bullet proof. Yesterday restarted my PC several times, would not work. Today is working again...

Do you happen to use TeamSpeak? I read something regarding a conflict between Target and TeamSpeak...

Anyway, try this:

Navigate to /Thrustmaster/TARGET/x64 and find the DeviceManagementApp and delet… no, just rename it to Old_DeviceManagementApp or something else and then try to run target.

The original discussion came from here:
https://forum.teamspeak.com/threads...master-Target-to-Bug?p=443627#post443627

If it doesn't solve your problem or you get some side effects, go back and rename DeviceManagementApp to its original filename.
One thing I noticed is that if I try to load a target script when TS is running, it takes much more time, and the problem described at the first post on this thread happens (in my case, there will still be a T16000 together with the Thrustmaster Combined joystick, thus sending double inputs - the DX one plus the scripted one).

When I tried this "fix", Target always starts normally even if TS is running, and everything is fine, except that TS doesn't recognize Direct X input from the device, but if your keybindings are mapped to keyboard keys, the problem is solved.

Give it a try.