Thrustmaster pedals - does not sense left rudder

Hello - after a couple months off and updating MSFS, wanted to fly a gain and having a problem. I cannot input left rudder. I have set the rudder axis to axis-X. It picks up all movement from neutral/center to full right, and nuetral is full left. It does not sense or pick up anything from neutral to left. So to hold a plane steady I have to be at more or less half right rudder.

the bar in the control settings is full left at neutral, and full right at full right.

tried independently setting left and right axis and it doesn’t even sense when I push full left from neutral.

Its not a hardware problem, XP and thrustmaster calibration are sensing the full travel of the rudders.

thoughts?

If I had a similar problem, I would probably start looking for the files storing your individial controller settings.
Read this post:

In case of Steam version there’s a folder storing all these profiles;
C:\Program Files (x86)\Steam\userdata\1145115672\1250410\remote
Make a copy before you start messing with it:)

Btw - are you sure that your pedals are in flight simulation mode ( green led light instead of red)?

Check your Sensitivity Curve on the pedals, you might need to adjust the “Neutral” point accordingly.

So…I had a car racing wheel and pedals also by thrustmaster that I use for VR racing games.

I have no idea if they share drivers or something whacky like that, but MSFS was reading my flight rudder pedals as the racing pedals. So basically what it was calling the X-Axis could only go one way like a gas pedal. I unplugged, deleted drivers (could only find a driver labeled as the racing pedals, not the rudders), reinstalled new rudder drivers from TM website, rebooted. MSFS reading it fine now. Crazy.

Well, MSFS detects all the hardware that was plugged into the PC, so it’s best practice to unplug the hardware that you don’t want to use with MSFS.

No the racing pedals were not plugged in at the time. Nor do I think they have ever been plugged in when MSFS was launched. Something happened with the thrustmaster files/drivers that confused the two thrustmaster products I think. Oh well, solved now.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.