I’m currently busy, but I’ll get back to you later this evening (UTC+2).
In the meantime, please don’t make any changes to your system and don’t disable Rebar.
Instead of guessing, the free SayIntentions AI Analysis Tool will give you seriously good recommendations for your individual system. The machine analysis is getting better than human advice. Just my 2 cents.
Another example. It’s really slow. Despite my performance being fine. It’s not smooth for me.
Okay, I think I see your issue. It’s “really slow” despite “fine performance.” Every hardware is different, and where it matters is things like bus speed, cache size, buffer size, etc., and these are things that are probably outside your control. So, when you move the viewport around like that, you are asking the sim to move a lot of data around very quickly, in and out of memory, in and out of the CPU, etc. The trick is to find the sweet spot where your hardware can move everything quickly, and this is not just a matter of having a 5090 and a 9950x3d.
So, here is a two step approach. 1. Select Low Graphics Preset, and perform your test. Is it “fast”? If yes, you know your hardware can move that much data around quickly. If not fast, drop your monitor resolution down to 2k. Repeat. 2. Select Low Graphics Preset, and Select Ultra Texture Resolution. Is it fast? If yes, you can now begin to add higher graphics settings one by one, until it’s “not fast”, then back it off one notch. Now, you may get to “fast”, but you really want more reflections, for example. Go back and Select High Texture Resolution with your higher reflections, and test. If not fast, go back and Select Medium Texture Resolution and test. I use Medium Texture Resolution on my system.
Think of it this way. You have a white screen at 4k resolution. The amount of data in that screen (take a screenshot and look at the size) is much less than a 4k screen with a 3d image with Ultra Shadows, Ultra Reflections, etc. So, you are running at 4k, but you increase your graphics settings until at some point you add just enough data that you hit a roadblock. The roadblock doesn’t stop you, but your computer has to split up the load to get through the choke point, and this is where you see the movement as “not fast enough”.
This is the method that I use to find the sweetspot on my hardware. Fly a few different aircraft when you think you’ve found it because some aircraft will force you back into the choke point due to their level of optimization or the weight of their textures. Let us know how that goes.
PS. Don’t forget to reboot the sim each time you change Texture Resolution.
I’m sorry to say but it’s still the same. I get the same in Low Preset.
- Download NVIDIA Hotfix driver 610.82
GeForce Hotfix Display Driver version 610.82 | NVIDIA - I recommend completely uninstalling your current NVIDIA driver using DDU
https://www.wagnardsoft.com/forums/viewtopic.php?t=5633
If you need help for using DDU, check this GUIDE
- Once that’s done, install the latest NVIDIA Hotfix driver 610.82 instead of the standard Game Ready driver.
- When you launch the NVIDIA app for the first time, make sure to uncheck the option to optimize your games.
- Leave the Global Settings in the NVIDIA app at their default values.
Below, I’ve attached screenshots of my MSFS 2024 profile settings. Please configure your MSFS 2024 profile to match mine exactly.
DLSS Override Model preset
All other MSFS 2024 profile settings are left at their default values.
MSFS 2024 settings
With the above MSFS 2024 settings, the simulator should work fine.
Please do not test with third-party aircraft such as iniBuilds, iFLY, FENIX, PMDG. For testing purposes, use the default MSFS 2024 aircraft, for example the Cessna 172 Skyhawk G1000.
For the best test results, please also test with an empty Community folder. Rename your current Community folder to Community_old and create a new empty Community folder.
Please also test without additional third-party programs running, such as ChasePlane.
Please also be aware that there have been camera panning stutters since SU4. Hopefully, this will be fixed in a future update.
Change your Windows Desktop resolution to 1080p and the Sim full screen resolution to match. Also, you may try switching to 8bit color in the Nvidia App. I know the monitor can do 10 bit, but nothing is free.
Do you actually move that rapidly when flying. Dont mean to be overly crirical.just asking.?.
Hi,
If you see here it’s really bad I reverted back to SU5.
No idea. Tried everything. It feels really slow and laggy when performance seems to be ok? Anything I can do?
@VenomousSteam64 Since you are running the 9950X3D2, is the sim using both chiplets? Even though both have the 3d v cache, I’d think the inter chiplet latency would possibly be an issue.
You could force CCD0 in your bios, effectively turning off CCD1, test it and see how it feels. If it feels better, then we need to look at your chipset driver, v cache optimizer and if both are properly working in conjucntion with GameBar. This will tell us if the Windows scheduler is working. Or Process Lasso could be used to force the Sim on CCD0 and everything else sim related on CCD1. @TenPatrol your thoughts on this idea?
I think we can rule out running out of any DP bandwidth as you should still be within the 1.2 bandwidth limit of 17.28Gbps at your resolution and 120hz, 8 or 10 bit color. On that front, have you swapped to a different DP cable? What about HDMI?
How about the 5090? Running any undervolts? Have you verified it’s running in x16 and not in x8? What motherboard are you running?
I too had this experience when switching to a 7900xtx in Jan 2025. Great performance but it felt laggy like you’ve described and shown in videos, thanks for those btw. I’ve not had this on my 9800x3d/5090 system but, we’ll get it smooth for ya in one way or another!
Swap out the monitor. There’s your problem.
Can I just use process lasso instead of going into bios? I have no clue what I’m doing with this software.
You don’t need process lasso, or any bios tweaks. Your machine is pre-built, so unless the builder made a mistake, you should never need to go in there. They wouldn’t make a sim that required bios tweaks to run properly. The performance numbers are good, but when you move the viewport around the results are not satisfying.
Why are you asking for help if you’re not following the suggestions people have already given you …
It is not recommended for the OP to try fifty different suggestions at once.
Also, there is no need to play around with CCD0 and CCD1 settings. The issues related to this were fixed a long time ago. Process Lasso is not needed either.
EDIT
@WingWarper1 what’s your opinion? The OP has a Ryzen 9 9950X3D2, so I’m curious whether you think playing around with CCD settings is actually necessary.
There is no reason to play around with CCD settings with Process Lasso or the bios, especially with a 9950x3D2 where 3D cache is contained on both CCD’s. Up-to-date chipset drivers and Gamebar software will take care of optimizing the run time execution of the cpu. He can verify the chipset drivers installed as per Win 11 installed apps are the latest with the AMD driver web site. He needs to ensure the gamebar software is up to date via the MS-Store app->Downloads->Check for Updates. He can verify gamebar operation via the Xbox app->click on profile->support->Gaming Services Repair Tool.
@TenPatrol, I think your recommended settings above are spot on and are almost identical to mine (albeit I have a 7900xtx gpu).
From the monitor specs above, it shows only Freesync support and no G-sync support. In the case of a Nvidia gpu, the monitor will almost always default to a generic variable refresh rate technology to smooth things out however it’s not clear if VRR is actually turned on so I recommend that be checked.
Worth looking into… If I were you, I’d investigate the possibility of a synchronization issue between the graphics card and the monitor. Check settings like VSync, G-Sync/FreeSync, and VRR. If possible, try matching your frame rate to the monitor’s refresh rate—even if it means capping the frame rate.
You might try this.
To get perfectly smooth panning with G-Sync you need to restrict your frame rate slightly below your monitor’s maximum refresh rate. This keeps G-Sync active consistently and prevents standard V-Sync from causing input latency or stutter.
NVIDIA Control Panel Configuration
- Open the Tool: Right-click your desktop and open the NVIDIA Control Panel.
- Navigate to Settings: Click Manage 3D Settings in the left sidebar.
- Select the Application: Click the Program Settings tab, and choose Microsoft Flight Simulator from the dropdown list (if it is not listed, click Add and find the simulator’s executable).
- Set Max Frame Rate: Scroll down to Max Frame Rate, turn it On, and input a value exactly 3 FPS below your monitor’s refresh rate.
- Examples: For a 144Hz monitor, set it to 141 FPS. For a 60Hz monitor, set it to 57 FPS.
- Configure Low Latency Mode: Locate Low Latency Mode and set it to Ultra. This syncs your CPU and GPU frames perfectly to minimize lag.
- Set Vertical Sync: Change the Vertical Sync option here to On (and make sure V-Sync is toggled Off inside the Microsoft Flight Simulator in-game menus).
- Apply Changes: Click the Apply button in the bottom right corner.
It probably depends on the monitor… G-Sync on mine only works really well if the frame rate matches the monitor’s refresh rate exactly; at 3 fps lower, it’s less smooth. As for VRR, I’ve never managed to get good results with it.
For me—with my hardware—the winning combination is VRR Off, VSync On (in the graphics driver), G-Sync On, and the frame rate set to the monitor’s refresh rate… but it’s hard to make generalizations…
The Pimax app and GPU-Z show that my Gigabyte Aorus RTX 5090 is running at PCIe x8 instead of x16. I have the BIOS set to Gen5. I don’t know why.
Gigabyte Aorus X870 Master, Ryzen 9800X3D, RTX 5090, 64GB DDR5
Check your motherboard manual carefully. Sometimes, the bandwidth of certain PCI ports is shared between multiple connectors. On mine, the manual states that plugging a component into a specific PCI port—or an NVMe drive into a particular connector—reduces the number of PCI lanes available for the graphics card slot.