Wow many thanks!!! I’ve just purchased the Pimax Crystal and I was close to sending it back.. with 1.37 it’s absolutely fine =)
I just tried 1.37 with all cameras uncovered and it works very well - no jitter! I’m going to keep working with 1.37!
FYI, covering 2 of the tracking cameras makes the headset drop from 6DOF tracking mode to 3DOF which reduces the complexity of the tracking algorithm hence why it (sometimes) works to fix this issue. This is the difference between 6DOF and 3DOF btw.
1 Like
I am so glad that I read this thread today and it should be required reading if you have a Pimax Crystal Light. I’ve been trying to solve this exact issue for so long and just thought it was the unoptimized sim. Put 2 pieces of painters tape on the top cameras and just had the smoothest flight ever in MSFS2024. Not one single stutter/jitter. Thank you all for posting your findings here. Now that is solved for me. I couldn’t for the life of me figure out why I was getting 40fps but having these jitters. Sometimes it happened all the time and others it was less.
@milavgeek Glad my post helped get your SU3 beta reporting accurate!
Big thanks to @ABF81 and @Spirit539 for their contributions. Reading the links on DoF and I would say for seated VR we only need 3DoF so I will definitely try out the top camera cover up tip and report back.
In the interim, I have been able to complete 2 VR flights with minimal jitters after re-installing the latest Pimax Play Software 1.40.4…go figure
While the links about 6 DOF vs 3 make sense I don’t think that’s what’s going on in this case. I was still able to lean forward and backwards with the cameras covered. Granted I didn’t try walking around but all of the things I could normally do in a VR flightsim were still happening last night.
I’m not losing 6DOF when covering the top cameras. I can stand, sit, lean forwards and backwards, left and right and turn with no issues. The only thing I haven’t tried is walking - which I wouldn’t do with a tethered headset.
When I was working with PiMax support and they suggested covering the top cams, they then had me perform the maneuvers I mentioned above to confirm I didn’t lose 6DOF.
FWIW, having said all that, using PiMax Play 1.37 as suggested has worked very well so far and I now have all cameras uncovered again.
New version of Pimax Play released - 1.41.1
I’ve given it a bit of a test, the tracking jitters and lag are still there in MSFS 2024 but much reduced from the previous few versions. I’ve been able to mostly eliminate them using the “set CPU affinity so MSFS and pi_server.exe aren’t sharing cores” method. Still not as good as 1.37 where it’s smooth and completely jitter free without needing to do anything but it’s a step in the right direction from Pimax.
You the man. This was the solution for me too. Going back to 1.37 seems to have completely solved my tracking issues.
I have also updated to 1.41.1 and seemed to notice an improvement but yes the jitters are still there. Gonna keep testing out 1.41.1 but I will revert to 1.37 if need be. Agreed a step in the right direction from Pimax.
….And back to 1.37 I go. Just did a group flight with the new 1.41 version and it had bad jitter even setting CPU affinity.
Likewise. Fs2024 disabling core 0 didn’t cure the tracking issues for my PCL. However, I really like using Quadviews with 0.3 sharpening - the best VR has looked to me.
Hey all,
Could someone please help me understand how the “jitters” appear? I have a PCL, msfs24, 14700k, 48gb DDR5 @7200, Aorus Master X MB, Gen 4 game drive, Gen 4 OS drive, and an EVGA 3080ti 12gb. I am also using Pimax OpenXR. Latest Nvidia driver, Pimax firmware one back from the newest that just released.
I am just trying to understand what is happening, as I feel like I am not experiencing this issue. Maybe I do not realize it, and I could get smoother performance. Are there any videos showing the issue?
Thanks for any clarification
The simplest way I can describe it is the image in VR vibrates when moving my head around. I am not sure how to record in VR though.
You say your not experiencing this issue - can you confirm what version of Pimax Play you are using ?
Interestingly, I checked last night, and I am on 1.40.1. That does not appear to be current, but when I try to update, it says I am on the latest update.
I am not sure, but what you describe almost sounds like a “low” framerate while moving “fast”.
I am not saying it is the same, but this is why pro gamers in fast paced games strive for the highest refresh rate at the cost of fidelity. The higher the refresh rate, the smoother the picture. At an fps of 30 or 45 or 60 moving around is going to appear somewhat blurry until you stop. As an example pro gamers are hitting 240-360 fps so the blur is minimal as possible.
Maybe this is not what you are talking about. In order to get a smooth, non blurry movement, I would say you would need 120+ fps absolute minimum to achieve that. That’s not happening in vr. Again, my apologies if the issue is different from this, but this is the only thing I am experiencing.
Here is a link to give you an example of how things can be blurry at certain fps as you look around (move). It is a visual, interactive tool. You can change the test parameters to see different results. https://www.testufo.com/
1.40.1 is a version affected by tracking jitters however, if you’re trying to hit 120fps+ on a PCL with a RTX 3080ti GPU then I imagine you’ve got your graphics settings turned way down which has in turn lowered the demand on your CPU and is probably actually benefitting you in stopping the tracking issues everybody else has been having.
The auto-update in the app can take up to 2 weeks to catch up with the latest release as Pimax do a staged rollout. If you want it sooner you need to go to their website to manually download the installer.
While what you say about pro gamers trying to his 240-360FPS is true, it very much doesn’t apply to MSFS especially in VR. It’s much slower paced than any “Pro” game and most of us enjoy the game for the visuals so we turn the graphics settings up as high as our system can handle while still getting an acceptable framerate. And what is an acceptable framerate also depends on your individual tolerance to motion sickness.
I personally have found I can tolerate down to about 25 to 30FPS in MSFS VR but I generally aim for 45 - 60FPS to make the scenery a bit smoother when I’m flying fast and low. I’ve had friends try my rig who couldn’t handle my standard settings and I had to lower the detail to bump the FPS up to 80-90 before they were comfortable. It also changes by game as when I tried VTOL VR I found I couldn’t tolerate anything under 90FPS without feeling sick.
Sorry I wasn’t clear. I cannot come close to hitting 120 fps. I am around 30-40fps with a Crystal Light at native resolution and dlss balanced and settings pretty low. What I meant was the issue sounded like motion blur, but I could be completely wrong.
I am trying to understand what some of you are experiencing if it isn’t motion blur.
Oh, and I just got the current Pimax Play update today. lol.
It’s not an FPS issue. It was happening to me at a solid 45fps. It is a headset tracking issue where the head position in game lags significantly behind the head position IRL. Be thankful it doesn’t affect you but the problem disappeared for me when reverting back to Pimax Play 1.37 as suggested above.
That makes more sense.
It most definitely isn’t an FPS/motion blur issue. To best describe it would be that the game stays smooth but as you move you’re head to look around you view doesn’t pan smoothly but has micro-skips from position to position that feels like stuttering or jittering. If it’s particularly bad you also get lag where the in-game head movement lags behind your actual head movements.
1 Like
Ah, ok, that makes sense. Thanks for explaining further.
I have run into a similar type of issue randomly and found it was because the room boundary was barely going in and out causing weird stuttering until I finally realized what was happening.
Has anyone tried turning off room boundaries or making sure they set the boundaries before they fly to seated and large?
could it possibly be the reflection off of certain objects like a monitor if you are flying in front of your pc and that covering the top cams stops the reflection from the monitor?
just throwing some stuff out there.