Maybe for 20XX, but not compatible with 30XX:
Did more testing here and on my 2070S 457.30 still better than the new one. Fresh install probably helped. I will try 451.48.
That’s the one I have been using for a while and it works good sim still has issues but its more stable than the latest.
Let us all know how it goes!
Ok. Just tested. Fresh install of 451.48. This is night and day on my system (Quest 2 + 3600x + 2070s + 32Gb). Incredible how much smooth it is running. I am locking fps at 30Hz ASW, so not sure if there’s a gain in fps, but frame times are more stable. Tested only on a short flight on the Bonanza and even with glass instruments it was running really well. Clouds on HIGH, Terrain LOD at 100. Reflections on HIGH. Resolution is 1350x1350 (using oculus FOV multiplier) - 100% render scale + TAA. No SS.
Oculus is set to 90hz and recommended resolution (1624x1648 on my system). It is running so good now that I don’t want to turn off the PC to avoid problems. hahaha.
Driver made a difference for sure. Also, I am not sure if this new MSFS update or the Oculus v25 also had an effect. I have a feeling that V25 is less taxing on the CPU. Seems to leave more Headroom, but can’t confirm.
This sim in VR is absolutely incredible… when it works. Really rewarding to finally have this running well… not only playable, but very enjoyable now.
Tip for Quest 2 users is to keep your Headroom higher than -100. On my system, - 70 works really well. This will keep ASW stable.
Thank you for all the details! I’m looking at the NVidia release notes right now (see below).
It looks like:
- 451.48 was the first one introducing support for DX12 Ultimate.
- 452.06 has specific optimizations for FS2020.
- 456.38 was the first one introducing FrameViewSDK.
This is a game monitoring SDK included in GeForce Exp.*
It is interesting to see what they are adding over time!
PS: it took me some time formatting this but it gives direct link to all the drivers and this is very convenient!
PS: I’ve changed the list because the previous links were for the non-DCH drivers.
*I never install anything else than Core Drivers and PhysX and I’ve no particular knowledge about this one, except it is a new framework and some have reported uninstalling it via Control Panel > Programs and Features, is helping reducing stuttering issues. It looks to me this is the SDK GeForce experience is using to auto-tune the game settings automatically, and unfortunately not like you’d want. In effect, the auto-tune feature is considering FS2020 performance from a NVidia card perspective and is adjusting FS2020 settings to lower what is taxing the GPU, but as a pilot, you could end up looking at a very smooth and high fps FS2020 with blend and featureless scenery in the distance…
I am new to VR and to Quest 2, could you explain what is “headroom” and where do you set this?
thks for this work, but i guess this list is for 2070 series from Nvidia ?
for my 3070 the list and versionning is different…
should i try the first one in the list ? or make several trials maybe…
You might want to scroll this discussion up a few post and find my links to the “recommended” drivers.
NB: this is the same list, but it is clear older drivers couldn’t support in advance cards that would be released at a later time… This is why your list starts with the first driver for your card.
I have noticed a huge improvement with only the Oculus V25 update, much smoother, I haven’t touched my NVIDIA drivers. It’s so much better I don’t even want to touch my drivers in case it breaks!!!
So is VR better in this 461 driver? Or should I still keep the old one (416, from may)? I’m on a 1070 because I ordered My 3080 twenty minutes too late back in september
I highly suggest not going to any driver other than New ones for anyone running 30X0 series card. I finally decided to try these drivers a week or so ago, and my experience has never recovered since… Even going back to the newest drivers… Last week I gave up on trying anymore… Spending way to much time trying to get things running, I had it acceptable before I made the change… But now, its just not even in the ball park. (stutters, very min stutters, but enough that my brain hurts)
Hopefully this new driver when released gets me back on track.
Thks again, but by going above i find two reco :
- one for 457.09 through a link to another post and specific to 3070, but set as min driver version
- and one u mention just on top of this page which is 457.30 but not sure for which CGU model
i guess i will give a try to 457.30
Just curious if you did a clean install (unfortunately resets all profiles if you have them for a given game ) or not. One would think that you could back to where you were if you did a clean install. I rarely do a clean install but I would if I had to.
I’ve updated the post in order to more clearly show the recommendations and why:
Make sure to also read the Tip because this is probably what is making a lot of fps results differences as well.
Yes, And I redid all the settings again. Of course I had so many settings changes can’t be sure if I did them all.
Edit: Just tried the settings in another thread with a guy that basically has the same system as me, only I have 3080 and he has 2080Ti… And I’m back in to acceptable frames. using the latest Nvidia drivers just released.
It is definetely running much better after v25 update.
I’ve finally took the time to test 451.48 and it is running with less fps than 457.30 and similar stuttering pattern found with all the 460.xx drivers (less strong but stuttering nonetheless).
For now I revert to 457.30.
PS: this is good intel overall with all of us testing these drivers. I’ve pointed to some of these discussions to a developer working in the WMR team and I hope they will improve further and pass the information along.
I am thinking that the Oculus V25 is what is giving the biggest improvement. Not sure. I will keep the current configuration as it is working well enough… Quest 2 is really tricky as the Link encode/decode process adds another layer complexity that messes with latency, gpu and cpu usage.
I’m not sure about AMD cards, but if this “link” is encoding in H264, the NVidia cards have a hardware encoder/decoder onboard and this runs on dedicated silicon. The only impact there would be is having the encoder waiting for the frames and then the link waiting for the encode, but hopefully this kind of processing should be streamlined in the video card easily.