You wouldn’t want committing such sacrilege! Unless you only play FS2020 and even then, try running TAA 200 SS100 and let me know about the visuals. Once you get a 3090 or FS2020 optimizations permit, you’ll get nearly same legibility as G2 with much more robust VR experience and device.
Having said this, SteamVR 1.16.3 is breaking motion smoothing but look at the bright side: their release notes are mentioning the application can now pass the depth buffer. This means motion smoothing will be able to project pixels based on their distance, which is what WMR motion smoothing is doing and why WMR implementation is visually better (if not also faster).
Nevertheless, today I’ve tried pushing my 2070S OC (never really done it before): +147Mhz core / +497Mhz mem. Results: no gain I can notice in particular either with G2 or Index. The same pixel shader related settings are depriving me from the same amount of fps as well (maybe not as much but nothing I would really measure from the look of it).
However, I’ve been trying both the Robin and the Longitude over the Hawaii islands and it was great: with my settings in the OP but Terrain LOD 100 (instead of 50), 120Hz/30fps, TAA80/SS128 no reproj. and all good to fly and look in the Index.
Update: been doing a few flights over Hawaii with Longitude and K350 and all excellent with the SteamVR 1.16.2 beta (this evening they’ve retired 1.16.3 which is disabling reproj. by error): 120Hz/24fps/50ms, TAA100/SS128 reproj.
NB: I find TAA100/SS128 giving really great EFIS screens of course but also good external and overall cockpit details, considering it is 2070S “only” I’m quite fine with the perf thanks to reproj. working there. I can’t wait they introduce 1.16.3 back, with the depth buffer support, and see whether this makes SteamVR reproj. much better with FS2020.