Hi Thino! After about 4-5 years using VR on my Quest 2, i think i'm starting to understand something of this world. This thing you said is wrong. The performance boost gained using vrperfkit_v0.3 is very impressive and no, you don't need Stem VR to use it.
Now I will try to explain what I have learned so far:
1) Both Steam VR and Oculus Software have a setting to set themself as "Default Open VR environment". This means that every Open VR application will be launched with what was last set as the default Open VR environment (sorry but now I don't remember exactly where these settings are).
2) The rendering resolution scale: This is important to understand. You have THREE (TWO if you don't use Steam VR) places to set this and everyone of them take as INPUT the OUTPUT resolution of the one that is under them in the stack.
If you use a Quest 2, those are in order:
- Render scale in Oculus Software.
- Render scale in Steam VR.
- Render scale in VaM.
Let's say that your device resolution is 1000, this means that if you set render scale to 0.8 in Oculus Software, 0.8 in Steam VR and 1.2 in VaM you will have:
1000 x 0.8 (done by Oculus Software) = 800 -> 800 x 0.8 (done by Steam VR) = 640 -> 640 x 1.2 (done by VaM) = 768
Then... the vrperfkit will take this 768 resolution as the rendering resolution target and will render at a lower resolution to then apply it's upscaling techniques.
Now... here comes the hard bizarre part: If you set the render scale to default In the Oculus Software, it will show you that the slider is set at "1.0". But... this is not real... don't ask me why but to set the render scale to the actual real resolution of the Quest 2, you have to set the slider to the max.
So... here are the steps to have the best results with a Quest 2:
1) Set the Oculus Software as the "Default Open VR environment".
2) In the Oculus Software, set the Resolution Scale to the max.
3) Launch VaM and set it's resolution scale to 1.0.
4) Play a bit to note how VaM run with this settings.
5) Close VaM and install vrperfkit_v0.3 (copy the files in the zip into VaM root folder).
6) Launch VaM and admire the miracle...
NOTES: vrperfkit_v0.3 is not perfect, indeed, it's very buggy atm. Sometime will happen that VaM will crash on launch and... it will also take down the Oculus Software Service and Quest Link. This will take you back to the Quest 2 Home but... you just have to wait for the service to restart, re-enable the Quest Link and try again.
I hope this can help...
Edit: And don't forget to disable ASW (Asynchronous Spacewarp) in the Oculus Debug Tool!! You have to do this every time you launch the Oculus Link.
P.s. Maybe i'll put all of this into a guide...