In all the time I have been flying, this issue has stumped me dead. Something very odd is happening when I use msfs2020. It started with the PMDG 737-800. I started a flight and for some reason, once I wasin the VC, the rudder pedals began to rattle, as though they were being pressed on and off quickly. The rattling movement was accompanied by a rattling sound. This was in any panel state that was loaded. Then in the A2A Comanche, for some reason, the pressing of the pedal brakes, intiates rapid in and out movement of the handbrake lever. In the Just Flight Arrow, the moment I enter the VC on flight startup, the handbrake continues to rapidly move in and out. In the Kodiak, there are numerous sounds that are present even when the aircraft is in a cold and dark state. When trying to start the Kodiak, it will not start and there all the sounds are muted. Likewise in the Cessna 414 the cold and dark cockpit is full of odd sounds. It's all very odd and I have been unable to get to the bottom of things. I have uninstalled FSUIPC and have tried all scenarios wihtout Axis and Ohs. I am 99.9% convinced there is no conflict with anything. The issue is always present, even when I have disconnected the MFG rudder pedals. Any help with this would be very much appreciated.

Edited October 21, 2025Oct 21 by Rocky_53

I'd start by downloading the free DIVIEW utility from the leobodnar.com website, and look at what's happening with the raw inputs from all your physical device axes.  If you have a device with a fluttering axis, you'll see it there.

Second, I'd go through all the assignments on every device listed in the MSFS controls UI and make sure you don't have any "phantom" unintended axis assignments.  Make sure you scroll down through all of the listed axes, even if they don't physically exist on the device.  Multiple assignments across different devices to the same control can fight each other and produce rapid oscillations like you describe.

As to sounds in cold/dark state, could they be environmental, nearby AI, ground handling etc?  Are they weird electronic artifacts, or sim sounds that are out of place?

Are there any other add-ons in play, particularly something like a ground handling add-on that may be grabbing your rudder axis?

Hi mate, don't be alarmed, but I think MSFS 2020 is in the process of self-destructing. I've noticed no end of odd things occurring, not least a gradual decline in graphic quality. So much so that I'm currently in the middle of removing 2020 from my PC completely and switching to 2024.

1 hour ago, SierraHotel BSc said:

Hi mate, don't be alarmed, but I think MSFS 2020 is in the process of self-destructing. I've noticed no end of odd things occurring, not least a gradual decline in graphic quality. So much so that I'm currently in the middle of removing 2020 from my PC completely and switching to 2024.

Some of us saw the writing on the wall and made the switch a year ago.  🫠

Really happy with the new sim.

dd

Edited October 21, 2025Oct 21 by Sky_Pilot071

2 hours ago, Bob Scott said:

I'd start by downloading the free DIVIEW utility from the leobodnar.com website, and look at what's happening with the raw inputs from all your physical device axes.  If you have a device with a fluttering axis, you'll see it there.

Second, I'd go through all the assignments on every device listed in the MSFS controls UI and make sure you don't have any "phantom" unintended axis assignments.  Make sure you scroll down through all of the listed axes, even if they don't physically exist on the device.  Multiple assignments across different devices to the same control can fight each other and produce rapid oscillations like you describe.

As to sounds in cold/dark state, could they be environmental, nearby AI, ground handling etc?  Are they weird electronic artifacts, or sim sounds that are out of place?

Are there any other add-ons in play, particularly something like a ground handling add-on that may be grabbing your rudder axis?

Thanks for the suggestions Bob. Some interesting theories. The oddity, is that nothing has changed from the previous day when everything was working fine! I'll pursue things again tomorrow, cheers.

 

1 hour ago, SierraHotel BSc said:

Hi mate, don't be alarmed, but I think MSFS 2020 is in the process of self-destructing. I've noticed no end of odd things occurring, not least a gradual decline in graphic quality. So much so that I'm currently in the middle of removing 2020 from my PC completely and switching to 2024.

Yikes!

 

Did you try to repair MSFS ? Go to the Xbox app,then MSFS 2020 in your library, click on "manage" then "verify and repair". Just in case before further investigations. Be aware to rename your Community folder first to save it.

The control profiles are stored in the cloud.  My guess is that any sort of oddity with the cloud save and you could end up with the situation you describe.  This has never happened to me though.

I'm not sure I'd go for a repair of the install quite yet...it might work next time you boot the sim.

It sounds like your save profiles aren't being read, and it's reverting to some default controls state which isn't set up for all of your input devices.

Try temporarily disabling all your sound devices in Windows Control Panel | sounds. 

Also Control Panel | Device Manager | Human Input Devices and USB Controllers. Click every listing in those two areas and | Properties | Power Management | uncheck the box allowing Windows to ever turn that device off. Windows will now never turn it off/on off/on etc.

45 minutes ago, danhenri said:

Did you try to repair MSFS ? Go to the Xbox app,then MSFS 2020 in your library, click on "manage" then "verify and repair". Just in case before further investigations. Be aware to rename your Community folder first to save it.

Nope, not yet. That will be my last resort mefinks.

40 minutes ago, Mace said:

The control profiles are stored in the cloud.  My guess is that any sort of oddity with the cloud save and you could end up with the situation you describe.  This has never happened to me though.

I'm not sure I'd go for a repair of the install quite yet...it might work next time you boot the sim.

It sounds like your save profiles aren't being read, and it's reverting to some default controls state which isn't set up for all of your input devices.

Indeed.

 

38 minutes ago, Fielder said:

Try temporarily disabling all your sound devices in Windows Control Panel | sounds. 

Also Control Panel | Device Manager | Human Input Devices and USB Controllers. Click every listing in those two areas and | Properties | Power Management | uncheck the box allowing Windows to ever turn that device off. Windows will now never turn it off/on off/on etc.

Thanks. I'm off out now, but will follow your's and others' suggestions tomorrow. Fingers crossed.

Hey guys... sorted!! I got up this morning with one thing on my mind, and that was to get to the bottom of this problem. However, as is often the case, the most frustrating of issues are often attributable to the simplest of solutions. With that idea in mind, I thought I'd revisit the conflicting assignments idea, even though I had gone through that possibility with a fine 'tooth comb.' Now don't shout at me too much fellas, but yes, that is what it was. In my defence, it wasn't all 'finger trouble.' As I was going through each of the hardware in the control panel of MSFS, I checked the throttle, the rudders, the yoke, the controller that I have, and assignments in FSUIPC and A&Ohs, all good, as before! There must be something, so I went back into MSFS control panel and there's a section named Button Box, which recognises a Leo Bodnar switch panel I use with A&Ohs.... and here's the thing, in there was an assignment for a parking brake! Now I don't know how that was assigned or even moreso, how that particular profile became active. I never touch that profile, I only ever choose the profiles for the rudder, yoke and throttles. After deleting that profile, all was good! Another darn frustrating bug in the world of MSFS  

Anyhow, thanks for everyone for their advice and suggestions, very much appreciated. 

Edited October 22, 2025Oct 22 by Rocky_53

22 hours ago, SierraHotel BSc said:

Hi mate, don't be alarmed, but I think MSFS 2020 is in the process of self-destructing. I've noticed no end of odd things occurring, not least a gradual decline in graphic quality. So much so that I'm currently in the middle of removing 2020 from my PC completely and switching to 2024.

Planned obsolescence? Nah too much of a conspiracy lol … or is it?

Edited October 22, 2025Oct 22 by UAL4life

@Rocky_53 Thanks for posting your discovered solution. I (and maybe others) have been following this thread because the puzzle you presented is peculiar...and because you had tried all the obvious fixes. And lots of good suggestions from others (to be filed away for other contingencies). 

Sometimes the original poster will fade away after finding (or not finding) a solution. Others might post "sorted now" without details. Your very explicit description of your second-day-process helps us all to think about how to solve these little mysteries that Asobo presents (presumably for our education or our entertainment). 😉

Much appreciation to all involved.

20 minutes ago, MM said:

@Rocky_53 Thanks for posting your discovered solution. I (and maybe others) have been following this thread because the puzzle you presented is peculiar...and because you had tried all the obvious fixes. And lots of good suggestions from others (to be filed away for other contingencies). 

Sometimes the original poster will fade away after finding (or not finding) a solution. Others might most "sorted now" without details. Your very explicit description of your second-day-process helps us all to think about how to solve these little mysteries that Asobo presents (presumably for our education or our entertainment). 😉

Much appreciation to all involved.

👍

On 10/21/2025 at 11:18 AM, SierraHotel BSc said:

Hi mate, don't be alarmed, but I think MSFS 2020 is in the process of self-destructing. I've noticed no end of odd things occurring, not least a gradual decline in graphic quality. So much so that I'm currently in the middle of removing 2020 from my PC completely and switching to 2024.

MSFS has never looked or performed better here and any decline in graphic quality is on your end, on my end it is sharing the same digital twin as MSFS24, night lighting is great, if it was self destructing it's on your PC MS is not deprecating 2020 (yet) but don't let the tin foil hat burn your scalp LOL

10 hours ago, Rocky_53 said:

Hey guys... sorted!! I got up this morning with one thing on my mind, and that was to get to the bottom of this problem. However, as is often the case, the most frustrating of issues are often attributable to the simplest of solutions. With that idea in mind, I thought I'd revisit the conflicting assignments idea, even though I had gone through that possibility with a fine 'tooth comb.' Now don't shout at me too much fellas, but yes, that is what it was. In my defence, it wasn't all 'finger trouble.' As I was going through each of the hardware in the control panel of MSFS, I checked the throttle, the rudders, the yoke, the controller that I have, and assignments in FSUIPC and A&Ohs, all good, as before! There must be something, so I went back into MSFS control panel and there's a section named Button Box, which recognises a Leo Bodnar switch panel I use with A&Ohs.... and here's the thing, in there was an assignment for a parking brake! Now I don't know how that was assigned or even moreso, how that particular profile became active. I never touch that profile, I only ever choose the profiles for the rudder, yoke and throttles. After deleting that profile, all was good! Another darn frustrating bug in the world of MSFS  

Anyhow, thanks for everyone for their advice and suggestions, very much appreciated. 

Glad you got it sorted!