One thing about VorpX is it doesn't deal well with programs that have a D3d9.dll in the root folder!
Like AMS got by default and if you use ENB or reshade or even DgVoodoo wrapper.
You can rename the d3d9.dll to something like V3d9.dll and the just hex edit the .exe and change instances of d3d9.dll to v3d9.dll
The motor games do work like that but you you can also get into a endless loop with config so better not doing it.
You are also better of not using AA with VorpX!
Driver MS or SS has no assess to Vorpx display driver anyway and you risk special MSAA will corrupt the dept buffer.
Just make the largest custom resolution your computer can handle is will work as SS in the headset
And no real point of using SteamVR SS ether as it is just wasted.
A real shame it isn't a true SteamVR app.
You are right - many GTR2 plugins use d3d9.dll proxy and that conflicts with vorpx. Hex edit is a great idea. I am trying to create my own plugin, and I found a way to make Vorpx not mess with dlls - "Use alternative hooking method". I do not use ENB and stuff, but I learned this the hard way when vorpx clashed with my stuff.
fi
I also agree with you on SVR SS settings - it doesn't matter, I reached the same conclusion, resolution is what matters the most.
Regarding AA however, I figured something out. I use 8xMSAA + 8xSGSSAA in Inspector. But in order for it to work I have to set AA to 4 in gtr2config, but most importantly, I have to set "Enhance application settings" . If I set it to override, FPS drops very badly. With current settings I found GTR2 looks and runs amazing in Pimax with full FOV.
The only remaining issue is tracking, i managed to achieve good results with EMVA filter, and changing max distance on x, y, z from recommended 100cm to 30cm, it is good, but not perfect yet. Really curious to see Opentrack GTR2 filter and mapping settings from people relying on SteamVR tracking.