Thrustmaster TARGET Script Editor users:
I have been frustrated by the way TM Script Editor builds the "Thrustmaster Combined" device in the Windows 10 "Game Controllers" window. Sometimes it would remove the "Joystick - HOTAS Warthog" controller, and/or sometimes remove the "Throttle - HOTAS Warthog" controller when it installed the "Thrustmaster Combined" controller as I ran a TARGET Script. Sometimes TARGET built the "Combined" controller without removing anything like it should.
Furthermore, it has been taking too long to run the script before using the system. It should compile and run a script in about 3 seconds instead of this long loadup I was experiencing.
I used to work around this by implementing the "Thrustmaster Firmware Updater (3.0.33), but even that stopped correcting the problem with recent driver and Windows 10 updates. Since Firmware Updater used to work, I tried playing with it and found, quite by accident, what seems to fix the problem:
When the Thrustmaster Firmware Updater (3.0.33) appears, there are two controllers presented for updating: "Joystick - HOTAS Warthog - VER.: 12" at the top, and "Throttle - HOTAS Warthog - Ver.: 23" underneath it. Instinctively, I've updated the top option first, then the Throttle option second. This order seems to be the problem.
I simply reversed the order and updated the "Throttle - HOTAS Warthog - Ver.: 23" FIRST, and the "Joystick - HOTAS Warthog" SECOND. After closing the updater, the script compiled instantly with all the appropriate bells and whistles, and the Windows 10 "Game Controllers" window shows "Thrustmaster Combined" all by itself, like it's supposed to!
Success! (I just hope it continues to work!)
Bookmarks