I must admit I always use the latest nvidia studio driver as opposed to the game ready ones.
I just find them generally a bit more stable and solid.
I guess this wouldnāt affect your problem here anyway as the latest studio is 452.06, so most likely exhibits the same issue.
Iād refrain from using anything like this with any simulator, even if it gives some boost, and even more with FS2020. This is interfering with the simulator own internal task scheduler and might cause problems with add-ons.
Here are a few reasons I wonāt be recommending this kind of tool:
- FS2020 is now using a sandboxed SDK for which most non-aircraft 3rd party code could run as external .exe, therefore in giving more priority to FS2020 youāll give less priority to 3rd party code and possibly also break synchronizing optimizations which were implemented in the 3rd party code.
- FS2020 will use DX12 which is opening threading optimization opportunities at the simulator code level which could be impaired if the user is artificially changing the process priority and/or threading affinity.
And fundamentally, what process lasso is doing could be done directly within the FS2020 code by the developers and if this tool proves any benefit, I believe youād rather post your detailed analysis to Zendesk so that it benefits all of us.
Having said this the simulator is running quite well already given the richness of its graphics and the number of live objects/states it is managing. There are still a number of optimization opportunities Iām sure and Iām also certain they will come in due time. For example in VR Iām noticing more load with the 2070S whenever I increase some settings (Terrain LOD or buildings HIGH) whereas Iām observing much lower load increasing clouds or texture size (comparing both changes from the same initial conditions/settings). When comparing these changes and the CPU/GPU sync/stalls with fpsVr I tend to think the bottleneck is in the vertex shader and the number of vertices to process, whereas the pixel shader is more comfortable. There might be an optimization opportunity here in using SPS (single pass stereo)* so that the video card is handling 2 vertices transforms at once. Maybe Iām wrong though because it is only empirical and maybe they are already using SPS or other similar techniques, I donāt know.
*SPS has its share of problem too and seems to be even wrongly rendering with the G2.
Iām sure you right, Iām not an expert, as you might be, I just experienced that FS2020 with CPU utilization is more soft to me, there is much less frames dropping while flying. Maybe it wonāt be effective after the future updates, but in this stage at VR seems to be a bit better at me.
@gyurmak I wouldnāt pretend being an expert or better than you in any way, Iām just sharing some technical details about these topics and someone one day might prove me wrong as well
Btw Istead of spending hrs of trying to get better performance - I like to have the beta access before the official releaseā¦I couldnāt wait till 23thā¦
I have, sorry for my bad english. I have, thats i likeā¦
I was wondering about these and never took time to try out. Do you find any particular difference in games performance generally (not just FS2020)?
Just posted:
[Update 03DEC2020]
Changes:
- update Win10 Graphics Settings and comments (Game Mode OFF).
- update SteamVR Settings and comments (78% instead of 80%).
- update VR Graphics Settings and comments (different strategy with a baseline and 2 custom adjustments).
- update VR Traffic Settings and comments (slightly lower values).
- added Sound Settings and comments.
- corrections, additional comments and cleanup.
Since Iāve created this discussion Iāve flown much more hours in various conditions and settings and I came to new conclusions and decisions regarding how the best I can maximize the experience. This is an interesting journey which I hope is also helping you along the way!
Iāve always felt (and this is not backed up by empirical evidence!) that thereās not much gain in any driver upgrade once theyāve settled in after card releases!
As Iāve got a 1080Ti, itās old and well-tested now so Iād rather have something which is predictably solid, than constantly updating to the latest iteration which might have issues. The studio driver just tends to be the most bug-free from the last 5-10 versions.
I guess you might gain a few FPS here and there from having particular game-ready versions but itās not worth the hassle in my mind unless youāre getting a clear 5+% improvement
Just wanted to thank you and send some apreciation for sharing your suggested settings.
Although I donāt use the Index but Quest2 and G2, your Nvidia settings make a big big difference for me. They have significantly improved my overall experience - hopefully you will get your G2 soon On the G2 the sim is just incredible (once the settings are tuned)
I just made one minor change to your CPL suggestion: Low Latency Mode on Ultra seem to work even better for me personally (also in-game settings are different as I run a 2080TI)
Thank you for your kind words! Last time Iāve tried FAST or ULTRA the former gave me better results in 2D and 3D, but it was we a previous NVidia driver version. Iāll try again and see how it goes now on my test system, thank you for the heads up!
Iāve just posted an update at the top you might want to read!
Great updates, thanks. Just to clarify: I own MSFS steam version, but Iām using the HP reverb, so I see that I have no usual āper application settingsā that I can set for msfs (not on the list). Does that mean that I basically canāt try any of your steam SS methods?
Iām using FS2020 Store version and it doesnāt appear in the list of SteamVR games. However while in game you can open SteamVR settings (either in HMD or from the Win32 app window menu) and change it. Once you do it is permanently saved in the steamvr config file:
C:\Program Files (x86)\Steam\config\steamvr.vrsettings
Here is what my entry looks like:
"system.generated.flightsimulator.exe" : {
"disableAsync" : false,
"motionSmoothingOverride" : 2,
"resolutionScale" : 140
},
Awesome, thanks!
Us lot using WMR natively donāt have any per-application settings. We have a few options in the WMR portal to change the resolution/performance but none give you the granularity that SteamVR does. Itās a bit all-or-nothing. Either itās going to render (the G2 in my case) at the equivalent of SteamVR 100% SS (3000px-odd hor. and ver.) or something considerably lower.
Our only option is to use the Render Scaling setting in-game and TAA to smooth it out for us.
You still could could use SteamVR OpenXR instead:
Yeah I asked someone in another thread about that, maybe Iāll try it.
I just find that WMRās Motion Reprojection (at 30Hz) is very very good, so donāt want to lose that.
Iāll try SteamVR and see how it goes. It might be worth it to gain more minute control over resolution and therefore performance!
Iāve just added a new comment in the first posts above: