TARGET .tmc scripts not working after Windows reinstall

[moggel]

I had to do a clean Windows reinstall to resolve an other matter. I saved the .tmc scripts, of course (a lot of hours have gone into that).
But after the ireinstall, the Thrustmaster driver and then TARGET sowftare installation, when I run the .tmc the script fails with this output:

 

Running script: D:\Thrustmaster Warthog\DCS\Warthog f-16c\DCS F-16C.tmc
*** Allocated ProcInstances found from the previous run: use FreeProcInstance() *** 
Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"
Compile Succeeded.
Physical USB HID devices managed by script!
Currently plugged USB HID devices[5]:
1: "TPR T.Pendular Rudder" - "USB\VID_044F&PID_B68F&REV_0110"
2: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
3: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100"
4: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100"
5: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\5&153678D8&0&11) selected
USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\5&153678D8&0&12) selected
USB HID device with hardware id "VID_044F&PID_0403" cannot be found
USB HID device "F16 MFD 1"(USB\VID_044F&PID_B351\6&15B8B68D&0&2) selected
USB HID device "F16 MFD 2"(USB\VID_044F&PID_B352\6&15B8B68D&0&3) selected
USB HID device with hardware id "VID_044F&PID_0400" cannot be found
USB HID device with hardware id "VID_044F&PID_B10A" cannot be found
USB HID device with hardware id "VID_044F&PID_B10B" cannot be found
USB HID device with hardware id "VID_044F&PID_B687" cannot be found
USB HID device with hardware id "VID_044F&PID_B679" cannot be found
USB HID device with hardware id "VID_044F&PID_0405" cannot be found
USB HID device with hardware id "VID_044F&PID_0406" cannot be found
USB HID device with hardware id "VID_044F&PID_0407" cannot be found
USB HID device with hardware id "VID_044F&PID_0408" cannot be found
USB HID device with hardware id "VID_044F&PID_040A" cannot be found
USB HID device with hardware id "VID_044F&PID_040B" cannot be found
USB HID device with hardware id "VID_044F&PID_0409" cannot be found
Virtual HID devices managed by script!
Connecting virtual joystick...Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard...Done
Connecting virtual mouse (absolute axes)...Done

main returned 0
Error:One of the selected USB devices (2) has been unplugged. Aborting script!
Aborting script (check output above for reason)...
Script stopped!

Any idea what's causing it, and how to fix it?

[Lange_666]

Maybe of any help:

https://www.reddit.com/r/hotas/comments/7lybgv/a_solution_to_thrustmaster_target_software_on_the/

https://www.reddit.com/r/hotas/comments/bf62bp/target_software_help_t1600m_hotas/

 

[moggel]

9 hours ago, Lange_666 said:

Maybe of any help:

https://www.reddit.com/r/hotas/comments/7lybgv/a_solution_to_thrustmaster_target_software_on_the/

https://www.reddit.com/r/hotas/comments/bf62bp/target_software_help_t1600m_hotas/

 

- Tried setting all '1' to '0', in USB registry, as per instruction0
- Remove TARGET and TM drivers, then rebooted
- Installed TM divers
- Unplugged TM devices
- Installed TARGET, then rebooted

Still get the issue

If I unplug the MFDs it seems to work

Tried commenting out the MFD mapping in script and rerun TARGET (with MFDs plugged) but still get the issue

Tried starting a new empty script. Still get the issue

So: I can't use TARGET with MFDs plugged in, for some weird reason

Edited April 3, 2023 by moggel

[Lange_666]

On my previous Intel motherboard I had problems with my VR headset being recognized when plugged into USB.
With my current AMD X570 motherboard i still have to see the first disconnect of VR headset but i had the same problem with the Warthog when running a script.
It would sometimes trow back the same error as you get: One of the selected USB devices has been unplugged.
When it happened it always happened when running MSFS and always at the same point in the loading process.
Looked at various solutions, none of which worked until i plugged both stick and throttle USB's to a USB-C splitter cable and then into my only USB-C port. Since then i didn't had any unplug message.

What bugs me a little is that load of USB HID Device with hardware id xxxxxxx cannot be found messages. These are all each different devices.
I don't have that, i only see devices that are recognized by Target.

[BitMaster]

Nirsoft's usbdeview can help you sort out USB devices, also delete them, even ones not currently connected.

If you really want to clear them all out, this is what you need.

[moggel]

It was me misunderstanding Thrustmaster's docs, it seems. I mistakenly assumed that the driver package I downloaded would cover all detected Thrustmaster devices but, apparently, it did not. It only supported the Warthog HOTAS and TPRs, not the Cougar MFDs. I ended up uninstalling TARGET, then all Thrustmaster drivers and started over. After having installed the HOTAS drivers and then the Cougar drivers I unplugged everything and installed TARGET. A reboot, all devices plugged in, and now it works fine.

So, the usual combination of user not reading up carefully and really really louse error messaging. As always.

Also, I have to say that even though I really love Thrustmaster's hardware it really isn't very Plug'N'Play.

Thanks for trying to help out guys!

Edited April 4, 2023 by moggel