thrustmaster 16000 joystick yaw axis not responding

[Cleo9]

Hope this is the right place to reports this

 

It looks like since the last update fix, the yaw axis of my Thrustmaster 16000 joystick is not detected by the game... All planes deviate to the right and even at takeoff the rudder is inclined to the right. No way to calibrate this if I go back to the "settings". The yaw axis is just not detected at all... Makes taking off and flying... a bit complicated... To say the least... I'm just a SP player and I don't fly on "expert", I use custom settings, but resorting to "rudder assist" makes things a little too simple... I've had this joystick (no throttle lever/pedals) since last fall, so it's should still be functional. 

 

A few people have reported issues with the thrustmasters since the latest fix. Could this be be one of them ?

 

What can be recommended as an upgrade ( The TM 16000 is not the top of the line, I know). Everything basic included, pedals, etc. Willing to pay 500 CND...

 

 

Edited April 29, 2020 by Beurling

[RhumbaAzul]

Is it detected in Windows USB Game controllers?

Edited April 29, 2020 by RhumbaAzul

[Cleo9]

1 hour ago, RhumbaAzul said:

Is it detected in Windows USB Game controllers?

 

Yes, clearly, this is not an issue. And everything else works fine, except for the yaw axis, as described

[Cleo9]

I've tried other games ; they can detect the twist/yaw axis. So it's not that my joystick itself is broken or something...

Edited May 2, 2020 by Cleo9

[zdog0331]

I have seen this problem being reported by multiple people in the forums.  Something might have broke after the most recent update.  I'm currently about to check my t-16000m and see if i have the same problem.

[Cleo9]

I have found a way to deal partially with the problem : I unplug then plug back my joystick.... or I just start IL-2 1946, verify the integrity of the yaw axis, and then switch to BOS... It works everytime... For a while... Then the problem returns if I leave the game and return to it without taking those preliminary measures. weird....

[=RS=Stix_09]

IMHO the T16000m is a very good stick for the $
 

13 hours ago, Cleo9 said:

I have found a way to deal partially with the problem : I unplug then plug back my joystick.... or I just start IL-2 1946, verify the integrity of the yaw axis, and then switch to BOS... It works everytime... For a while... Then the problem returns if I leave the game and return to it without taking those preliminary measures. weird....

 

For this reason quoted I believe its not issue with IL-2 GB

 

I have the t16000m, I can confirm I do not have this problem with twist rudder being seen in il-2 GB.

(I also have t-rudder pedals, both work, and every axis is detected in game)

Works without any problems. Sounds like a conflict with software problem(possibly hardware conflict also).
 

1)make sure drivers are current for t16000m 

1a)if steam verify game install,

2)test in minimal config, stop all non required programs in windows, unplug all other devices except mouse.

The order devices are connected can effect the joy# assigned to it (see "Game setup and settings FAQ" section 22)
3)test   and that all axis and buttons are working before starting il-2 gb with control panel (if it works here (all axis , inc rudder) it will be seen in game or you have a software conflict somewhere)

4)check this

 

DEVICES.TXT file (how it works:

 

In this game folder "...IL-2 Sturmovik Battle of Stalingrad\data\input" is a file called devices.txt

 

If DEVICES.TXT is not present at game start a new one will generate on game start.

 

The contents look something like this (just an example, yours will be different , but structure is the same)

 

Quote

configId,guid,model |

0,%22465b2200-84c9-11e7-0000545345440180%22,HP%20Deluxe%20Webcam%20KQ246AA|

1,%22fdd5ee90-1417-11e9-0000123456777870%22,T.16000M|

2,%22bc5c1100-b02c-11e8-0000545345440180%22,T-Rudder

 

The configId, is the JOY# ID seen in the settings withing the game. In the above example the T.16000M (device model) is set as JOY 1 in game settings when you bind your joystick.

guid is the unique ID created by windows for the device (the device driver name for it).

model is the user friendly name generated by windows for the device.

 

Its possible if the configId  changes in here it will mean the mapping in game no longer match it, and it will not work in game, unless you change these to match.

The configId  generated here can change in windows (as it depends on order devices are connected) and this can cause ID mismatches in the game, because the game only uses configId  and not guid to determine the mapping based on what is generated in this file. guid  can also alter depending on how (where) device is plugged in.

 

 

 

 

 

Edited May 7, 2020 by =RS=Stix_09
addtion about devices.txt