#4506076 - 02/04/20 08:29 AM
Re: Thrustmaster Combined, OK, but the physical joystick is OK too...
[Re: Joao Muas]
|
Joined: May 2001
Posts: 468
Joao Muas
Member
|
Member
Joined: May 2001
Posts: 468
Portugal
|
I tried to remove, re-install, use different USB ports, etc., but no luck...
The facts are these:
1) This is not a consistent behavior, I mean sometimes it just works as it should 2) When the problem occurs there are two "annoying ways" ways to solve it: 2.a) I unplug and re-plug the stick, this solves it 100% of times 2.b) Reboot the PC, most of the times it works, but not always, sometimes I need to reboot it twice
I tried this software USBDeview to make solution 2.a) simpler by running a bat file but it doesn't work; I have to physically connect and disconnect the stick.
Thrustmaster support says I should try it in another PC with USB 2.0 ports (mine are 3.0 and 3.1 but they were supposed to be backward compatible...)
I guess I have to live with it for the time being...
|
|
#4509496 - 03/04/20 07:53 PM
Re: Thrustmaster Combined, OK, but the physical joystick is OK too...
[Re: Joao Muas]
|
Joined: Dec 2006
Posts: 418
SAPPER
Member
|
Member
Joined: Dec 2006
Posts: 418
Portugal
|
I have this issue with the Warthog. Unpluging and replugging my devices after reboot sets me good to go. True, but after some time of unplugging and replugging your precious device and you start feeling the socket is not so tight as it used to be, you start questioning yourself why do I have to do this... try loading it on start up and see how your life change I have now implemented this, it works... sort of... well it works but it's not bullet proof. Yesterday restarted my PC several times, would not work. Today is working again...
|
|
#4510092 - 03/09/20 10:24 AM
Re: Thrustmaster Combined, OK, but the physical joystick is OK too...
[Re: SAPPER]
|
Joined: May 2001
Posts: 468
Joao Muas
Member
|
Member
Joined: May 2001
Posts: 468
Portugal
|
I have now implemented this, it works... sort of... well it works but it's not bullet proof. Yesterday restarted my PC several times, would not work. Today is working again... Do you happen to use TeamSpeak? I read something regarding a conflict between Target and TeamSpeak... Anyway, try this: Navigate to /Thrustmaster/TARGET/x64 and find the DeviceManagementApp and delet… no, just rename it to Old_DeviceManagementApp or something else and then try to run target. The original discussion came from here: https://forum.teamspeak.com/threads...master-Target-to-Bug?p=443627#post443627If it doesn't solve your problem or you get some side effects, go back and rename DeviceManagementApp to its original filename. One thing I noticed is that if I try to load a target script when TS is running, it takes much more time, and the problem described at the first post on this thread happens (in my case, there will still be a T16000 together with the Thrustmaster Combined joystick, thus sending double inputs - the DX one plus the scripted one). When I tried this "fix", Target always starts normally even if TS is running, and everything is fine, except that TS doesn't recognize Direct X input from the device, but if your keybindings are mapped to keyboard keys, the problem is solved. Give it a try.
|
|
|
|
|
|
|
|
|
|
|
|
Exodus
by RedOneAlpha. 04/18/24 05:46 PM
|
|