Uncommanded Rudder

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.


ISSUE DESCRIPTION

Description of the issue: As soon as I click on “Ready To Fly” in Free Flight the rudder will move to full right rudder. Using the rudder pedals to try and center the rudder will make it flutter and then go back to full right rudder. I disabled my Turtle Beach VelocityOne pedals and used a keyboard binding to eliminate it being a hardware issue but the problem persists. It makes the simulator unusable.

If applicable, which aircraft is experiencing this issue: It happens on all the aircraft I have tried. Obviously I haven’t tried every single aircraft but at least 7 different aircraft are effected. The DH2 Beaver, Cessna 172, Cessna 152, Cessna 152 by WBSim, Carenado C170B, DC Designs Stearman, and the DC-3

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue? Yes I did and the issue persists.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)? Every time I try to use the sim.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Launch Free Flight
  2. Select and aircraft
  3. Select an airport
  4. Click on Ready to Fly.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant: Turtle Beach Velocity One Rudder, Honeycomb Alpha Yolk and Bravo Throttle Quadrant, and an Xbox Controller

[PC Only] Are you using Developer Mode or have you made any changes to it?
No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

[PC Only] What GPU (Graphics Card) do you use? NVIDEA GTX 4090

[PC Only] What other relevant PC specs can you share?

Processor 13th Gen Intel(R) Core™ i9-13900K, 3000 Mhz, 24 Core(s), 32 Logical Processor(s)
Windows 11 Pro Version 10.0.22631 Build 22631
64 GB memory.
NVIDIA GeForce RTX 4090 24 GB VRAM

MEDIA

Please add a screenshot or video of the issue occurring.

The full right rudder at the beginning of the video is without any input from me. I then use the rudder pedals to recenter the rudder and as soon as I return to neutral they go back to full right rudder. The view from the outside is the same behavior.

Below are screenshots of this problem:

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Are you using any assistance or something?

You’re going to need to supply more detail here for this bug report to have any value to the developers.

:slightly_smiling_face:

Are you using keyboard commands to move the camera position (i.e. CTRL + Enter, SHIFT + Enter)? Enter is one of the keyboard key to move the rudder to the right. Also, if using a joystick check and see if the joystick twitches on its own…

Thanks for the reply. I do use some keyboard commands for camera positions but none of them use the enter key. They are mostly the set camera positions for looking at different parts of the instrument panel. I have created all new profiles for all the peripherals I use and deleted all the key bindings that I don’t use. I find this particularly important for a joystick that I only use for helicopters and keyboard commands that can be accidently activated by my fumble fingers.

I am using the Turtle Beach Velocity One Rudder Pedals and have checked them out in MSFS 2020 where the hardware settings allow you to actually see the different axis movement in Controls Setup, unlike 2024 where there is no indication of movement in the setup. They work flawlessly in 2020 so I don’t believe it is a hardware issue at all. I did adjust the sensitivity and dead zones for the rudder pedals and thought that may have caused the issue but returning the settings to the default did not solve the problem.

Hey Nixon, what additional information would you suggest? I have supplied the video card I am using, that it is MSFS 2024 and the steps I take to cause the issue. My graphics settings don’t include any choices for DX 11 or 12

To start, I’d fill out the Issue Description. Reading the report, as it has been submitted, doesn’t explain what the issue is you’re having.

Definitely answer the question regarding disabling add-ons (if you have any) and testing without them.

Of course, if you can, capture some video of the issue occurring, and add it to the original post.

Try to unplug your Xbox Controller, I had a similar issue and unplugging it fix the issue with the rudder. If it is confirmed it was the root cause, maybe a workaround exists to avoid this kind of conflict but I am not aware of any.

Hey Demented,

Thanks for the suggestion. I have customized the profile for the controller to only have commands that work the drone camera, player character and slew mode. None of the aircraft functions are used by the controller. That being said I did disconnect the control as you suggested but it made no difference.

1 Like

Earlier today, without making any changes, the behavior stopped and I was able to complete two flights. I paused the simulator during dinner and upon resuming the simulator the problem has returned. I did nothing to stop the behavior and, other than leaving the sim paused for a while, I did nothing to cause the issue to return.

I have exited the simulator and restarted multiple times and the issue persists. No clue why it stopped for a short while. I am considering a reinstall but I am hesitant to do that.

If not already done, what I would try:

  • disconnect all your USB peripherals (except mouse/keyboard), I know you already disconnected the Xbox Controller but worth try disconnecting all of them
  • check you don’t have any rudder binding conflict, searching "rudder axis " in all your peripherals:

Problem solved. It was not what I expected. While looking to see if someone else had posted something about the User Interface shortcut keys defaulting to the Controller instead of the keyboard and there being no way to fix it, I found several references to default 2020 Transversal Keyboard profile being a problem and corrupted.

With that information I changed the General Keyboard profile from the one I created from the 2020 transversal to the 2024 Transversal and magically, the ESC key became the back shortcut in the UI instead of the “B” key on the controller. So I knew I was onto something.

With that change and thinking about what Demented had posted earlier I rechecked the Rudder Axis key binding only to find it was also bound to my joystick. When I changed the keyboard profile back to the one created from the 2020 transversal the joystick Rudder Axis key binding disappeared but was still active. Go figure. So when I had the 2020 Transversal General based KEYBOARD profile in use it masked key binding for another device and in the 2020 Transversal Keyboard PLANES profile.

With that knowledge I took screen shots of all of my keyboard key binds, deleted the 2020 Transversal General and Planes keyboard profiles I had created, copied and renamed the 2024 Transversal General and Planes profiles, cleared them and then recreated all of the key bindings.

This solved several issues I was having. The rudder problem described above, an issue with the sim semi-freezing after using pause, and the issue with the User Interface using the Controller for shortcuts instead of the keyboard.

Apparently the 2020 Transversal Keyboard Profile is corrupted and will carry over the issues if you are using it.

Mike

I

1 Like

Moved to User Support Hub since a solution has been marked.