Incompatibility Thrustmaster TARGET Virtual Game Controller

[em4joshua]

Hello everyone,

 

I have been looking into an FSSB for years and finally Santa gave me an FSSB R3 Lighting (serial #216, Job #214) for Christmas. At my suggestion, Santa also brought a friend of mine an FSSB R3 Lighting (serial #221, Job #214). We are both running Windows 10 64 bit (latest version), Thrustmaster TAREGET Software v3.0.18.328 v2 (see link below), we are both using MJF_FW_2_00_2 as the devices were shipped with. We both installed the Thrustmaster HOTAS Warthog OEM PCB so we can use the TAEGET Software. I have to use TARGET as I am in charge of building profiles for our very large group.

 

In the "Game Controllers" both of ours Warthogs show up as "Joystick - HOTAS Warthog," "Throttle - HOTAS Warthog." When we run the TARGET profile in the TARGET software (you can download from link below), they change in the "Game Controllers" to "Thrustmaster Virtual Game Controller (root)."

 

Initially, when we run the "Event Tester" in the TARGET Software, the throttle inputs show as mapped, but as soon as you touch the throttle, the stick stops working. For whatever reason on my PC, I initially could reproduce the error this way, but after some uninstalls and reinstalls of the TARGET Software, I now can use throttle inputs in the "Event Tester", but as soon as I open the "Game Controllers" my stick stops working. This also happens if I run DCS, or likely anything that interacts with the inputs.

 

I can get the stick input to work again by unplugging the stick from my computer USB slot and then plugging it back it, but as soon as I open "Game Controllers" or DCS, the stick stops working.

 

I even tried making a new TARGET profile with just one button programmed to the throttle and one button programmed to the stick and the same issue occurred.

 

I love the feel of the FSSB, but I can't use it if we can't use the TARGET Software, and it was my understanding from reading the the website that the FSSB was compatible with the Thrustmaster TARGET Software.

 

None of the above problems occurred until I installed the FSSB.

 

Please help,

Joshua

 

Link to the TARGET Profile I am using (https://drive.google.com/open?id=1S389e ... sjOg1Ks9kB)

 

TARGET Software

http://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/TARGET_v3018(328v2).exe

 

http://www.realsimulator.com/html/fssb_r3_lighting.html

Edited December 31, 2019 by em4joshua

[guod]

Had the same problems. My solution was setting the multiple "EnhancedPowerManagementEnabled" Dword's within Regedit.

 

Here's the reference thread that helped me. Note especially the post by "the100thmonkey".

 

https://forums.frontier.co.uk/threads/thrustmaster-t16000m-fcs-hardware-problems.421485/

 

Reference screenshot back when I was sawing away at it.

 

https://www.dropbox.com/s/zpp810fsonfv0vx/device.jpg

Edited December 31, 2019 by guod

[em4joshua]

Had the same problems. My solution was setting the multiple "EnhancedPowerManagementEnabled" Dword's with Regedit.

 

Here's the reference thread that helped me. Note especially the post by "the100thmonkey".

 

https://forums.frontier.co.uk/threads/thrustmaster-t16000m-fcs-hardware-problems.421485/

 

Reference screenshot back when was sawing away at it....

 

https://www.dropbox.com/s/zpp810fsonfv0vx/device.jpg

 

Thank you and I will try it.

[em4joshua]

Had the same problems. My solution was setting the multiple "EnhancedPowerManagementEnabled" Dword's within Regedit.

 

Here's the reference thread that helped me. Note especially the post by "the100thmonkey".

 

https://forums.frontier.co.uk/threads/thrustmaster-t16000m-fcs-hardware-problems.421485/

 

Reference screenshot back when I was sawing away at it.

 

https://www.dropbox.com/s/zpp810fsonfv0vx/device.jpg

 

That did it! THANK YOU!

 

I am always appreciative of how cooperative the community is.