@cymantix I believe resistance is futile (can’t resist)
Having said this, the in-game fps window is only giving you the game view of performance, not the VR view. I’ve been doing a lot of investigations and I can assure you the reasons for lower than expected performance on the hardware is not just the simulator code, but also and maybe as importantly the VR driver.
I’d suggest you review this for example:
NB: it is with SteamVR prior 22nd release but it is showing some really interesting intra and inter frame behavior which could be attributed to WMR OXR driver or FS2020 itself. Alex Vlachos videos are explaining the technique they had to use in SteamVR in order to “trigger” the right moment for submitting and this is “voodoo science”.
Otherwise you are right: these are base settings giving you a comfortable experience for a given hardware (listed in the post). Should you have a more capable hardware, please do raise the settings you’d like. My personal short list is increasing Terrain LOD to 150% first, Clouds to HIGH second, which are probably the only 2 worth considering from a pilot perspective. The rest is mostly cosmetic yet agreeable.
As for the VSync you are right. However, there are oddities I’ve commented on in “My VR Settings - Index” discussion. For example, I was at one point capable to pushing to 42fps with the Index. In setting the headset to 90Hz, the implementation (FS2020? SteamVR?) was locking the HMD to 30fps (the closest to 90/3). In just changing the headset to 80Hz (you can with the Index) it was automatically locking to 40fps and it was really neat. However sometimes it was instead locking to 22.7 (90/4) even if set to 80Hz. This is typical to me of a mis-predicted “present view” timing.