Message for Pimax support:
Asobo hasn’t yet provided a concrete plan for this issue — it will depend on their project priorities. We’re sorry for the inconvenience this may cause.
Message for Pimax support:
Asobo hasn’t yet provided a concrete plan for this issue — it will depend on their project priorities. We’re sorry for the inconvenience this may cause.
Yeah this needs to get a lot more attention than its getting - considering most of pimax’s headsets are targetted towards flight sim and race sim people, they partnered with Asobo for specific release versions of the hmd, Asobo needs to live up to their side of the deal after pimax released the hmd’s to be fair… I really think Asobo is stretching themselves/developers with xbox and ps5 versions, but again they are chasing money the exact same thing they did for pc release with a half baked product that still has enormouse performance and other issues.
So as said for this issue it lies with Asobo to fix it.
I also noticed something else wich is related to Foveat rending but not specific on this software bug.
Recently I noticed that my dashboard was “vibrating” or twitchy (not sure how to discribe it) but it was definitly not still.
I had my setting on 0.5 so it could not be the bug.
Then after some figuring it noticed my lens was a bit dirth on the top from my eyebrows.
I also use some insert for my glasses correction which is (I think) also not helping the tracking of my pupils.
When i cleaned my lens and made sure the eye correction lens insert was perfectly in the spot the problem went away.
So I think we can say, that the active eye tracking can cause vibration in the image.
I hope I don’t dilute our topic here, just a FYI for others ![]()
I’m also getting jitters in the background when using DFR and eye tracking. I don’t seem to get it with PimaxXR runtime (not using OXRTK), but the eye tracking isn’t working in PimaxXR so I’m stuck with FFR. Possibly unrelated but since the last update on the 20th i’m getting horrible distortions in the sky with DLSS mode and better but still there in TAA mode (although the stars are fixed and they look pretty good when DFR is off)
Yeah, I hope Asobo fixes this since the adjustable foveated rendering feature is almost pointless if it only works with FFR since settings lower than 50 without DFR look awful.
Same here, but only the skies jitters
Sky/clouds wobble is a separate issue:
so i got my Crystal super today. I tried a flight in su4-beta ( haven’t tried normal su3 or msfs2020 yet) and i encountered the same problem,the sky in the distance, and the atmosphere shakes/jitters like crazy. its unplayable for me like that. even with absolutely clear skies, its not tolerable.
This is not the issue we cover in this thread, see my post above.
Seems like this bug will be not fixed before the SU4 public release (despite all the votes in this thread) which will make Dynamic Foveated Rendering with Eye Tracked at any value other than default 0.5 unusable, which will mean severe performance hit for DFR users. This is a very bad news.
We will need to find a workaround like the one I proposed higher in this thread, however I was only able to have this workaround working with 0.25, which results in too small foveated rendering rectangle, making it noticeable (0.3 was the sweet spot).
Very bad news that this bug was ignored by Asobo ![]()
Agreed. Other than this work-around, is there even a point to having the adjustable foveated rendering setting other than to frustrate since without using this in combinateion with eye tracking, FFR is just horrible at anything less than 0.5 and I don’t think this issue is limited to Pimax headsets. It’s such a shame since this feature does enable dramatically better framerates in VR that I thought were finally going to let me use my Super in high res mode in MSFS, but I guess not. So back to waiting another round!
I noticed that the issue with the shaking image under 0.5 is in openxr.
In steamvr it is not shaking.
But not resolved (not even logged).
FYI, This topic is tagged with feedback-logged
In the meantime I discovered another workaround parameter set for the Foveated Rendering Scale 0.32 (closer to optimal 0.3, the previous one higher in this thread was for 0.25 which resulted in a bit too small foveated area region).
These parameters are for Pimax Crystal OG (default resolution 4312 x 5102 per eye), will also probably work with Pimax Crystal Light, but 0.32 may be too small for Light as it doesn’y dupport Dynamic Foveated Rendering (no eye tracking). Without eye tracking Light may not be affected by this issue at all.
To apply the workaround you must use OpenXR Toolkit with Ohne Speed mod allowing setting vertical and horizontal resolution in VR separately. Downolad inks under this video by the developer of the mod:
You must run the sim, load the flight, enter VR and enter OpenXR Toolkit memu.
Then you must navigate to System menu and set Override resolution to Custom.
You must then set:
Resolution X (per eye) 4300
Resolution Y (per eye) 5075
You must then set in the VR Graphics Menu in the sim:
Foveated Rendering On
Foveated Rendering Scale 0.32
Whith these parameters there is no image shake.
The original inventor of this workaround was @W1CKL0S who proposed the parameters for SU3:
BTW: As there is another bug in SU4 - World Scale always deafults to 100, you can also use OpenXR Toolkit World Scale in the Apperanace menu to set your preferred world scale.
If I use the SteamVR OpenVR, yeah, the shaking goes away but I only get FFR and not DFR.
With a super ultrawide Pimax, 25% is fine for me. I set it to give whole numbers and it works well. Thanks for the tip.
My problem with OXRTK Ohne Mod is that I get really bad banding in the night sky and mountain shadows and horrible artifacts on the wings. Personally I’m getting a much much smoother experience with it off, using the PimaxXR runtime and dfr in MSFS set to 50. Frame rates are lower but no jitters, no banding, and minimal stuttering.
Pimax Crystal Super user here. If I set it to 25% indeed the image is much more stable, but I still see some slight shaking effects. If it is at 50% it is perfectly stable. At least 25% is tolerable and I get a good fps boost from it.
I hope they fix this soon b/c I want to get away with setting it to 20% without the world looking like an earthquake.