Forum Discussion

5 years ago

Solved

Using Thrustmaster TARGET to fix the Thrustmaster HOTAS deadzone issues

You will have to add this into a script for the TARGET Script Editor: MapAxis ( &Joystick, JOYX, DX_XROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE); MapAxis ...

Opiate987
5 years ago
Okay I managed to solve this with a similar, simpler solution, using the TARGET GUI.

1. I followed the instructions at the bottom of this thread to ensure my HOTAS drivers and TARGET were installed correctly (requires plugging and unplugging devices as you go): https://forums.eagle.ru/showthread.php?t=269051

2. After installing TARGET, I opened the TARGET GUI and created a New Configuration. On the next page I selected just my stick (T16000M), not my throttle. Then I left the axes mappings as default. I actually Changed the CURVE to -4 for the X and Y axes just to make sure there was no deadzone in game. On the final page you can save the profile but before you do so, you can take a look at the script it generates which contains the same lines of codes you've shared. Hit Run Configuration and TARGET should reassign your stick to be a Thrustmaster Virtual Game Controller. You can check this by opening up the Joystick Control Panel from the new window that has opened after running the configuration.
3. Now I ran into some problems with getting the T16000 to stay connected via the TARGET virtual game controller, with the stick falling asleep. However just to test that the above worked I managed to keep the connection alive by keeping the stick in motion as I hit the Run Configuration button, then checked the properties of the Thrustmater Virtual Game Controller inside the Joystick Control Panel (which is just a shortcut to the the windows Game Controllers panel) and could see input for the X and Y axes in the test tab.

4. Finally I booted up squadrons (also keeping the stick in motion) and with some luck managed to set the Joystick 1 device at the end of the controller settings to Thrustmaster Virtual Game Controller. E voila! in game I was able to move the cockpit's crosshairs with even the slightest movements from the stick and no deadzone!
With regards to the issues in step 3, I found some articles about turning off the power saving features for the T16000 in Windows registry, device manager and Windows power saver menu.

Opiate987

5 years ago

Okay I managed to solve this with a similar, simpler solution, using the TARGET GUI.

1. I followed the instructions at the bottom of this thread to ensure my HOTAS drivers and TARGET were installed correctly (requires plugging and unplugging devices as you go): https://forums.eagle.ru/showthread.php?t=269051

2. After installing TARGET, I opened the TARGET GUI and created a New Configuration. On the next page I selected just my stick (T16000M), not my throttle. Then I left the axes mappings as default. I actually Changed the CURVE to -4 for the X and Y axes just to make sure there was no deadzone in game. On the final page you can save the profile but before you do so, you can take a look at the script it generates which contains the same lines of codes you've shared. Hit Run Configuration and TARGET should reassign your stick to be a Thrustmaster Virtual Game Controller. You can check this by opening up the Joystick Control Panel from the new window that has opened after running the configuration.

3. Now I ran into some problems with getting the T16000 to stay connected via the TARGET virtual game controller, with the stick falling asleep. However just to test that the above worked I managed to keep the connection alive by keeping the stick in motion as I hit the Run Configuration button, then checked the properties of the Thrustmater Virtual Game Controller inside the Joystick Control Panel (which is just a shortcut to the the windows Game Controllers panel) and could see input for the X and Y axes in the test tab.

4. Finally I booted up squadrons (also keeping the stick in motion) and with some luck managed to set the Joystick 1 device at the end of the controller settings to Thrustmaster Virtual Game Controller. E voila! in game I was able to move the cockpit's crosshairs with even the slightest movements from the stick and no deadzone!

With regards to the issues in step 3, I found some articles about turning off the power saving features for the T16000 in Windows registry, device manager and Windows power saver menu.

Opiate987

5 years ago

I found that the new 1.1 patch has fixed deadzoning issues for me and it's pretty playable without the TARGET software faff in my opinion 🙂