Hi everyone,
I hope this post can sweeten the weekend for some of you, because I think I’ve found a workaround (at least for my rig) that finally fixes the steadily increasing mainthread latency.
Important upfront: I’m only talking about the bug that’s mentioned in the title of this thread - not the one caused by opening and closing the controller settings.
As you can see from my previous posts here, I’ve already tried just about everything on the BIOS, CPU, GPU, Windows, and sim settings side, with no real success.
User RogueNaught1 reported that uninstalling his GPU drivers in Safe Mode with DDU and then reinstalling them fixed the issue for him. I tried exactly that, but unfortunately it didn’t work on my end.
However, in a later post he also mentioned reinstalling his sound drivers, which got me curious and led me to dig deeper into the audio side of things.
Here’s what I found:
-
My motherboard (Gigabyte B850 Aorus Elite) still had a Realtek audio driver from 2021 installed. On the Gigabyte support page I noticed there was a brand-new driver from late August this year. I updated to that version.
-
With the new driver installed, I had noticeably fewer mainthread spikes, but the creeping latency problem was still there. Still, that improvement was enough to make me keep investigating.
That’s when I remembered an old MSFS2020 thread about mainthread issues when leaving the sim’s audio set to “Default Sound Device” instead of explicitly selecting a dedicated device.
https://forums.flightsimulator.com/t/high-manipulators-thread-usage-when-audio-device-is-set-to-default/497252
And bingo that opened a can of worms. It seems that SU3 introduced serious sound-related issues, and that old MSFS2020 bug has made its way back into MSFS2024.
So I switched my in-sim sound from “Default” to a dedicated device. With that change, I was able to complete my first flight since SU3 where the mainthread latency didn’t** climb!**
BUT don’t stop reading here - it gets more complicated:
-
After every system or sim restart, the sound setting resets back to “Default Device.” (Sounds like another bug.) So you’ll need to manually reselect your dedicated device each time you launch the sim. At least for Steam users, this bug seems to be known and can also be found here in the forum.
-
Once I consistently set the sim to use my Realtek device, I could fly without any creeping mainthread latency. The flights were completely stutter free… up until touchdown. But as soon as the wheels hit the ground, I started seeing pulsing CPU spikes.
Digging further, I traced those spikes to GSX. Now, don’t blame GSX itself - because it’s still tied to the sound issue. Here’s what I had:
-
I had GSX voices playing through my monitor’s AMD HDMI sound, while the sim’s main audio went through my Realtek card to the speakers.
-
When I disabled all AMD/other sound drivers in Windows Device Manager and left only Realtek enabled, then set GSX to use the same dedicated Realtek device as the sim, the CPU spikes on landing completely disappeared.
Since then, I’ve managed several full flights: no creeping mainthread latency, no spikes, fully smooth all the way.
Hopefully this isn’t just a fix for my rig and can help at least a few others here as well.