I just saw that, downloading it now
Probably the best comment of this thread.
4 Likes
Yeah but it does help with the temperatureâŠat least that is what I noticed on my rig.
Iâd still choose TAA + scaling over DLSS since it doesnât come with blurriness, ghosting and temporal artifacts.
1 Like
I see people mentioning removing old versions of drivers before downloading a new new version.
How do you do this? I normally just download via Geforce Exp
1 Like
When you install the new driver if you click on advanced options, there is an option to perform a âclean installationâ which will remove the old first.
I also do not install the GeForce Exp app.
2 Likes
Ok so you suggest downloading the drivers directly from Nvidia site?
Does it still give you the clean install option that way?
On a GTX1650 Iâve seen far more stutter using DX11 so far 
This driver made a massive difference to my DLSS performance and DX12 smoothness. I was playing without the driver earlier today on a very similar flight at the performance has shot up. Almost a third higher or more. Itâs seemingly removed a lot of the DLSS blur as well (on quality).
1 Like
for dfriver uninstall, i use the DDU tool.
Itâs better than a clean install. When used go first to windows safe mode. (reboot while hold the shift key and then start windows in safe mode 
3 Likes
I use DDU.
Thank you for this!
1 Like
Asobo does not need to turn on anything. There is no âOn switchâ. Once the sim detects whatever there is in the driver that was needed, the allocator is working.
Furthermore, there was no difference between GRD and Studio as many stated.
2 Likes
Here are my results in VR
Honestly the simple but effective way is to just download the driver from their website.
Just make sure to select custom install during the installation and there you have the options you need (only driver, and clean install).
Its honestly very straight forward and easy.
2 Likes
A little thing could be. At least I donât get a graphics card warning under DX12 with GRD.
But as so often, it may have been on the server side. FS is inscrutable here. 
Just finished my first flight with 517.48, and Iâll post my thoughts and results here (without having read the prior posts, so sorry in advance if I repeat stuff).
From the release notes I could see two sections relevant for MSFS:
2.4 Whatâs New in Version 517.48 WHQL
2.4.1.1 Game Ready for Overwatch 2
This new Game Ready Driver provides the best day-0 gaming experience for Overwatch 2. In addition, this new Game Ready Driver offers support for the latest releases and updates including the addition of NVIDIA DLSS technology to Microsoft Flight Simulator.
3.1 Fixed Issues in Version 517.48 WHQL
[DirectX 12] Microsoft Flight Simulator may display texture corruption after extended gameplay [3762763]
âŠ
This is a bit different to Studio 517.40 which only had this:
3.1 Fixed Issues in Version 517.40 WHQL
[DX12][Flight Simulator] Potential image corruption [3722516]
âŠ
My test flight was in the analog Caravan from Oslo to Bergen, Norway. Weather was quite heavy, with dense cloud layers, light rain and icing conditions. Flight time was just a bit over 1 hr and I was running the following settings:
4K DLSS quality | ultra | TLOD 200
I was running ReShade, the Map enhancement mod and Norway DEM10 mesh which very well could have affected my fps.
Performance was pretty much the same as with the Studio driver Makes me wonder if that also had the DX12 optimizations for MSFS in place? Hmmm.
Anyway decent performance, not amazing but it usually isnât in heavy weather. Generally smooth but some stutters here and there. Nothing major. Excellent CPU multithreading like with the Studio driver, and both the 12900KF and 3090 was getting a decent workout.
The screenshots were taken at cruise FL150. You can see from the HWiNFO grab that all the cores (and threads) are being used fairly evenly, with an average CPU utilization of 62%.
Benchmark for the whole flight:
- Average framerate : 45.0 FPS
- Minimum framerate : 6.9 FPS
- Maximum framerate : 69.7 FPS
- 1% low framerate : 28.6 FPS
- 0.1% low framerate : 13.6 FPS
Not a bad result but the 1% lows didnât manage to stay above 30. 0.1% lows are also quite low. This explains the stutters.
I have a AMD 3900x, RTX2090ti, 32GB system and a 5120 x 1440 monitor.
After installing this driver, the resolution defaulted to 2560 x 1440 and every time I attempt to set the resolution to 5120 x 1440 I get a CTD.
Iâm going to roll back the driver to see if this remedies the situation.
Has any one with a 32:9 5120 x 1440 monitor experienced the same?
1 Like
Yep, this is the Same Method I Used, via Safe Mode, thereâs also a checkbox you can enable within the DDU Settings to prevent windows from Downloading a Generic Driver upon Re-Start. Options-> Advance Options at the very Bottom you will see (Prevent Downloads of Drivers from âWindowsâ Updates" when âWindowsâ search for a driver for a device}.
Once the PC Re-Restarts I still do a Custom Install of the new Driver and select Perform a Clean Install via the Nvidia Driver Installer.
NOTE: Performing a clean Install will Reset all previous Nvidia Control Panel Settings so make sure to make those changes again when finished.
1 Like
You are massively CPU limited.
With 13GB of Vram usage and only 75- odd percent clock use.. your cpu-dependent elements are limiting your fps.
Turn LOD down and Ai âeverythingâ off ⊠then compare.
Your GPU should be doing 100 percent.
This is assuming you are running at 4K ⊠2160p.
Try to get a balanced setting where the GPU/CPU Llimited indicator in Dev Mode display is constantly flicking back and forth.