Just took the 465.89’s for a spin and bust my buttons… not bad!
Most drivers I’ve tried - post 457.30 - have disappointed in one way or another until now. As suggested the Nvidia release notes I tested with HAGS ON (Hardware-accelerated GPU Scheduling). But Game Mode OFF.
For the record, my system, and usual tests settings are:
System:
~ Alienware R11
~ RTX 3090 24GB (not overclocked)
~ I9-10900KF (3.7Ghz, not overclocked)
~ 64GB Ram (XTD’d at 3400 Mhz)
~ Oculus Rift S, OTT SS at 1.5, ASW at 30Hz (27.5 FPS lock on Rift S) running Oculus V27.0.0.45.587
MSFS Settings (VR):
~ All graphics settings at ULTRA (or their max)…
… except Ambient Occlusion at medium (my personal preference)
~ Rendering Scaling: 100
~ Terrain LOD: 100
~ Object LOD: 100
Customary Aircraft & Airport:
~ Asobo C172
~ KUKI, Ukiah, CA, Runway 33, Few Clouds, Midday
(Ukiah is photogrammetry, surrounded by standard Bing textures and Blackshark AI autogen.)
~ Road Traffic, 100%
~ GA Traffic, 100%
~ Airlines Traffic, 50%
With the above configuration(s), I flew around Mendocino County for about an hour or so, landing and taking off in various fields and open meadows, back to KUKI and back out again, sharp turns, low passes, switching cameras, and then loaded some heavy rain and flew into and back out of it a few times. With OTT set an 30Hz, I was pleased to see I stayed smoothly locked at 27.5 FPS most all the time, with only the standard unavoidable occasional hiccup or minor stutter – BUT – no worse than (and maybe even a bit better!) performance than our beloved and trusty 457.30 drivers.
Will definitely hold onto the 465.89’s for a few days and run them through their paces, but this initial test looks very promising. Remember, HAGS HAS TO BE ON THOUGH… I tried it with HAGS off and sure enough, it was stutter city. I fly VR only, and it’s is a bit refreshing I must say, as it’s the first driver in months that didn’t get uninstalled in favor of the good ole’ 457.30’s.