Hello!
I’ve got rudder problem. The rudder isn’t go to the center after I pushed the button. It was good until the last update. It works now as a rudder trim. (Normal: I push the rudder yaw left button, the rudder go left and go immediately to center. Now, I’ push the button and the rudder stay left. I have to push the right rudder yaw or the center rudder button to go to cebter.)
I’ve got a Logitech Attack 3, without rudder axis. I use the 4 and 5 buttons to operate the rudder.
Do you have A/THR or Auto-Throttle On or armed? If so, try to turn it off and check your rudder again.
Thank you for your comment, but all the plane are working “bad”. I disconnect A/THR, but the rudder isn’t good. Cessna 172 is bad too, without ATHR.
Assign your buttons to the Rudder Axis Left and Rudder Axis Right instead of Rudder Left (Yaw Left}/Rudder Right (Yaw Right). You’ll have to select your button choice from the pull down menu (Select an input) instead of using the scan input.
You’ll receive a warning that this action is not recommended. Ignore the warning and validate it anyway.
This is the only way I could personally get the rudder to re-center automatically after using a button to move the control surface.
Bingo, it is just working. Thank you Randall! 
i can’t find rudder AXIS left/right under keyboard profile (and yes, I have filtered to ‘ALL’). under my joystick (logitech attack3), I can find rudder AXIS left/right but cannot assign a keyboard button to it. what do I do now ? I really don’t like the press ‘‘numpad5’’ to center. I want auto-center like before !!!
There is no axis on a keyboard, only controllers have an axis, so you can’t assign an axis to a key.
Change your keypress to make it more convenient.
I set the “del” button on the numpad for “center rudder” which makes it a whole lot easier to keyboard taxy.
The binding you are using, Num 5, which is center aileron and rudder, is a bit out of the way, and not really the correct command anyway.
I don’t know if it was a keyboard AXIS before the update, but I know one thing, I flew for 3 months with auto-center with keyboard and it WORKED. Now I cannot anymore.
I will remap auto-center to numpadDEL, but this was previously my brakes. where am I going to put the brakes now ? somewhere with my other hand that’s supposed to handle the joystick ? I hate that this was changed.
I wrote in another post about the same subject about the Center key:
tried it. it works for slow taxi (it’s not intuitive, but I could get used to it), but it is absolutely ineficient and impractical when medium-high speed (take-off and landing), because even the 1st increment off-center makes the plane turn too fast (and that’s not even considering WIND that is not constant). I would have to press the centerKEY precisely to the micro-second to keep the plane inline with runway (and adjust many many times with the same precision), where as with auto-center, I could tap (more or less fast) and it would behave like any other ‘‘driving’’ on the ground
Like you I didn’t have a problem with taxiing using the keyboard before this update. Somewhere on here there is another thread where the op does state that the rudder axis disappeared for keyboard. It seems really stupid that this should just disappear as part of an update when it was a proper and normally functioning command before. Like many on here i’m really disappointed at the lack of testing Asobo seem to run before releases. I remapped my del button for rudder center and whilst not perfect at least it works. Here’s hoping that Asobo correct this soon. But i’m also aware I need a new stick that has a rudder axis!
Because Axis is an analog controls that have infinite number of levels to control the amount of input. Keyboard is a digital input, not analog. Either you press it or you don’t. So binding rudder axis to keyboard should not be allowed. Instead, use Rudder left and Rudder right to be bound to keyboard instead.
Do NOT patronize me. I (we) are fully aware of the distinction between analog and digital input. YES, it is very and fully possible to map a keyboard button to an analog input : IT was the way it was done a few weeks ago and fully working (and the best way for people without a joystick, or pedals): a single key press took the rudder to the extreme position and it came back by itself when key is release. It also works like that since decades with car games (a steering wheel is analog, but it can be map to left and right arrow on a keyboard). I know it doesn’t allow for partial rudder (coordinated flight), but you should know that people without a joystick can still enjoy a flight simulator with auto-rudder)
If the amount of people experiencing the problem does not convince you. Then go on with your day and bebay!
I’m not patronising you, I just had a lot of topics being raised simply because people can’t differentiate between analog and digital inputs. I’m just trying to cover that’s not the case for you. I work in IT, and you have no idea how many people come to me with stupid questions that can easily solved by common sense. And again, I’m not patronising you, but you might need to show us that you do have the knowledge with everything. So if you only say “it works before and not anymore” we’re just gonna assume you’re a beginner that we have to be a bit more clear on our explanation.
Yes, of course you can map a keyboard button to an analog command. But it’s not recommended to do so, because the sim already has an equivalent digital command to go with it. Rudder axis can go either way, left or right in a single axis command. So if you bind this axis to a single keyboard button. How can you tell the sim to turn left or right using a single button.
That’s why the sim has a digital input called Rudder Left, and Rudder Right that’s specifically designed for digital inputs where you bind one keyboard key to the Left Rudder, and another keyboard key to the right rudder.
And one thing for certain… Changes will always happen, never assume that if it works today, it’ll work the same way tomorrow. You have to be flexible, adaptable, and be mindful of any changes. If one thing suddenly doesn’t work, investigate, analyse, get some understanding on what’s happening, try different things, see if that works. And keep doing it until you get it working again.
Chances are, the changes are made deliberately to fix something else, which impacted your setup. Just like the sensitivity curve changes that happened months ago. I have my joystick hardware setup properly and it works just fine. Then they change the sensitivity curve which makes my joystick no longer working the way it was. There is a valid reason for that sensitivity curve change, which is to make another hardware fully supported to the sim, which couldn’t work with the old sensitivity curve change. Sure, it breaks my current setup, but this is done so that other people can have their hardware working, So what I did was to simply reset the curve, and make adjustments so it can behave the way it was before. Now everyone has equal opportunity to enjoy the sim. Just because a change affects you negatively, that doesn’t mean it’s a negative change. Adjust it, and you will adapt to the change.
If you want auto-center with the runway, turn on take-off auto rudder assists. That should help you stay straight when taking off.
just to show you how stupid ASOBO are with this particular issue : I have a joystick and according to you, I shouldn’t map RUDDER AXIS to a keyboard button (ASOBO have effectively prevented that), but guess what? I have mapped it to a BUTTON on my joystick !! yes, that’s right, a digital button for an analog input ! it just doesn’t work on keyboards (so ASOBO is effectively giving the finger to those who do not have joystick and/or pedals).
Have you tried taxiing at medium to high speed with RUDDER INCREMENTS (on keypress, and without auto-center) ? it is NOT the way to go… try it and report back.
I can try it but my sim is keeps CTD on main menu… So I’m waiting for the UK update next week and reinstall everything after I reinstall my Windows. So I’ll give a report after then.
I also have rudder control issue. When moving the joystick in the Z axis, it starts to move properly, the flutters and slowly does it’s re-centering thing… Is not aircraft related, since it acts the same on three totally different aircraft types. I have mapped it in every way available, done all the curve and sensitivity adjustments, but problem persists. I even mapped it to the elevator movement of the joystick, but no change in behavior. I have used several different joysticks, and rudder behaves the same on all… I am setup now using just " Rudder Axis". I haven’t used the keyboard in a long time for control surface flying, especially for the rudder, so not doing much testing there. All other flight control surfaces and trims work perfectly. I am left with the assumption that it has to be a software related issue affecting only the Rudder input since it is the only common element I can’t check.
I should like to note that All of this was done in the Free Flight Section, not in training or other sections.
We can only hope is addressed in the next upgrade…
It is very frustrating to have a near perfect flight and landing, then have the aircraft go berserk on the ground handling. Thanks to everyone here trying to work us through this issue.
ASOBO giving the finger?
Sorry, but I disagree very strongly.
The analogy I would like to present is: If you need a steering wheel for your car, would you wire in a keyboard and try to drive the car with that?
Airplanes aren’t flown from a keyboard IRL.
When you attempt to do so, you are never going to get the same flexibility of operation.
There will always be issues and restrictions.
Personally, I taxied with a keyboard using rudder increments for years when I was younger and didn’t have the cash to buy rudder pedals and other controls.
I had one button for left, one for right, and one for centering
It’s not easy, but it was do-able.
There is something going on, as that shouldn’t happen.
It would be fairly common if it was MSFS software related, and I haven’t noticed this issue before.
I take it the Z axis is a twist command?
Did you try playing with the reactivity settings?
Is there any assists enabled?
Have you checked for a control conflict?
Sorry it took so long to answer, but read on and you will understand…
Yes, my rudder control it is with a twist of the joystick (Z-Axis).
Yes, tried changing/modifying the curves and percentages including the Reactivity.
Yes, checked for conflicts and even cleared all other rudder related input boxes, even if they didn’t show any entries.
No assists were enabled.
As I indicated previously, even swapped out Joysticks, still no help, same issue…
I used two different aircraft, King Air 350i and the 172 Skyhawk G1000, same issue, but “somewhat better” with the “Skyhawk G1000”, than with the standard Skyhawk.
That variance started me thinking “maybe” it could be with the Aircraft Type… So I loaded up the Boeing 747, the Cessna Citation CJ4, and the Piper J-3 Cub. NONE of those 3 had Any Rudder issue at all…!!
I reloaded the Skyhawk G1000, rudder problem was still there. ALL 6 Taxiing and Runway tests were done with Same Rudder Settings, nothing was altered except using different Aircraft Types… Try it. Would really like to know if others have any rudder issues with the KingAir 350i especially… I consider the problem solved for my purposes. I will avoid using those types with the issue until it is fixed with a patch.
I experienced the same rudder issue with both Cessna 172’s and the KingAir 350i.
Try using the Piper J-3 or the Cessna Citation CJ4. They don’t have the rudder problem on my setup… Good Luck.
What command are you using for the rudder?
Are you using the "rudder - - -(Yaw - - -) " or the “rudder axis”?
