Windows 10 Fix for TM HOTAS WARTHOG disconnect when in COD.
Using USBDeview Program: identifies USB ports.
http://www.nirsoft.net/
ID's are as follows.
TM HOTAS WARTHOG connected directly to USB 2.0 Ports.
Address:
Joystick: Port_#0003.Hub_#0006
Throttle: Port_#0004.Hub_#0006
Your port assignments will probably differ.
Using TM TARGET software ports are "logically" changed to . . .
Address:
Joystick: Port_#0007.Hub_#0003
Throttle: Port_#0008.Hub_#0003
Your port assignments will probably differ.
Under Device Manager - a new category Thrustmaster Devices is created when TM TARGET software is started showing the above change in port numbers.
I had previously gone through all my physical port settings to ensure that the box "Allow the computer to turn off this device to save power." was unchecked.
However, my HOTAS would still disconnect at irregular intervals. In actuality, it was disconnecting from the "logical" ports #0007 and #0008 and reverting back to "native" port ID of #0004 and #0003 and therefore as this was happening within COD during flight, the SIM did not recognize the new settings and all controls froze.
The FIX:
In the Device Manager:
After making sure that all the ports under Universal Serial Bus Controllers have the box for allowing the computer to turn off the device UNCHECKED - load the Target software and still in the Device Manager go to Thrustmaster Devices and UNCHECK ALL THE BOXES thereby preventing the computer from turning off the device.
So far so good.
NOTE: When turning off the TARGET software the ports also revert from the logical 0007/8 back to 0003/4 (DX direct connect)
Summary, make sure that the USB ports under Universal Serial Bus controllers AND under Thrustmaster Devices are UNCHECKED to prevent the computer from turning them off.
This may also be an issue for other Manufacturers' devices.
Bookmarks