I just got back into fiddling around with the new Pimax software, eye tracking, etc. and I’m having some confusion on what the current recommended runtime should be, especially for dynamic foveated rendering.
The Pimax client seems to want “Pimax OpenXR” for the runtime in order to make settings for Quadviews. Is there any benefit to these settings?
Currently I’m still on “PimaxXR”, with FoveatedRenderingScale=0.25 in UserCfg, TAA and experimenting between 1 to 2x upscaling in the sim’s settings menu.
Also, do the settings in the OpenXR overlay do anything? Toggling them on or off doesn’t seem to make any difference I can tell. Eye tracking is working even if it shows off there.
With TAA at 1x I’m getting about 40-55 fps. At 2x it looks to be about 32 - 50 fps. It still feels smooth at 2x although the visual benefits don’t seem as much as I expected over 1x.
4090
Crystal OG
Thanks Calvin!
Although I’m very still confused between “PimaxXR” and “Pimax OpenXR”. If I remember correctly, PimaxXR is mbucchia’s runtime for Pimax. Which is also confusing because “Pimax OpenXR” sounds more 3rd party.
Pimax content also mentions “PimaxXR” specifically.
But the PimaxClient really seems to want me to reset the OpenXR Runtime to “Pimax OpenXR” runtime.
I’m also getting really good dynamic foveated performance when editing the UserCfg to tweak the settings in MSFS. But I don’t have any ability to tweak in the PimaxClient. How are the PimaxClient settings related to the UserCfg?
MSFS2024 QuadViews (foveated rendering) settings are native in the sim and the Puma software has no way of controlling it, other than setting the base resolution.
Pimax native OpenXR runtime (btw based on Matthieu’s runtime heavily) is maintained, while original Matthieu’s PimaxXR is not. This is why I switched to Pimax runtime, with no adverse effects - one component less in my system.
So, none of the reported performance drops? Although those reports were from a while ago. I suspect Pimax could have just looked at Matthieu’s code on github.
Pimax Play’s OpenXR implementation is largely based on PimaxXR (1st version was nearly a carbon copy afaik), however they did remove certain parts, such as the asynchronous running start, which may cause performance issues for some (but perhaps alleviated if you use OpenXR Toolkit Turbo mode). They’ve also added new stuff since, I don’t follow closely but for example Crystal Super eye tracking will only work with Pimax Play’s OpenXR.
I use the Toolkit primarily for the screenshot function. After my flight, I crop them at 16:9 (captured with one eye is great) and they come out very clear. I have tried the Nvidia screenshot and MSFS screenshots but they look terrible after cropping.
Would you know of another way to take screenshots with the same clarity as your toolkit?
Thanks
I’m trying to switch the runtime to Pimax OpenXR but when I switch I can’t get VR to start in the sim. This even after restarting everything.
As soon as I switch back to PimaxXR the sim will launch.
If you are using OpenXR Toolkit, consider disabling it or resetting parameters to default/safe.
I can get PimaxXR to switch between itself and SteamVR just fine, but the Pimax client just won’t rest itself now. 
I modified the registry as follows.
HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1
C:\Program Files\Pimax\Runtime\PiOpenXR_64.json
With that VR in the sim launches but the Pimax client doesn’t seem to recognize it has been set. Perhaps it want’s the 32-bit version?
Also, setting safe mode in OpenXR Toolkit fixed the launch issue. I know Matthieu doesn’t want us using it anymore but it’s hard to give up.
After resetting OXRT to default parameters (as the startung point) I should work normally and you should be able to set the parameters you wish.
OXRTK still prevents VR from loading for me, even after resetting to defaults in safe mode.
There is definitely something buggy going with setting the runtime in the Pimax software. It could be related to the original Crystal. The Light and Super seem to get the most focus these days.
@CalvinPimax , are there any know issues setting the runtime through the Pimax software? As you can see below, it says that it is set but is acting like it is not.
Also, should we use the 64-bit or 32-bit version?
I’ve been having all kinds of issues now. I used to have the PimaXR runtime working along with OpenXR and DFR.
Eventually I got the Pimax app to set and recognize the “Pimax OpenXR” runtime. I recalibrated eye tracking. However, eye tracking is no longer working in MSFS. It looks terrible without the eye tracking!
Before calibrating the FR point was stuck to the upper right. After restarting everything and running calibration, MSFS is stuck on the center at least.
I’ve also tried going back to my original configuration and eye tracking is not working there either.
I’m quite puzzled. 
***** edit *****
I did a full removal of everything VR related and wiped out anything in AppData\Local. That seems to have resolved the eye tracking problem. I’m still curious as to how I had PimaxXR+OpenXR working with DFR.
My Crystal OG works fine with Pimax OpenXR, OpenXR Toolkit (no DFR set here) and native MSFS2024 Quad views with eye tracking (DFR). No registry hacks, just setting Pimax OpenXR runtime in PimaxPlay.
Everything is working now. Even OXRTK with the pimax runtime. I just had to wipe everything VR related out and reinstall.
I kind of hated doing that as I like to understand what was actually wrong.
But it really showed how critical eye tracking is with quad views. Stuck in the center and it’s so easy to see the box. Outside the box it looks like garbage. It’s about impossible to notice once tracking is on.
This issue isn’t specific to the OG Crystal—it affects all product lines.
We were able to reproduce it when OXRTK is enabled and the runtime is set to Pimax OpenXR, where MSFS VR fails to activate.
The devs are looking into it.
Would you recommend switching from a PCL to PC OG then? Performance wise. I think about selling my PCL for an OG to achieve better frame rates.
Oh man, tough call. If you asked me 6 months ago, I was probably thinking swapping for the PCL, lol.
But I’ll say now that MSFS has tunable dynamic foveated rendering that eye tracking is mandatory for me. Anything else won’t make the list now. I went from fussing with DLSS to having everything be faster, sharper, and smoother than back in 2020.
I just don’t know if everyone experiences dynamic foveated rendering the same. I just can’t see the low-resolution parts, even if I try.
How do you disable OpenXR Toolkit without deinstalling it?
Hi,
You can disable OpenXR Toolkit here:
