I experience a similar bug on Xbox. But, it’s sometimes worse: the throtle and the flaps controls change also without any action on controllers.
I first thought of a conflict between devices (I have joystick HOTAS ONE + Xbox controller + mouse + keyboard attached).
But I think, the issue is more related to AI, that take control of your plane (like it does, if configured, when you are under the “cursor” mode).
On external view, I clearly see the rudder moving left/right when I move my joystick, but then return to central position.
Same for the throtle, even that I’m at idle position, I see it moving to full! and same for the flaps.
It’s exactly as if someone has control of my aircraft, and act as opposite as what I want to do
Quite sure this issue is related to AI automatically activated, when unwanted.
If you have multiple devices connected. Make sure none of these devices are mapped to the same command. For example, if you set throttle axis to your Joystick HOTAS ONE, make sure your Xbox controller and Keyboard do not have any engine power management bound to them. In other words, your engine throttle control needs to be bound ONLY to your Joystick HOTAS ONE and nothing else.
Similarly, the commands that you have bound to your Xbox controller must not exist in other hardware as well to make sure nothing is conflicting.
If it has something to do with AI, make sure you go to your assist settings and set everything to HARD/True to life to turn them all off so that AI don’t do anything to your plane without you knowing.
This was related to IA, as I suspected , but it was also the consequence of another bug that I experienced a few days before. Indeed:
Initially, I configured all settings to “difficult”, to avoid strange behaviour caused by the IA.
Some day ago, I suffer twice a disconnection from Xbox live servers (errors 0x87DD0017 and similars). And of course, I got a message of “invalid licence” for the game.
As strange result, I lost twice my LOGBOOK, but also some others settings (like sounds volume). I opened another thread for that.
But I didn’t notice, that my difficulties settings were also reverted to “easy”. It’s not me that modify that, it’s FS2020 that hang when the Xbox live service was unavailable and revert to defaults .
I’ve check today, indeed my settings had been reverted to “easy”, with IA selected for several things (landing, cursor mode).
so, I changed back my settings to “difficult”, and the problem is gone away.
Note that, I’ve try to reproduce the disconnection issue, by removing my ethernet cable. In this case, the connection is lost but don’t get the same error. And my LOGBOOK, and settings were not erased.
It is still abnormal that FS erases such important information on the Xbox. Luckily, I only had 25 hours of flight time, but I can imagine the head of those who will suffer this bug with 499 hours of flight, or worse 999!
For the rudder recentering, the solution seems to be, to do without AI. But it is still necessary that the configuration is not randomly erased by FS2020.
Yeah, MSFS has the tendency to change settings on its own. A good rule is that, if things work differently than before, check, and double check your settings. Just because you never change it and confident that your setting is correct, doesn’t mean it didn’t get changed and it didn’t become incorrect.
So once you finished checking, and making changes and double checking it… The next step is to triple check it again just to make sure. Then try flying again.
I’ve been doing this checking since launch, and for every major update. Which gets me to be on top of any “potential” issues that might crop up.
It seems that rudder assist in flight should be separate from rudder assist on ground. Two different settings for us novice pilots that need auto-assist on flight turns, but need “realistic” on ground.
I “had” this problem too… gone now.
It was because I had rudder axis set on two different devices… my Rudder Pedals, and my twist axis on my HOTAS… even though I was using my rudder pedals to steer the aircraft (I was on the ground taxiing) the rudder kept getting sent back to center… because it was getting instructions from both devices.
Once I unplugged the HOTAS (which I was only using for Helicopter flight) everything worked fine.
This issue is very annoying. As soon as I touch down on the runway the rudder gets uncontrollable. I’m using Thrustmaster T16000M FCS with Throttle on a PC. I’m using the joystick RZ axis for rudder axis control, when twisting right the rudder initially goes slightly to the right, but immediately re-centers itself. The same when twisting left. After a while when ground speed drops to somewhere below 10 knots even this behaviour changes and the rudder gets totally nuts and doesn’t respond to any twisting.
I notice that if I do a manual re-center rudder command, the rudder behavior briefly becomes normal. But after 2-3 seconds the erratic behaviour is back again.
I’ve trimmed sensitivity curves, dead zones etc, but the erratic behaviour remains. Side winds, aircraft etc doesn’t matter. Tried switching off all AI, no impact. Double and triple checked that I don’t have more than one rudder control mappings, I don’t.
If someone knows anything more about this, it would be appreciated.
@Neo4316 yes, I did, same thing anywhere on the ground.
But I tried the last thing that I hadn’t yet tried, that is unplugging my throttle unit from the USB port while standing on the runway with engine running and waiting to take off. Waited a few seconds, plugged it back in again. After a few seconds the throttle was connected again, AND… the rudder control is now working 100% correctly while twisting the joystick. Couldn’t believe it, so I powered down my PC, restarted, and restarted MSFS… now the rudder behavior is fully correct already from start without any unplugging/plug in… I have no clue why, but it seems the problem is gone.
You are not the only one.
Flying with simple Cessna 152 or the IconA5, (my preferred aircraft, it can float),
always the same happens.
Before taking off, taxiing to a runway everything goes fine, perfect.
I can control the aircraft perfectly with the rudder keys 0 and Enter.
Than I take off and fly to another airport or return to the same.
I land fine on the gear-wheels, and then suddenly the rudder “blocks”, centers.
No way to control it with the keys 0 or Enter.
The aircraft therefore is riding uncontrolled, ending up almost everytime somewhere on the side of the runway.
Very sad.
They should warn you that if you ever use the flight assistant to look after your bird while you see to other things then thereafter he has the habit of changing settings and turning up when you least expect it.
After reading through all the responses, I took off any assists and BOOM! Problem gone! OMG - SO much easier to land a plane with a functioning rudder …!!! Thabk you all for your comments, and everyone that has contributed to this thread
I have the same problem. But only on some planes. Rudder works fine on airbus so it doesn’t make any sense other than poor programing and no interest in fixing it.
Just encountered this behavior in SU7. I thought it was a quirk of the new PC-6, but with full rudder applied to my physical pedals in either direction, the pedals in game slowly move back to center.
Maybe some fixes work for some. None for me. We shouldn’t have to be fixing anything. Total nonsense. It worked before and now it doesn’t. Hmmm? I wonder who’s fault could it be. My guess is incompetent programmers. They designed the software so they should know how to fix the bugs.
I’m getting this too, and it never happened before. Watching the plane tail from outside and I can see the rudder making an initial deflection but then returning to the centre fairly quickly. Makes taxing almost impossible without differential braking. Plus I have Auto-Rudder turned OFF.
, but it was also the consequence of another bug that I experienced a few days before. Indeed:
.
Thabk you all for your comments, and everyone that has contributed to this thread