OpenXR Clicking on Customise Render Resolution causes huge drop in VR FPS

After reading all the positive posts about using the Developer Tools part of OpenXR. I tried clicking on customize render resolution and left it at 100 (also tried reducing to 70) and just doing that caused my VR fps sitting on runway to decrease from 30 fps to 10 fps! I have the use latest preview set to ON. Don’t get me wrong I like OpenXR and the other tips as it has helped me achieve the 30 fps with good graphics in VR but this Customise… setting problem is hard to understand when everyone else is extolling its virtues. I am at a loss.

I don’t know whether it has any bearing on my problem but when I try to run the Demo Scene in OpenXR Developer tools I get an error (see attached screen shot).

Is motion reprojection disabled?

Thax for reply. Yes Disabled.

BYW I am using HP Reverb G2.

Just done some more exhaustive testing. When actually flying the reduction is from 30 to 20fps so a bit less than the 30 down to 10fps I originally reported.

Try unchecking Use the Latest Preview! I have never checked it on and I have been pretty happy with OpenXR

So I thought OK I have never tried with that option unclicked so I tried that today and it worked. OpenXR works perfectly. …so I thought I would try checking the “Use latest preview OpenXR runtime” again and lo and behold it still worked. NO drop in fps!!

I had not made any other changes to the any settings on the PC at all so I am mystified why I got the original problem in the first place. Maybe just unclicking that switch triggered something to happen.

Thanks very much for your help.

It would help to know what CPU and GPU you have. However what I have noticed works good and I do have the G2 is increasing openXR to 130% and reducing the rendering scale within the flight simulator down to somewhere between 70 and 100 depending on your system. I also have game mode off, hags off, motion reprojection off.

Thanks for reply. I got this working OK now. Unclear what caused my original problem, just my misuse probably. :grinning: