I’ve been running without BATC in all my testing, so that’s not a cause for my stuff.
I’m trying to find the motivation to downgrade to 23H2 to test that hypothesis But since Asobo isn’t even acknowledging that this is something they’re looking into…
I will not downgrade to 23h2 and I don’t see the point in making my system less secure just because Asobo can’t do it. This post currently has 319 messages and 4900 views. What else should we users do to make Asobo realize that the fault lies with them, or with Microsoft? I can still see the point of updating a driver. But I can’t ask them to carry out a bios update. Even if Asobo hasn’t said this, some people here are doing it (including me) The error should finally be rectified! The simulator has been out for four months now. In my opinion, this is a disgrace what is being delivered. I would love to play the 24. But the problems with the sound are just annoying and ruin the flying experience.
Let’s take a more scientific approach. My thousands of flight hours and extensive experimentation have led me to formulate the General Theory of Stutterevity, expressed as the following formula:
S = c * (1 + l)²
Where:
S – stuttering intensity
c – aggregate flight complexity, ranked by impact: photogrammetry + DEM detail + LOD + aircraft complexity + other sim settings
l – aggregate streaming latency: content-demand-induced latency (how many people are streaming the same content as you) + game server latency (determined by your location, ISP, etc.)
This theory explains why some people don’t experience the problem and why Asobo is unable to reproduce it. In both cases, aggregate streaming latency (l) isn’t high enough to trigger the issue.
Flight complexity (c) alone can theoretically induce stuttering even without streaming (when l = 0, so (1 + l) = 1), which is why I encountered the exact same audio stuttering already in FSX when using highly detailed mesh (DEM). While MSFS is more efficient at handling computational load, the stream-it-all philosophy of MSFS 2024 shifts the break-even point for stuttering, making it more dependent on latency than sheer complexity. This also explains why MSFS 2020, which relies less on streaming (e.g., mesh isn’t streamed), is less prone to the issue.
Due to the variability of aggregate latency (l), the same flight complexity (c) can sometimes induce stuttering and other times not. This leads many users to believe they’ve found a solution, when in reality, they’re falling for a post-hoc fallacy.
Downgrading Windows, changing drivers, tweaking settings, or throwing snake oil at your PC has zero impact on the root cause.
Great post and formule. You are right, I tried All Snake Oil. The problem must be on the server-side…
Due to some new hardware I have been testing the same scenario over and over the past week. Today during the weekend I noticed much more stuttering. Must be server load as nothing changed on my side…
I don’t think this is necessarily server-side. Could be exacerbated, yes, but not the sole reason.
I’ve done the exact same route multiple times, trying different settings, etc. .
There was no difference between when I loading the scenery for the first time, versus the last time when the download meter was almost zero the entire time.
It’s definitely scenery-loading related, though. And I don’t have a problem with a slight graphical stutter here and there, the problem is this stutters the sound at the same time and just becomes an annoying thing after a while.
Anyway, I stopped playing the flight sim for now altogether, I found myself troubleshooting issues more than flying, need a break
Why LOL?
I don’t have this issue either, so I also can’t repro audio stuttering.
MSI MPG X870E Carbon WIFI - BIOS v27, Windows 10 PRO 22H2, RTX 4090, DDR5 2x32GB 6000 CL26 G.Skill
Some of you assume that rolling back from Windows 11 24H2 to Windows 11 23H2 helped. Others say the issue is on the server side.
But I’m wondering - how do you have your network cards configured? They also affect the quality of the connection to the servers, right?
For example, in your network card settings, you could try disabling Selective Suspend and clear the Allow the computer to turn off this device to save power check box.
1 Right-click on the Start button and select Device Manager.
2 In the Device Manager window, expand the Network adapters section.
3 Find and right-click on your network card (e.g., Ethernet or Wi-Fi adapter).
4 Select Properties from the context menu.
6 Disable Selective Suspend and/or Power Saving Mode.
7 Go to Power Management tab.
8 Clear the Allow the computer to turn off this device to save power check box.
Changing these settings may or may not help with the audio stuttering.
It’s also worth checking if disabling XMP, A-XMP or EXPO profiles in the BIOS helps. And if you’ve overclocked your RAM, try reverting to the default speed and timings.
Lol because im a software engineer as well, and when bug report comes to me and i cant reproduce it doesn’t necessarily means it doesnt exist. Its not just one person with the problem, and we aren’t using asobos developer machines to play the game.
I will try the network adapter suggestion thanks . I have already tried everything else, expo, undervolting, windows config changes and so on.
Tbh as i wrote some weeks ago, sometimes seems all is good/better, very next hour or day, same flight same weather, and just full of stutters.
It reminds me of a situation on the Aerosoft forum when a well-known admin suggested that a user’s throttle issue in the CRJ must be on their end since no one else had reported it. Then Aerosoft released the CRJ for MSFS, and the exact same problem appeared - but the MSFS 2020 community was so large that Aerosoft could no longer blame the user. They had to admit it was a bug
I have found that this issue occurs for me when my rolling cache has been maxed out. My resolution to get rid of audio stutters is to delete the rolling cache manually. Once deleted, you can set your desired size within game, and the larger I’ve made it, the less frequent this starts to occur again. I have my rolling cache currently set at 300GB.
This has resolved the issue every single time for me, until my rolling cache again hits capacity.
Annoying as hell - add it to another thing for Asobo to deal with.
That’s interesting what you just said about the rolling cache. I also have noticed a connection between stutters and cache size.
With small caches of 16G default and I seem to get the stutters more quickly. After clearing the cache I seem ok for a little while.
I’ve just set a cache size of 256G and was going to test it tomorrow. Will see if that postpones the stutter fest.
Sure I’ll post back after a bit more testing. I could make it as large as 2TB I’ve certainly got the space. Not sure if this would have some other negative effect though. There’s always something that comes and bites you in the nether region if you try and get too smart with MSFS.
OK an update on my testing this morning.
Firstly a bit of background on my PC and what other software I’m using.
9800x3d processor
RTX 4070 ti super 16GB VRAM
RAM G-Skill 64 GB
C: is 2TB NVme OS and MSFS
D: is 4TB NVme Addon folder and cache file
OS Win 11 24H2
Graphics Driver 472.83 updated this morning
All settings on ultra including clouds with ray tracing no fauna
Frame rate locked at 45 FPS in Nvidia CP
Other stuff running at same time:
FSFO
Say Intentions
FSLTL
Old cache was deleted and new one created 512GB
Two flights YMHB (Hobart) to YSSY (Sydney) and YSSY to YBBN (Brisbane) both in the Fenix A320. Complete reboot between flights.
The first flight went smoothly with not a blip not a stutter of the slightest for even one moment. I increased the sim rate to 4X for around 10 minutes at cruise and no stutter (this used cripple it before).
The second flight likewise until I increased the sim rate when I got a few stutters. These stopped when I went back to normal sim rate.
In conclusion it was a definite improvement and I will continue to run with the large cache file.
Whether or not things revert to normal again tomorrow who knows this is MSFS afterall but at present it has become usable again.
Hope this helps..
Another good example of a post-hoc fallacy. I got audio stutters yesterday evening with an almost “fresh” 256 GB rolling cache—its size is not a factor. What mattered was the busy time of day and the area (London)—I was simply competing for content with many other users.
On the contrary, I believe that disabling rolling cache could actually help, because it isn’t well optimized and could add to content availability latency. Disabling it in MSFS 2020 reduced all kinds of stutters for me, but we don’t have that option in MSFS 2024.
And by the way, I’ve seen recommendations against using a rolling cache size above 256 GB for some solid reasons here. Elaborations in that topic also show that while rolling cache is a good concept, its execution is far from optimal.
I can only report on my own personal experiences and they seem to have some commonality with others.
But yes there must be lots of different reasons for the stutters and there most certainly isn’t going to be any common cure all.
This is currently working for myself at the moment but as I stated above by tomorrow it possibly won’t.
Hi. Me too. Yesterday I turned in BIOS my core tuning option on to level 2. That setting reduces the latency.
I have not tested level 1 and legacy mode.
I also reduced my OC (by turning down my negative curve values from negativ 15 to negativ 10 on CCD0 and to 0 on CCD1. I know your chips has only 1 CCD…but just to inform because after those two changes I have not had any issue anymore with sounds AND the sim ran smooth as silk…it reduced the frame times spikes even more on my 9900X3D
Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes
Provide extra information to complete the original description of the issue:
Follow the below steps to reproduce in the production-level environment (not dev environment or configuration):
In MSFS 2024, adjust rolling cache size to a small value, for example 16GB or lower (if possible). Do not have a rolling cache size above 16GB or the reproduction may take longer. Set off-screen terrain caching to Ultra.
Fly enough so that the rolling cache is completely full.
Once the rolling cache is full, spawn in a different location that cannot utilize the rolling cache.
Open developer mode and display FPS.
Observe as the audio stutters, crackles, and pops, with lost frames. You can see an immediate impact in the FPS counter.
From my testing, it appears the issue is caused when the rolling cache is being overwritten with new data. This process is horribly optimized, which results in FPS stutters and the crackling/stuttering/popping of the audio.
Decided to test this theory. Confirmed to be true and the cause of my audio stuttering and why deleting the cache and restarting resolves it until it becomes full again. Asobo, here is your bug you need to acknowledge and fix.