Hotas warthog Stick win USB aleatory disconection problem. What I can do?

[Silver_]

I'm trying to find a solution both at the hardware and software level but I can't find it. I have changed from USB 2.0 to 3.0, I have updated the firmware to the latest version (12), I have connected the Stick to a USB hub and I still get absolutely nothing. Sometimes I have had the feeling that the TARGET application, when I load a script in my startup, blocks my controller.

The symptoms presented are that of a dead stick, the USB controller is detected by Windows but neither the axis nor the buttons respond, they are frozen. I take out and insert the USB and it comes to life again. I have read a lot of posts with similar things but none of them clarify a valid method for this problem.

I have also heard of static problems, I am electronic and I could solve it somehow but I don't think this is my problem. Does anyone have any effective solution for this? (downgrade firmware, need electronic mod, software problem)

I'm tired of taking the USB in and out so much, I hope someone can enlighten me with something good. Thanks for reading me.

Note: I have Win11 64 bit (could this be the problem )

Edited December 7, 2023 by Silver_

[Silver_]

Checking the output log of the target when I load a script I have seen that there are several entries that are not found, but the only thing I have is the warthog stick, I have nothing else.

 

Could this be my problem?

 

Running script: C:\Users\Silver\AppData\Roaming\Thrustmaster\TARGET\Scripts\DCS_Warhog.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[3]:
1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
2: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100"
3: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100"
USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\8&2EFE0359&0&5) selected
USB HID device with hardware id "VID_044F&PID_0412" cannot be found
USB HID device with hardware id "VID_044F&PID_0413" cannot be found
USB HID device with hardware id "VID_044F&PID_040E" cannot be found
USB HID device with hardware id "VID_044F&PID_040F" cannot be found
USB HID device with hardware id "VID_044F&PID_0416" cannot be found
USB HID device with hardware id "VID_044F&PID_0417" 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
Script stopped!

[Silver_]

 

In the virtual game controller appear more buttons than my hotas stick  has, is this normal?

[Lange_666]

7 hours ago, Silver_ said:

USB HID device with hardware id "VID_044F&PID_0412" cannot be found
USB HID device with hardware id "VID_044F&PID_0413" cannot be found
USB HID device with hardware id "VID_044F&PID_040E" cannot be found
USB HID device with hardware id "VID_044F&PID_040F" cannot be found
USB HID device with hardware id "VID_044F&PID_0416" cannot be found
USB HID device with hardware id "VID_044F&PID_0417" cannot be found

This is not your problem.
When "non existent devices" are commented out in the script (with // in front of the Configure statement), these messages appear.

6 hours ago, Silver_ said:

In the virtual game controller appear more buttons than my hotas stick  has, is this normal?

If you did run a script then that is normal because it will combine all Thrustmaster controllers you have (stick + 2 MFD's) into 1 controller (as a device Thrustmaster Combined) and this will add up the buttons up to 32 max (32 is limited by Windows for one controller if i'm correct).

[Silver_]

22 minutes ago, Lange_666 said:

If you did run a script then that is normal because it will combine all Thrustmaster controllers you have (stick + 2 MFD's) into 1 controller (as a device Thrustmaster Combined) and this will add up the buttons up to 32 max (32 is limited by Windows for one controller if i'm correct).

I have excluded the two MFDs in the script, so many buttons should not appear, right?

[Lange_666]

Looking at your compiler info they are not excluded hence the USB HID device cannot be found messages.

[Silver_]

I have finally managed to ensure that no "cannot be found" devices appear, I have been excluding them in the script with commands but I was missing the logical names of the devices. I got these names from the list that appears in the taget.tmh file. After a long search I found this file, I couldn't get this information from where I should have gotten it, in the manual, but I finally found it. Everything is fatally explained. This is not like Foxy of Hotas Cougar, it is more designed for programmers than for users.

I also found the problem, or at least, let's put it that way, what causes the problem. I asked Thrustmaster technical support but they didn't give me a solution, they just confused me more with stupid questions. I not get interest about them.

Apparently, for some reason, when booting into Windows 11 with the task scheduler set to autoload a configuration script at startup ("C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETGUI.exe" -r "C:\Users\XXXX\AppData\Roaming\Thrustmaster\TARGET\Scripts\DCS_Warhog.tmc") this one sometimes loads and most of the time it doesn't load, leaving the flight stick hanging. It's like the stick responds late and Windows 11 rejects it, it may be the whole problem with Windows 11 and not with Thrustmaster , the fact is that neither of them give me solutions. Ah, it's not enough to set it with administrator rights, it does exactly the same whether it's set or not, at least in my case.

Anyway, if anyone has a solution for this, I would appreciate it.

Edited December 25, 2023 by Silver_

[Lange_666]

2 hours ago, Silver_ said:

This is not like Foxy of Hotas Cougar, it is more designed for programmers than for users.

Not really, there is an empty template.tmc (one with and without MFD's) delivered with the TARGET software.
At first i thought: that's not my cup of tea, but after digging a bit into it with the manual open on my second monitor it became clear how to use the MAPKEY and other functions.
In the empty template.tmc all the basic stuff is already written out and commented out so all you have to do is remove the comments for the button you want and fill in the statements you need. All is step by step explained in the manual. The more programmer you are, the more complex stuff you can write but you don't need to be one to use it.

 

2 hours ago, Silver_ said:

Apparently, for some reason, when booting into Windows 11 with the task scheduler set to autoload a configuration script at startup ("C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETGUI.exe" -r "C:\Users\XXXX\AppData\Roaming\Thrustmaster\TARGET\Scripts\DCS_Warhog.tmc") this one sometimes loads and most of the time it doesn't load, leaving the flight stick hanging. It's like the stick responds late and Windows 11 rejects it, it may be the whole problem with Windows 11 and not with Thrustmaster , the fact is that neither of them give me solutions. Ah, it's not enough to set it with administrator rights, it does exactly the same whether it's set or not, at least in my case.

Anyway, if anyone has a solution for this, I would appreciate it.

Don't know why it sometimes works and sometimes doesn't but why would you load a script at startup of your PC besides the fact that's its automated (if it works).
If it doesn't work all the time why getting frustrated by being stubborn and keep doing it each time if it doesn't work 9 out of 10?
I just load up Target just before i launch DCS, select a script for the plane i want to fly and run it. Takes just a few seconds extra. And if i don't fly, nothing gets loaded either (keeps the memory clean and the CPU doesn't need to work to keep it running in the background for nothing).
Tip: You can use SkateZilla's Updater/Launcher to start the stuff you want and then start DCS all from within the same app. Nothing more easier then that.

[Silver_]

3 hours ago, Lange_666 said:

Tip: You can use SkateZilla's Updater/Launcher to start the stuff you want and then start DCS all from within the same app. Nothing more easier then that.

I think in the end it will be the option I will take. In any case, this afternoon while testing I realized that it not only fails at startup but also when I run it at any time manually.

Maybe a virtual device problem with windows 11

Edited December 25, 2023 by Silver_