I guess i am too old by now. Cannot process.
Iāve had a pleasant time performance-wise in SU2 this build. Everything (Fenix, PMDG etc) minus the ini 350 is running great.
9070XT, 5800X3D 64GB RAM Ultra preset TLOD 100.
Iāve not tried in 2024 but it may still be possible to set values >400 by editing the usercfg.opt file by hand.
What we need to run this sim satisfactory, I think, is a baseline. What I see in each and every discussion about this topic is seemingly random posts about lagging performance, stutters, frame drops, etc. Sometimes these posts have a little information on the system setup, and settings. Most of the time there is none. Just a statement about performance is absolutely useless.
A PC consists of many components, each having their own effect of performance. These components have drivers in different versions. Some work better than others. Then there is a bunch of BIOS settings. Overclocking options of the CPU and GPU. Then thereās Windows versions, and updates. Graphic driver settings. The settings in the sim itself. External and internal add-ons with different versions. If we combine all these variables, how can we expect to assist each other?
So could it be an idea to gather all knowledge in a more systematic way? It has been suggested before, but it does not gain traction, because it takes a lot of work, and people need to step over the emotion that they paid big bucks for their system and just expect it to run smoothly out of the box.
What could we do?
- Split posts on the basis of GPU. so we get one post for the 30x, 40x, 50x, AMD, etc. Titled: āHow to run the sim smoothly on 30x GPUā.
- Agree upon BIOS settings, like no OC.
- All install the same GPU driver version.
- Agree upon the same driver, and windows settings for the GPU.
- Drop any add on, external and internal.
- Fly the same plane. Preferably one tube and one GA.
- Fly the same trajectory.
Compare the results, and from there step by step improve/max the setting.
Otherwise we keep on clogging the forum with complaints that are very difficult to analyse, and solve.
3 Likes
Very sensible and would help Asobo
Whatās the point of it when even a top tier CPU struggles with sustaining 400?
Iām watching this thread while still on 2020, trying to decide when itās time to actually get on the 2024 train. Iām a high end system, stuttering framerate sufferer there. Iāve tried a bunch of tips and tricks, I will say for me the big pain point is lower altitudes and landing, but itās so bad that I have to wonder what magic people with a good experience are using. (edited: Iāve cranked LOD and TLOD way down, like 100 and even under sometimes. I donāt live and die by the buildings / terrain quality but dang, itās just a bunch of boxes at this point).
Asobo needs to help us out here. What do they recommend we do to get a better experience? Does the original guidance (below) still apply? Iām running a 13600 / 7900xtx system. Iām trying to use triple monitor, but Iāve gone down to just 1 & 1 touchscreen to narrow down the issues, without much gain. 2024 was supposed to help CPUs by getting us off main thread. Why are people with 5 year old CPUs and a 1080 getting decent performance and no stutters? Should this game work at some level without frame gen or upscaling? Itās just very frustrating.
Iām running the latest SU2 beta and have spent over 100 hours troubleshooting stutters.
Iāve tried more than a hundred different settings in Windows and BIOS, reinstalled drivers, disabled USB devices, tackled latency issues, and tested every possible solution I could find online related to 9800X3D stutters and X670/X870 motherboards. Step by step, I eliminated all stutters ā except for one that occurs roughly every 10 seconds, regardless of resolution or settings. At some point, I was convinced the issue was a bug in the flight simulator ā until I finally found the cause.
It turned out to be the motion platform software that receives telemetry from the sim. When launched alongside the sim, it introduced the stutter. Disabling the software didnāt help. Even exiting and relaunching the sim without it didnāt fix the issue. Apparently, once the software starts with the sim, it initiates a buggy background session that persists until a full system reboot.
Now I can confirm: SU2 can run butter-smooth. If it doesnāt, in 99.9% of cases, the issue lies in the userās hardware or OS configuration.
My system: 9800X3D, MSI X670E, RTX 5090, 64GB DDR5 6000 MHz EXPO. Below are my key BIOS and Windows 11 settings:
BIOS:
āŗ ReBAR: OFF + Above 4G Decoding: OFF (Removes 90% of all stutters in my system)
āŗ Core Performance Boost: Enabled
āŗ PBO (Precision Boost Overdrive): Enabled
ā¢ Curve Optimizer: ā15
ā¢ Max Boost Clock Override: +150 MHz
āŗ X3D Gaming Mode: Disabled
āŗ CPPC Dynamic Preferred Cores: Frequency
āŗ Global C-State Control: Disabled
āŗ SVM: Disabled
āŗ ASPM Control for CPU PCIe: Disabled
āŗ EXPO Profile1 (6000 MHz): Enabled
āŗ MCLK/UCLK: 3000 MHz (half of EXPO frequency)
āŗ UCLK Mode: = MEMCLK
āŗ Data Scramble: Disabled
āŗ fTPM: Disabled (can cause stutters on AMD systems)
āŗ TMP RNG: Disabled
āŗ Secure Boot: Disabled
āŗ TSME (Encryption): Disabled
āŗ SMT: Disabled (avoids virtualization overhead)
āŗ PSM (Power Saving Mode): Disabled
If youāre using a newer chipset with Thunderbolt/USB4, disable it in BIOS ā it may compete for PCIe bandwidth with your SSD, GPU, or other devices.
All drivers and BIOS are up to date.
Windows 11 (24H):
āŗ Core Isolation (VBS) and all sub-functions: Disabled
ā¢ Check via Win+R ā msinfo32
ā¢ VBS can reduce performance by up to 10% (see: Tested: Default Windows VBS Setting Slows Games Up to 10%, Even on RTX 4090 | Tom's Hardware)
āŗ Windows Defender: Disabled
āŗ Power Plan: Maximum Performance (set via Win+R ā control) + Minimum CPU speed set to 100% (set manually in power plan)
āŗ Fast Startup: Disabled (prevents Windows from hibernating the kernel across reboots)
āŗ No CPU/GPU/temperature monitoring software (e.g., MSI Afterburner, GPU-Z) ā they can cause latency spikes due to polling
Note: These settings force the PC to operate at peak performance, leading to increased power consumption and heat generation. CPU Core parking is disabled, and system security is partially compromised.
NVIDIA App, Pimax software, and pop-out panel tools are confirmed safe to run in the background ā they donāt introduce stutters in MSFS.
All unused audio devices are disabled in Device Manager ā they often introduce latency and stutters. There are usually multiple audio devices in Device manager (AMD HD Audio, Realtek, NVIDIA, etc.); disabled them one by one, keeping only the one actually in use. USB devices can also cause stutters ā unpluged them one at a time to identify culprits.
Stutters arenāt always tied to CPU or GPU limitations. Often, they result from the OS being occupied with background processes. A faulty USB device or unstable driver can cause repeated failures, each triggering logging activity and consuming system resources like CPU, RAM, and disk I/O. This overhead adds latency and disrupts smooth performance.
Modern PCs are complex systems with countless variables. A single incorrect hardware or OS setting can result in noticeable stutters. The combination of countless settings creates many potential sources of stutters, making them highly specific to each system and difficult to eliminate.
Hope this helps.
4 Likes
Depends on your altitude.
I would also suggest to maximize oneās available FS2024 startup VRAM by:
- Turning off Windows Spotlight (the changing themed Windows wallpapers);
- Use a only a small repeatable ātileā for your desktop wallpaper (so no big bitmap taking up precious VRAM)
- Run FS2024 in ā-fastlaunchā mode (this avoids your GPU loading the startup logos and animations);
- delete the long video (so it canāt load into VRAM during the sim boot-up phase).
Ps. Steps 3 & 4 on my system gain me around 1GB of VRAM additional headroom by the time the simās home page has loaded and is ready for a flight.
2 Likes
Interesting tips. Doesnāt the VRAM get quickly reassigned once actual gameplay loads though?
Canāt hurt to try these things, I will get my tweaking hat on again I suppose. 
Thatās very thorough, and I hope it is helpful to people.
āIāve tried more than a hundred different settings in Windows and BIOSā
Ugh - my head hurts just reading that!
Questions - I assume the motion thing is something youāre running, not just general ājust in caseā software for the sim?
Are most / all of those BIOS setting AMD specific? Iām guessing there are some Intel equivalent.
1 Like
Iāve invested a lot of time and money into this whole āmotion-VR-simā setup, so I couldnāt just leave it in a buggy state ā especially in VR, where every stutter can cause physical discomfort or even motion sickness.
1. The motion software is developed by the motion platform manufacturer. Iāve already notified them about the issue.
2. Some of the settings and overclocking tweaks are indeed AMD-specific, but many others can be applied to any system. You can always ask something like ChatGPT to explain each BIOS setting ā it helps to understand what they actually do in your system.
1 Like
Sorry HAGS were on.
I have a X3D system also and many settings are the same. However, Can you tell me why you have set CPPC to āfrequencyā?
Auto or Driver = Windows decides wich cores to use.
Frequency= CPU chooses cores with best potential.
I think it is better to leverage some low level tasks to the HW, not OS.
Iām puzzled by some of your findings, but since I have a 7950X3D and use Process Lasso, some of them may not apply to me.
Iāve always heard that with a single-chiplet design itās probably better to just let Windows manage processes with the Balanced Power Plan, Windows Game Mode ON, and the BIOS mode set to āAutoā (not āFrequency.ā)
Your findings strongly contradict that, and Iām interested for the sake of interest.
One thing puzzles me, though - and it seems like it wouldnāt matter whether one is using a single-CCD or dual-CCD CPU: Hyperthreadingā¦
If memory serves I did some extensive tests that included enabling/disabling HT, and found that enabling it provided a measureable performance increase. Iāll see if I can find those results when I get home. I understand the āoverheadā argument. But disabling the virtual cores seems counterintuitive to me.
Also, do you have hard data showing that ISLC isnāt useful?
We know that in a multivariate environment itās hard to quantify the effects that a single option has. I plan to run some tests tomorrow with HPT On / ISLC Off vs. HPT Off / ISLC On.
Maybe youāre right about it. I need data. Iām fine with going back to HPT if it gives me better results.
I tried running sim with ISLC. No profit. No stutters without ISLC as well
1 Like
Thanks. Iāll post up some hard data with CapFrameX tests tomorrow.
I might find no profit in it as well. Itās a variable I havenāt empirically tested yet.
As a 7900x3D user Process Lasso isnāt really a must i completely got rid of lasso cause of stupid timer and notification to buy it e erytime pc starts feels like someone pointing a pistol on your head. In my case i Disabled game bar HAGS is on HPET replaced by ISLC Rbar is enabled. game bar and windows game mode off. No nvidia app. No msi center app. NO Dlss swapper upadets. Power Plan Ultimate. Ccd0 and ccd1 work together not causing freaking stutters. In other games as well. Most of the stutters come from addons in the community folder and the Vram. Disabling dynamic setting also cause stutters after sometime passes so i set it to 40 with tlod 400 and olod is 200. rt on with shadows 4K Ultra Settings using only TAA. if i see vram is filling then to DLSS quality but not often. The only thing i do differently than most i donāt use FG anymore instead using LS on a rtx4070 as a second gpu. (HP Gpu is RTX 5080) Disabling FG within msfs also saves you some vram and resources from your main gpu.