Overall these seem to give a reasonable performance vs graphics quality.
Key points to note:
Turn off Windows Hardware Accelerated GPU Scheduling in Windows 10 Graphics settings (under Display/Graphics Settings), but you can leave the Variable Refresh rate on.
In Vive Console - do not use motion compensation (leads to screen tearing). Also try and avoid using Performance Priority Mode (it smooths but leads to fuzzy virtually unreadable EFIS and text).
Turn off the VFR Map icon in the MSFS toolbar settings (a bug that make the flight plan disappear when switching to VR)
Map your VR view controls to bindings first!
Also make sure you are using the latest beta versions of both Steam VR and Vive Console.
Thanks for sharing youre setting for the Cosmos. Although I can not go as high as 150 pixel-density, the rest is similar.
Did you gain anything when using the betas of Steam VR and Vive Console? I get Artefacts within my left lense when using the beta console. So had to switch back to stable.
My betas seem to work OK, though I had managed to install the wrong one initially! I am still getting some CTDs occasionally though, so might revert to the stable one if that continues to see if it helps, (though difficult to tell if its the VR or something else as am using ORBX scenery and the Working Title G1000 mod).
Now it is working well I may monkey some more with the SteamVR resolution slider vs the VR render scaling one in MSFS2020 to see if I can improve text clarity a little more.
Bernie
P.S. Also just discovered that ORBX Kelowna (CYLW) is the cause of a reoccurring CTD, so some progress!