Does reshade works in VR mode then ? I was under the assumption that it only works in 2D.
I always have my nVidia settings left at Default for MSFS since VR first appeared, except for capping FPS to 60 for the Menu otherwise my GPU is screaming (literally…) at full blast for no reason whatsoever!
Sorry for not responding earlier unfortunately I don’t own VR so I’m really not sure, I should have mentioned all settings were tested on 2D only.
No problem. Thank’s for your answer.
Same settings I had except I did not have performance set at max. I changed it just for giggles, but since SU5 practically has my GPU pegged at 100% as it it, I don’t expect to see any difference.
Then again, in the spirit of it’s as much voodoo as it is science, can’t hurt, no?
Here is the topic about the NVidia CPL Anisotropic bug, and several side-by-side showing that FS2020 settings are doing what they are expected to:
PSA: NVidia Anisotropic Bug: in-game setting disabled (was: Some tests on Texture Resolution and Quality) - Community / General Discussion - Microsoft Flight Simulator Forums
Here are my latest Index setting for SU5 HF1 (for HF2, just change TLOD and OLOD back to 100%):
My 2070 SUPER VR settings and suggestions (Index - SteamVR) 🟢 - #547 by CptLucky8
And some more comments:
PS: I’m not done yet adjusting for the Index, thus I’ve not tried the G2 with SU5 HF2 yet.
Oh I can’t wait for this!
Thanks for this super detailed post as always!
Oh, so waiting for your (CptLucky) updated recommendations for the G2!!!
I suspect both the latest FS2020 settings I’ve posted a week ago with the Index, and the OXR settings I’ve posted for the G2 months ago, would most likely be good starting point to experiment with.
Nvidia control panel at default, no issues.
What I’ve found is that even if set at default, this doesn’t mean it is at default! (at least for the anisotropic settings). This really requires clicking the “RESTORE” button to reset everything and to be sure it is.
NB: I’ve had the same kind of bug a few months back, when I was using 457.30 but did try a newest one just to see whether it would be better. This was one of the newest driver with the “limit background window fps” and I’ve set it to 30 for FS2020 so that during loading, it wouldn’t take 100% GPU if I selected any other window. When I reverted the driver back to 457.30 in just installing over (NVidia recommended way), I realized the background window fps limiter was still set even if this older driver wasn’t offering this feature yet!
I think you’re right that all settings doesn’t revert to default unless you do a ”reset”.
Another thing that I find, but it might be placebo…
If messing around with MSFS VR settings in order to test and find a smooth experience I eventually get a lot of stutters and need to dial back some values. This doesn’t really seem to restore the settings (even though under settings they are at the ”right” level) - it still stutters and is jerky. However, if I click ”default” under VR settings, and then set my higher values back and clicks apply/save it runs better.
Anyone else find this? Or am I imagining things…?
Clean install of MSFS and updated Windows and OXR. NVidia is 471.41. G2 + 3090 + i9 (5.3GHz). Nvidia CPL settings as per CptLucky8 of April (I think). Render settings 100/100. Repro off. Visual settings Ultra. Smooth flying and clear detail looking forward through windscreen. Looking out of side windows its jittery: maybe 2 or 3 frames. As discussed above, changing Aniso does not seem to have any effect on image and menu boxes have slightly jagged edges. Cockpit images clean and readable but could be a bit crisper for my liking. On the plus side, have ramped up render scaling in FS to 200. At this level no CTD but frames must be less than 10/sec. However at 150 seemed to be quite smooth over London. And load times are much quicker. So far its looking pretty good that a lot of negatives have been addressed. But still need to tweak and fine tune, presuming of course that there are no bugs. Continuing to experiment and will give these suggestions above a go. WIP.
Edit + 2hours - CPL set to default then relvant functions to Application to Decide. At first not a discernable change so I reset FS settings to default. Cleaned it up nicely and getting smooth and clear. (Cub at 1000ft) Render scaling 100/100. raised most settings to Ultra and sliders to 200. Left aniso and Tss at default. Still good. tried raising ansio and tss but seemed to degrade image. Also increasing render scaling >100 degraded clarity somewhat. Image not as good as 2d 4k but I think i’ve reached the limits of the G2 as far as clarity is concerned.
There does seem to be something weird going on… As per the thread below, some have found that ultra graphics settings are only applied after going down to low, hitting apply, and then going back to ultra. There is also suggestion that some settings are only being applied by the graphical Preset slider, and cannot be adjusted by the individual sliders (note we don’t actually have a Preset slider in VR!)
I have been unable to successfully locate a list from Asobo that shows No Fly, Don’t use, un-recommended Apps. Can you post where I can find this please?
that’s interesting…will give that a shot!
Game changer for me was someone on the forums suggested downloading the Nvidia Studio driver, changing from the Gaming driver. Immediate huge difference with NO CTD’s anymore. Also changed aircraft to Legacy from Modern. Very smooth now and most of my peripherals work again.
(i7-10700, RTX3080, 32G)
Sure. You can find it here, though it has many more suggestions aside from the “Don’t use these 26 specific apps”.
I tested a bunch of settings in the nVidia CP that people claim can offer XYZ today. After a number of hours I came to one conclusion… it’s not worth bothering. As far as I can tell, if there are any “gains” to be had, they are so small that I can’t detect them with my eyes or my performance monitoring.
I’ve set everything back to default except FPS limit, which I set to 30 to lower GPU usage in the menus. (Which I always use in 2D mode.)
Wow. Discord is on that list, as is PrecisionX1 and MSI afterburner…and Windows audio service! Lol.