Same for me. Latest beta running very good here, no crashes or stutters and great performance with latest Nvidia driver.
Well done Asobo!
3 Likes
Same here either using DLSS or TAA!
it sounds weird but i found preset K with originals files perform worse . swapped again 310.2 with preset k from app and perform better . idk . should wait for the official su2 release
Iām using the Nvidia app to change the presets. I no longer use DLSS swapper or anything else.
Iām hoping the official DLSS from Asobo will be even better.
2 Likes
Iāve had several CTDās using this latest driver but not enough to roll back.
The latest one was today. I started a flight out of KJFK with the default Asobo 747, which is a joke to begin with. As soon as I was over the textures headed towards NYC, I experienced extreme stutters and was barely able to get back to the main menu.
Restarted the flight and the same happened. Went to the main menu, selected Working Titles 747, loaded KJFK and immediate CTD.
Restarted the sim, started the same flight again with WTās 747 and it was smooth as silk even flying directly over NYC.
Nowā¦I donāt think this was a driver issue but rather an Asobo issue. So my point is CTDās can happen under some conditions.
The other CTDās Ivāe had were the result of pushing the sim very hard and I wonāt get into it now because it would be extending this post too far. Itās already long enough.
Other than that I am impressed with the way everything is progressing.
Iāve found that Preset J that comes as default in SU2Beta works slightly better with this driver.
So latest drivers installed, nvidia app set to use latest DLSS.
Msfs24 Su2 beta installed
In sim Iām seeing DLSS version 310.1 and preset E.
Having all kind of problems with my 5090.
After troubleshooting for hours, I found out that Nvidia filters makes MS2024 give the āyour graphic card have encountered a problemā (Dxgi_error_device_hung).
SU1 and SU2 beta.
Anyone able to use NV filters with this version?
Looks way better with, imho.
But will try some more and see if it is stable/actually works now 
Thinking about upgrading my 4070 to a 5080 this weekend. Curious if the black display screen issues are still a thing on this build?
I use DP for my monitor connection.
Hi All
This is something i have been monitoring and waiting for a Driver Version that doesnāt gobble more VRAM, and so far no joy.
In summary, every driver after 566.36/46 has been using about 1gig more.
See below :
Latest Driver 572.83
566.36 Driver:
This is on my Alienware M16 R2 laptop with a 4070, 64gb ram.
All Graphic settings the same in both tests along with same location (EGSS)
Any ideas as to the reasoning behind this? Bug?
Running on SU2 beta TA/FSR3 frameGen
thanks.
This driver brought support for nvidiaās Rbar, unfortunately the vram usage increased even more. Disable via nvidiaprofileinspector
exactly. I just tested it in Pyreegue EGPH v2 which is a very heavy VRAM airport.
566.36 got a better performance than 572.83 for my RTX4090.
With 572.83 I just use full of vram
Did you disable enable rebar feature in Nvidia profile inspector? Itās now enabled with the latest driver. Disable it!
No issues with 572.83 with a 4080Super. Most of my settings are on Ultra 3440x1440 with the exception of TLOD and traffic.
Yeag. I just roll back to 566.36 which is much better than 572.xx and I didnāt change the rebar
1 Like
Something is else is up on your setup. No difference for me between 566.36 and 572.83 with VRAM usage.
1 Like
Hi TenPatrol,
Just for clarification, you mean msfs2020 in DX11 mode, no nvidia panel installed?
Yes.
Iāve only installed the Nvidia driver and PhysX.
I didnāt install the Nvidia HD Audio and the Nvidia App.
Well, I will have to try this driver then. Iāve installed 566.36 with no problems (MSFS20, DX11, no Nvidia app), and I feel insecure about trying another driver.
But Iāll give it a try! Will let you knowā¦
Thank you for your time.
Regards
If everything is working fine for you with driver 566.36, then honestly ā thereās no need to change it. No point in fixing something that isnāt broken
But if you do decide to test 566.14 out of curiosity, feel free to share your experience. Always good to compare notes.
I firmly support the āless is moreā philosophy. IMHO, in-game graphics settings is the only way adjustments to graphics settings should be made. Any settings you try to force onto a game using the nVidia App or Control Panel or Inspector typically causes instability and unpredictable results. KISS.
1 Like