Hardware & Technical Thurstmaster TARGET Software Issue

Hi All,

I could swear there used to be a hardware sub-forum but I can't find it - if I've missed it feel free move this there.

I have a weird issue with the target software for my warthog. It runs absolutely fine but recently when you stop the script running the software hangs and has to be manually shut down though the task manager. After this if I shut the PC down the PC also hangs, the OS turns off but the PC fans keep going until I hard power off using the button on the top.

A friend of mine with a similar setup is reporting the exact same issue.

We're both running Windows 10.

Has anyone else got this issue, and if so have you managed to fix it? I have tried the standard fixes - clean re-install of latest drivers and software, run as admin etc. I'm completely stumped - even google is not my friend!

Thanks in advance.
 
I haven't experienced this specific issue using Win 10 and TARGET, however I had problems in ED after stopping the script and restarting it. Turned out Win 10 has problems unregistering the 'native' Warthog devices and the system was suffering USB port conflicts due to that.

You could try running joy.cpl and see if there are multiple devices displayed. When the script is running, only the Thrustmaster virtual game controller should show. If the throttle and/or stick appear as separate devices, your problem might be related to above issue.
 
Thanks guys.

KIRK I think you may be right. When the script stops it hangs after giving 2 of the devices back to windows, but without giving the 3rd. How did you resolve the conflict?
 
Thanks guys.

KIRK I think you may be right. When the script stops it hangs after giving 2 of the devices back to windows, but without giving the 3rd. How did you resolve the conflict?

Just to be clear: Stopping the script should give two devices back to windows (throttle and stick), whilst removing the third (Thrustmaster virtual game controller). I had a slightly different problem and I resolved it by just starting the script once and letting it run for as long as the PC is up. When I need to restart the script, I also have to reboot the PC. Not an elegant solution, but it works for me.

Maybe you'll find something here: http://theairtacticalassaultgroup.com/forum/showthread.php?t=18557
 
Thanks again all.

I never actually fixed this (though for reference when i referred to 3 devices I also have a set of pedals). I Still think the issue was related to USB allocation to windows. For a while I used the same work around as Kirk, but when I started modifying the script it became cumbersome.

However before I could investigate further my copy of windows decided to top allowing me to sign into my user account - effectively locking me out and denying me access to all of my files. There are a few fixes for this on line, none of which worked for me so I ended up re installing Windows from scratch.

Up side - the Thrustmaster stuff now works perfectly again!
 
Back
Top Bottom