Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Pimax Crystal Light Jitter Solution

Featured Replies

On 8/14/2025 at 6:53 PM, Dillon said:

Correct.  In intense areas with clouds, add-on scenery, and Garmin gauges you'll see a problem. 

What's crazy is the G2 never had this problem.😐

Hmmm, have you tried to lower the image quality?

4 hours ago, Calvin-Pimax said:

Hmmm, have you tried to lower the image quality?

Just so I'm sure, what exact setting are you referring to?  I've tried everything with the CL short of running it where 2020 looks two generations in the past (FS9/FSX), in which the headset get's retired.😶 

FS2020 

Alienware Aurora R11 10th Gen Intel Core i7 10700F - Windows 11 Home 32GB Ram
NVIDIA GeForce RTX 4070 Ti Super OC 16GB - Pimax Crystal Light VR 

2 hours ago, Dillon said:

Just so I'm sure, what exact setting are you referring to?  I've tried everything with the CL short of running it where 2020 looks two generations in the past (FS9/FSX), in which the headset get's retired.😶 

Hi, Dillon

What aircraft are giving you the most issues?  I'll try the same models with my own settings when I get a chance and see if I have the same or similar issues or whether I can help pin down where your issues are (performance here is pretty good at the moment but there are some MSFS settings that I steer WELL away from.  I'm flying generally live weather, Fenix A320's, iFly 737, the crazy Maddog, etc as well as fighters and general aviation - including using BATC with reasonable levels of live traffic).    

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

3 hours ago, AJZip2 said:

Hi, Dillon

What aircraft are giving you the most issues?  I'll try the same models with my own settings when I get a chance and see if I have the same or similar issues or whether I can help pin down where your issues are (performance here is pretty good at the moment but there are some MSFS settings that I steer WELL away from.  I'm flying generally live weather, Fenix A320's, iFly 737, the crazy Maddog, etc as well as fighters and general aviation - including using BATC with reasonable levels of live traffic).    

Thanks, AJZip2.  My most intense area where I have allot of add-on scenery is Florida (where I see the problem the most do to where I fly).  Flying up from the Ocean Reef club all the way past the add-on scenery Spruce Creek to land at KCRG can be a jittering nightmare in areas when looking around over the various add-on scenery I have.  The Longitude above 30,000ft you really start to see it with heavy clouds over the state.  The same can be said flying over the LA area down to San Diego (especially SD).  With add-on scenery in such close proximity in SD (Miramar, Montgomery Field, KSAN, North Island, the port scenery for the Navy Vessels, etc), it's all but a no go with the CL.  Last but not least the PNW can be a challenge as that area since an update by Asobo when Canada came out has not been the same since.  If's there a slight issue in 2D the CL is out the question.  This wasn't the case with the G2.😑

Edited by Dillon

FS2020 

Alienware Aurora R11 10th Gen Intel Core i7 10700F - Windows 11 Home 32GB Ram
NVIDIA GeForce RTX 4070 Ti Super OC 16GB - Pimax Crystal Light VR 

3 hours ago, Dillon said:

Thanks, AJZip2.  My most intense area where I have allot of add-on scenery is Florida (where I see the problem the most do to where I fly).  Flying up from the Ocean Reef club all the way past the add-on scenery Spruce Creek to land at KCRG can be a jittering nightmare in areas when looking around over the various add-on scenery I have.  The Longitude above 30,000ft you really start to see it with heavy clouds over the state.  The same can be said flying over the LA area down to San Diego (especially SD).  With add-on scenery in such close proximity in SD (Miramar, Montgomery Field, KSAN, North Island, the port scenery for the Navy Vessels, etc), it's all but a no go with the CL.  Last but not least the PNW can be a challenge as that area since an update by Asobo when Canada came out has not been the same since.  If's there a slight issue in 2D the CL is out the question.  This wasn't the case with the G2.😑

It may take me a little while to delve into the same regions in the same aircraft, but I'll give it a go.  What aircraft are you generally flying and who's add-ons are you using?

 

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

1 minute ago, AJZip2 said:

  What aircraft are you generally flying ?

Silly me - you confirm one of them is the Longitude.

 

 

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

  • Author
On 8/14/2025 at 4:28 AM, Calvin-Pimax said:

So, how was it? Is the tracking still not performing well?

Calvin, 

While it’s way better the issue is still not resolved.  Had 2 other flights now with the same jittering issue but a lot less frequent.  Also noticed if I placed my fingers over the top cameras it would quit.  May go back to tape if this continues as it seemed to not happen at all with the tape over the cameras.

  • 1 month later...

I can report that this is happening for me, too. A little bit last night the first time I used it but nothing major. This morning everything juddered if I was looking forward, but if I turned my head 90 degrees right or left, the juddering went away every time, then came back immediately when I looked forward again. 

 

Ryzen 7 7800X3D/B650 X AX | 5090 | 32gig | Win10 | Pimax Crystal Light

For the record, I cover the lower 2 lenses on my Crystal Light. Those lower two have small round glass lens covers. I do not cover the upper 2 cameras. I am sitting down in a chair not running around the room waving controllers like a sword or bowling ball. So I don't need the 2 lower lenses watching the floor move in relation to me, Because there is none of that kind of movement. But my head is moving. And the upper lenses are pointed at the lit up monitor and reacts to how my head is moving.  

Maybe it would be better if I did the opposite and cover the upper lenses. But months ago the word in the various forums was to cover the lower lenses so that's what I did. Now everybody seems to say to cover the upper 2 lenses. 

Other things can help tracking: better room lighting to the sides and above your head. Lower graphic settings. Tightening up the headset on your head so that it has no wobble at all. I use "CPAP" nose covers (amazon), I removed the built in nose flap on the cyrstal light. This makes for less discomfort on my nose when I tighten down the headset (crank the knob on the back of the Crystal Light halo headstrap). 

5800X3D, RTX4070, 600 Watt, one or two 1440p 32" screens, 64 GB RAM, 4 TB  PCle 3 NVMe, Warthog throttle, VKB NXT EVO stick, Honeycomb Alpha yoke, CH quad, 3 Logitech panels, 2 StreamDecks, Desktop Aviator Trim Panel. Crystal Light VR.

 

The other trick I use is to reduce the size of the MSFS screen window to the smallest it will go on my monitor and drag it to the side (you can't actually minimise the window as, for MSFS, the screen mouse arrow HAS to be in the MSFS window for it to be visible in VR).   This minimises the instances where the cockpit 'follows you around' in VR and other visual issues which result from the cameras picking up the movement from the VR display screen image on your monitor and getting confused - particularly if the room lighting is low.  It's a trick picked up from my VR days in XP-11 where this was (and probably still is) a common issue with VR users.  

 

Ryzen 7 9800x3D @5.2GHz; ASUS X670-P Motherboard; nVidia 4080 (factory o/c); 32G 5600MHz DDR5 SDRAM; Pimax Crystal Light VR Headset; Quest 3 VR Headset

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.