The driver seems fine (data point of a single flight in FSS E190 from EPKK to EHAM), but I can’t say it did anything for the stutters seen in SU5 which are still just as bad as ever when I set my TLOD and displacement mapping to where they were in SU4.
If there is no reply, it simply means that nobody wanted to answer or the question was overlooked or that the answer is already known to everyone, including the person who asked. If you want, you can reply there on how to set DLSS in MSFS 2024, i.e. how to switch it from TAA to DLSS. Every bit of help is valuable and I don’t always have to be the one replying - sometimes I leave it for others to step in, since I won’t be on this forum forever.
In this topic, I suggest focusing on the latest NVIDIA driver or older versions instead of discussing why no one replied in another thread.
How exactly did you test that driver?
For example, what did you set your NVIDIA Control Panel or NVIDIA app “Power management mode” to? Was it “Normall” or “Prefer maximum performance”?
Also, did you install/use NCP or the NVIDIA app or were you running just the driver clean without extra software?
But it’s your thread, isn’t it?
Anyway, it’s tiring, I will just stay with the driver I have.
I think I have it set to “normal” or “balanced”. I’ll have to go check.
Using Nvidia App with default sim set DLSS preset. Using DLSS frame gen 2X in game.
In the NVidia App it’s two clicks to roll back t oyour previously installed driver, super easy.
Yeah I get that feedback pretty consistently, albeit from a small number of users, that I should use a more complex airplane and jet and big airports, etc. The key to testing to me is consistency. Granted I should probably use the C172 G1000 as that adds CPU load, but I’ve been on an Islander kick lately.
In any event, I know literally every stutter on the route that I fly, so I know what’s new, what’s not, and what’s not there that used to be. And I do use pretty high settings, third party and Asobo airports, and no frame gen. And the data gets recorded and compared. I used to just eyeball the drivers, because smoothness is all I care about.
For a while I did ATL-DFW in the Fenix A321 and recorded the data, presented it all… and nobody watched. Plus it took me a day and a half to get the video recorded and out. This way I can get the information out quickly and I’m confident that the testing is more than sufficient.
Thank you!
Gladly! I should probably also say that for that to work you’d probably need to update via the App, which you can do on the Drivers section. The cool thing is that if you don’t like the driver, at the bottom of that section it shows your previously installed driver - just go over to the right, click on the 3 dots and select reinstall, done. One of the great features of the App in my opinion!
Great, so I can just test the new driver without worries.
Seems to work pretty good here.
Just 3 flights: 2xFenix and 1xPhenom.
FPS much the same, but generally smoother is my initial feel.
5090, 7900x3d, 2D 4k, 64gb, fps locked 40 3xFG → 120fps, dlss-dlaa, preset M.
I will never understand why security leaks in graphic drivers are completely ignored when it comes to the question if somebody should update the drivers or not.
Every few months serious security leaks are found in nVidia drivers with ratings > 8. When a browser or Windows has security vulnerabilities of this magnitude, no one hesitates to install an update. The assessment takes into account the likelihood of an attack, which means that a vulnerability in a graphics driver with a severity rating of 8 is just as dangerous to the user as a vulnerability in a browser with a severity rating of 8. But when it comes to graphics drivers, this is completely ignored. I will never understand this.
IDK mate 
While data numbers can be useful, relying on them to optimize this sim is a Fool’s Errand, lol! Smooth, stutter-free performance is still the most important thing imho.
Everyone’s systems are different, as is their flying style (areas and aircraft flown) so what works best for some, may look terrible to others. Case in point is the 610.47 driver which seems very good for some, but not so good for others, like myself (mainly fly heli’s in VR low/slow in cities, with lots of rooftop hopping), compared to 596.49. Still, good to watch your vids mate. Thanks for sharing them. Cheers.
The new driver has been amazing for me. Rock solid 60 fps with all ultra settings at 4k dlss quality framegen. Sitting on a runway at KSEA in a pmdg 738. Tlod 200, olod 200. Not a single stutter on takeoff roll.
Ryzen 9800x3d
Nvidia 4090
64gb ram
Win11 insider beta
Well all OK on my 5080 with the new driver. You may recall I use a standard test flight from Reno to SFO and it is the best I have seen with 5.1. Flight is entirely on autopilot… just saying.
Hi,
no its not about FrameGeneration, this is not what i look at. Its about “how flat the frametime curve is”… is it a “flat” line or not
This is the current driver compared to older ones… the blue is the current… and it shows what i feel. its smoother, the best ‘feeling’ so far. And it does not matter if i check it on a 240 sec apporach or a 15 min approach. As long as they are compareable, and they are as its always the same flight, the same condition, the same airplane and the same untouched (no camera movement, no nothing)
You never mentioned that before. What you said was:
Based on that, it sounded like you were testing the driver itself. If the test is actually focused on frametime consistency with Frame Generation enabled rather than the driver alone, it would be helpful to mention that in the original post. That way we can avoid misunderstandings and make sure everyone is discussing the same thing 
Thanks for all the work you put into this - much appreciated.
Your findings very much back up my personal experience of these drivers - very, very smooth indeed. Glad to see most others in this thread are finding the same. The best drivers for quite a while for both versions of MSFS (as well as across the board, frankly - well certainly for my 4080 anyhow).
Yesterday, I decided to compare the performance of the two latest NVIDIA drivers 596.94 vs 610.47 vs the older 577.00 driver. The reason is simple: for quite some time, something about the newer drivers hasn’t felt quite right to me.
Each driver was tested three times, with each individual flight taking approximately 22 minutes. This means I spent about 1 hour and 6 minutes per driver, resulting in a total of just over three hours of testing overall.
It may not seem like a huge sample size, but I believe it is still sufficient.
Test 1.
Test 2
Test 3
These results align with what I have been observing for a long time, namely that something feels off with the newer NVIDIA drivers.
There is a clear and noticeable performance advantage for driver 577.00. Both 596.94 and 610.47 perform very similarly to each other, but both are noticeably worse than 577.00, which is not surprising based on my previous experience.
What further supports my conclusions is NVIDIA’s own changelog, where they acknowledge a potential issue: “Prefer Maximum Performance” Power Management Mode may not be applied correctly [6007998].
Personal experience also matters here. If the latest driver works fine for you, then there is no reason to change it. It is also worth remembering that every system behaves differently, so what works well on my setup may not necessarily deliver the same results on yours.
Below you can find my MSFS 2024 settings, my NVIDIA Control Panel settings (without using the NVIDIA app) and the hardware specifications of the system I use for gaming.
Gaming Rig
- PC Case Be Quiet Light Base 900 FX
- MSI MPG X870E Carbon WIFI - BIOS 1A8
- Virtualization - disabled
- Re-size bar - enabled
- PSU ASRock Phantom Gaming 1600W
- Ryzen 7 9850X3D
- AIO Arctic Liquid Freezer III 420
- 64GB Ram CL26 DDR5 6000 2x32GB G.Skill
- AOC Agon Pro AG326UD
- MSI MAG 271QPX E2
- ASUS ROG Astral RTX 5090 OC / 577.00
- USB HUB
- Logitech X56 H.O.T.A.S
- VKB Gladiator NXT Evo Space Combat Edition
- Honeycomb Alpha Flight Controls XPC Yoke
- Logitech Flight Rudder Pedals
- Airbus EFIS Winwing
- Airbus FCU Winwing
- Airbus MCDU Winwing
- Boeing 737 MCP Core Flight
- Boeing 737 EFIS Panel Core Flight
- Boeing FMC/PFP 3N Winwing
- Thrustmaster T300 RS racing wheel
- Sound Blaster X5
- Sound Blaster Katana v2
- 4xNVMe // 4TB for MSFS2022/2024
- 1xSSD
- 1xHDD
- Windows 11 PRO 25H2