Pimax Crystal - Thoughts and Settings

[oCMANo]

Got the Pimax Crystal as my first VR headset.  Wanted to try and get as close to the experience I have with a 4K OLED monitor and Tobii Eyetracker 5, and it is VERY close after a LOT of research and settings tweaking.  (PC Specs in Signature)

Hardest thing to get past was the ghosting/blurring of fast moving objects that go past.  Took a lot of attempts, but now have fast moving objects visible and NOT ghosting.

Using a SteelSeries Arctis Nova Pro, originally put the earphones over the top of the VR headset.  That didn't work so good, lol.  Fell off during rapid head movements.  Fits really well if the headphones are on FIRST, then put the VR headset over the top of that.  Everything stays in place much better! 

First thing off, after getting the headset and to enable the Pimax eyetracking, needed to ensure that the Tobii Eyetracker apps and services were shut down.

End in Task Manager:

Tobii Game Hub

Tobii Experience App

Stop the Service:

Tobii Eye Tracker Generic Service

USB setup:

Use the provided powered USB Hub that comes with the Pimax Crystal.  Read that there were people having issues plugging the USB directly into their PCs.  I haven't had any issues with using the Pimax USB Hub so far.

Ensure you update the firmware before going too far!!!

 

Major Updates with the release of Pimax Play 1.39.01

Updated 5/14/2025

With DLSS 4.0 out now (only on Nvidia Cards).  It works MUCH better now and helps with FPS quite a lot.

For DLSS 4.0 you will need.

Download the latest DLSS DLL from https://www.techpowerup.com/download/nvidia-dlss-dll/

• Copy the nvngx_dlss.dll to your <Drive>:\Program Files\Eagle Dynamics\DCS World\bin and <Drive>:\Program Files\Eagle Dynamics\DCS World\bin-mt
• Keep in mind that every time DCS updates it will put back a older DLL, you will need to re-copy the DLSS 4.0 dll after a DCS update.

Set the Nvidia Global Profile to K

• Download DLSSTweaks from https://www.nexusmods.com/site/mods/550
• Extract to a folder
• Run DLSSTweaksConfig.exe
• Under NvGlobalProfileSettings
• Set GlobalForcePreset to = K
• Save and close.

Again, like the DLL and DCS, a Nvidia Driver update can reset the Global Profile off of K.  So re-run DLSSTweaks and make sure it's on K after a Nvidia Driver update.

Pimax Device Settings:

I'm running 90Hz.  Seem to be able to keep it steady in flight, but will drop into the 70s when close to large cities.

Using Manual Ipd Adjustment now.  Seem to get best results personally with around 66 mm after measuring with the PD Meter phone app.

If you have https://github.com/mbucchia/Quad-Views-Foveated/releases Mbccia's QuadViews installed, uncheck the Pimax OpenXR QuadViews

Depending on how much VRAM your Graphics card has, try increasing the Render Quality.   Going higher makes the picture MUCH clearer as your increasing the headset resolution.

With a RTX 4090 I can run at 2.0 but the FPS is only in the 40s.  Going above 1.0 you had better have 8GB+ of VRAM.

Uncheck the Pimax OpenXR Quadviews AND Pimax Central Priority Rendering.  You want to ensure that Mbccia's QuadView is used that you installed above.

Use the Native Render Quality of High.  Let Quad Views Companion do the up sampling to 125% below.

 

Companion Apps Settings:

Remove/Uninstall:

• OpenXR ToolKit

Keep QuadViews Installed!!!!

With DLSS 4, you can raise Foveate Resolution to 125%.  Tried going higher, but didn't really see a difference above 125.

BE SURE YOU UNCHECK Turbo Mode!!  Crystal Super users noticed it created issues, and actually benefits OG Crystal having it turned off.

I increase transition thickness to take out the sharp edge on the boxes.  Blends a lot better.

 

DCS World Settings:

With the new built in QuadViews in Pimax able to get 90 FPS.  FPS still drop close to the ground into the 70s but generally having great performance.

Updated 5/15/2025

As Above, added DLSS 4.0.  Set it to Balanced or Quality.  Try both as FPS can vary between the two, but Quality WILL look better if you can keep a steady FPS.

Sharpening to 0.  It kills FPS and doesn't help the image.

LOD Switch Factor up to 2.  This helps identification on distant objects and doesn't really impact FPS very much.

SSAO = I use high as I like the additional lighting features.  Didn't seem to impact FPS too much, but if you want more FPS, turn it off.

SSLR = Definitely turn this OFF.  Kills FPS when there's many objects and I really couldn't see a graphical improvement with it on.

If you have fast SSD drives lower the Preload Radius, it'll help the game load faster and you aren't loading objects far away.  SSD will load them in when you get close, might be minor stutter but it's barely noticeable.

System Settings:

5/18 * Drop Gamma down to 1.8.  2.5 was looking too washed out for me so tried 1.8.  Looks WAY more realistic.

GamePlay Settings:

For Pimax headsets, you'll want to use 2 pixel and NOT Auto.  Auto spotting dots do not seem to do anything from my experience.  2 Pixel in Quad Views seems to be noticeable, but not overbearing.

VR Settings:

Changed Pixel Density a bit, reduce back to 1.0 from 1.3.  1.3 was giving around 45-55 FPS, going back to 1.0 made it up to 60-90 FPS.

Pixel Density is a MAJOR FPS killer.  Don't think it's worth increasing.

Check the box for:

• Use QuadView*
• Track the Eyes

Final Thoughts:

Been mostly playing on the 4YA WW2 Overload Multiplayer server and spotting had always been a pain.  I'd really recommend going into the DCS Controls for UI Layer and map the VR Zoom Spyglass to a button.  Makes life MUCH easier and more enjoyable.  Can ID planes and avoid TKs with it.

The cockpits and terrain are amazing looking in VR.  I do notice the foveated rendering and eyetracking 'ghost box' occasionally, but it's not  immersion breaking.

VRs depth of field makes up for a bit of the 'blur' you get coming from 2D.  

At some point would like to see someone make a 'larger' view area so it's not like wearing scuba googles, but for now really impressed with the Pimax Crystal.  Did take a lot of tweaking though to get where I wanted it to be though.

Tried VR years ago (like 2010s) and wasn't impressed at all.  It's come a long way, but still has a ways to go.  Having large screen monitors with 3D depth of field and headtracking would still be my ideal, but for now really enjoying the Pimax Crystal.

Edited May 18 by oCMANo
Updated for Render Quality and Spotting

[j9murphy]

I did some "tuning" with my crystal last night and had the following observations...

- ghosting (I'm defining ghosting as the smearing or the elongating of ground objects when looking at them during a roll or high speed turn) - in my case this was 100% related to frame rate.  if frame rate equals hmd refresh rate then no ghosting, the farther these things get apart then the worse it is.

This lead me to conclude that if I want to eliminate ghosting then I need to make other trade offs.  For me this was dialing back the center for quadviews to 100%, turning off all anti aliasing (no MSAA, DLSS, DLAA ) - for the crystal, I dont see much shimmering or need for AA anyway

This gave me the headroom to get right around 90fps in most scenarios with clear crisp images.  How far that drops in complicated missions and in multiplayer is yet to be seen, but so far i'm happy with the results.

 

 

 

 

 

Edited March 14, 2024 by j9murphy

[oCMANo]

Did a test with the newer versions of DLSS on Balanced.  Looks better with less ghosting, but the distance image is still pretty blurry.  Went back to MSAA 4X and was like putting on a pair of glasses compared to the DLSS.

Until there's significant improvements for DLSS, I'd stick with MSAA and take the FPS hit.

[Qcumber]

2 minutes ago, oCMANo said:

Did a test with the newer versions of DLSS on Balanced.  Looks better with less ghosting, but the distance image is still pretty blurry.  Went back to MSAA 4X and was like putting on a pair of glasses compared to the DLSS.

Until there's significant improvements for DLSS, I'd stick with MSAA and take the FPS hit.

Have you tried manually installing DLSS 3.7? You can then use DLSSTweaks to edit the presets and the scaling. I find that 0.8 scaling is a nice sweet spot. Also 3.7 preset F has a lot less ghosting. 

https://github.com/emoose/DLSSTweaks

[oCMANo]

On 4/23/2024 at 1:04 PM, Qcumber said:

Have you tried manually installing DLSS 3.7? You can then use DLSSTweaks to edit the presets and the scaling. I find that 0.8 scaling is a nice sweet spot. Also 3.7 preset F has a lot less ghosting. 

https://github.com/emoose/DLSSTweaks

I'll have to check that out!  Thanks!

Found out that on my Motherboard (ASUS ROG Maximus Z790 Hero) that if I plug the Primax Crystal USB hub into the Red USB Gen2 Type-A ports the headset seems to be more consistent when connecting.  Had been using the blue Gen 1 ports and was getting a bunch of issues getting connected.  Found this thread which lead me to try it.  

  Hope others find this useful and try the Gen2 ports if you have them.

[oCMANo]

Eye Tracking issue

After noticing some sessions where it felt like I had blurry vision, have noticed that Eye Tracking in a 2nd session isn't guaranteed to be working.  If you play, take a break and let the headset go into a screen off/rest and then pick up another VR session without rebooting, eye tracking will often not work.  Have to go into the Eye Tracking calibrate, verify it's working or not.  If it's not working restart the headset, and check again.  Usually a headset restart will get it working again.

In the habit now of just checking eye tracking works before firing up DCS.

Would be nice to NOT have to do a reset to get eye tracking reliably.  Hope that's something Pimax can fix at some point.

[Chief_Biv]

I have noticed this issue after putting down the headset whilst in DCS. When I returned and woke up the headset the eye tracking was not working. A headset reboot fixed it. At least I have had a couple of flights where I have simulated how the Crystal Light will perform. If Light owners use Quadviews FFR in DCS I think most of them will be happy with it.

 

[Nedum]

On 5/13/2024 at 11:21 PM, oCMANo said:

Eye Tracking issue

After noticing some sessions where it felt like I had blurry vision, have noticed that Eye Tracking in a 2nd session isn't guaranteed to be working.  If you play, take a break and let the headset go into a screen off/rest and then pick up another VR session without rebooting, eye tracking will often not work.  Have to go into the Eye Tracking calibrate, verify it's working or not.  If it's not working restart the headset, and check again.  Usually a headset restart will get it working again.

In the habit now of just checking eye tracking works before firing up DCS.

Would be nice to NOT have to do a reset to get eye tracking reliably.  Hope that's something Pimax can fix at some point.

At first, I had the same problem with the eye tracking. Not every single session, but every new PC start.

Now I play 4+ weeks without any issue or the need of a calibration.

Tested it today and did some "Restart Service" and "Restart Headset", no changes. No need for a calibration.

What I do every day, I "Shut Down" the headset every time I am not using it anymore.

Maybe that's the trick, and only if you "Shut Down" the headset, the calibration of the eye tracking will be saved? Maybe.

[Calvin.Pimax]

On 5/14/2024 at 5:21 AM, oCMANo said:

Eye Tracking issue

After noticing some sessions where it felt like I had blurry vision, have noticed that Eye Tracking in a 2nd session isn't guaranteed to be working.  If you play, take a break and let the headset go into a screen off/rest and then pick up another VR session without rebooting, eye tracking will often not work.  Have to go into the Eye Tracking calibrate, verify it's working or not.  If it's not working restart the headset, and check again.  Usually a headset restart will get it working again.

In the habit now of just checking eye tracking works before firing up DCS.

Would be nice to NOT have to do a reset to get eye tracking reliably.  Hope that's something Pimax can fix at some point.

This issue has been reported to the dev team, and they are investigating why the eye-tracking stops working after some time.

On 5/17/2024 at 5:52 AM, Nedum said:

At first, I had the same problem with the eye tracking. Not every single session, but every new PC start.

Now I play 4+ weeks without any issue or the need of a calibration.

Tested it today and did some "Restart Service" and "Restart Headset", no changes. No need for a calibration.

What I do every day, I "Shut Down" the headset every time I am not using it anymore.

Maybe that's the trick, and only if you "Shut Down" the headset, the calibration of the eye tracking will be saved? Maybe.

The calibration result will be saved. 

[oCMANo]

On a whim, decided to try 4K again with some tweaked Quad Views settings.  Honestly was shocked I could maintain the 65-90fps!  All that said, still getting where Eye Tracking seems to stop working and I have to go out of game and restart the headset.  Hopefully it gets more reliable with some updates.

[Calvin.Pimax]

@oCMANo 

Have you previously filed a support ticket mentioning the eye-tracking issue? If so, you might want to attach the log files to help them investigate further.

[oCMANo]

On 6/17/2024 at 10:47 PM, Calvin.Pimax said:

@oCMANo 

Have you previously filed a support ticket mentioning the eye-tracking issue? If so, you might want to attach the log files to help them investigate further.

Yup have a open ticket and attached logs.

Was suggested I disable the USB Hibernation in windows 11 so did the following.

Open command Prompt as admin

Ran command:  powercfg -h off

Restarted and tried playing.  No change, eye tracking still failed after about 20 minutes.

Also was suggested bypassing the Pimax powered USB Hub and plugging the USB 3.0 cable into the Motherboard directly. 

Connected the Pimax USB 3.0 cable to the USB 3.1 Gen2 port and left the Pimax USB 2.0 cable in the Pimax Powered hub to keep the headset charged.

Also went into Device Manager > Universal Serial Bus Controllers and any Hub items > Properties > Power Management and unchecked the 'Allow Computer to turn off this device to save Power'

After that played a bit and didn't have eye tracking stop.  So far so good, but won't close the ticket quite yet until I have a chance to have a few successful sessions with eye tracking staying active.

06/23/2024

With the settings and the cables connected as described above, the eye tracking stays active.  Not sure what in particular solved it, but the combination of the Power Settings and plugging the USB 3.1 directly into the MoBo seems to have solved it.

Edited June 23, 2024 by oCMANo

[Calvin.Pimax]

Roger that.

Please do not close the ticket, and if the eye-tracking fails again, report it to the tech team promptly.

[Glide]

I reached a new level of smooth with maximum resolution and quadviews on my 3080ti today.  Headset at 90hz, max fps 45 with some headroom left on busy missions.  HAGS off was a surprise from TallyM's video above.  Thanks for that. 

[Calvin.Pimax]

Perfect!

Great to hear that you enjoyed the headset!

 

[Glide]

So, I decided to give Smart Smoothing another test, and it worked very well.

No quadviews, no turbo mode, Low Latency = Ultra, Lock to Half Framerate in PimaxPlay (not the companion App), DFR on Balanced in PimaxPlay, 72hz, Resolution on Balanced in PimaxPlay for my 3080Ti, and graphics tuned so the FPS will be around 40ish without Smart Smoothing.  Also, MSAA for AA at x4 and AF at x16.  Very good results so far in the F16 and Apache with the latest Nvidia driver. 

Edit.  Just did some river racing out of Batumi in the TF-51D with Overcast and Rain.  Perfection.

Added Quadviews to the mix.  Very stable at 120hz. 

Edited August 18, 2024 by Glide

[oCMANo]

Found this chart and adjusted QuadViews.  If your eye normally only has full focus in about 18 degrees, then tried lowering the vertical and horizontal focus size to 25% down from 33%.  Got about a 8-12fps increase and didn't notice any vision degradation when in eye tracking.  Playing mostly in the 4YA WW2 server and don't really have any issues spotting planes (of course using VR Spyglass Zoom for distant spotting).  Recommend trying anywhere between 18%-30% for focus size, 25% seemed to be my sweet spot.

Edited August 18, 2024 by oCMANo

[Aapje]

@oCMANo

The eye tracking in current headsets is not of the quality that it can actually track that accurately. Nor can it necessarily adapt quickly enough when you move your eyes.

So this is unlikely to be a good idea for everyone, although we all differ, so it can work for some people.

[oCMANo]

4 hours ago, Aapje said:

@oCMANo

The eye tracking in current headsets is not of the quality that it can actually track that accurately. Nor can it necessarily adapt quickly enough when you move your eyes.

So this is unlikely to be a good idea for everyone, although we all differ, so it can work for some people.

That's the reason I wouldn't go down to 18%-20%, but 25% seemed to be a good middle ground.  Anywhere between 25-30% is likely a good compromise for FPS vs focus.

[WipeUout]

Hey @Calvin.Pimax, I am still using Pimax play 1.18 with my 8kX.  I tried 1.21 a while ago with bad results but I see now that there is even a 1.26 version?  Should I switch or it is only for the crystal?

[Calvin.Pimax]

It's compatible with all Pimax headsets (except 4K), so feel free to give it a try.

[j9murphy]

On 8/18/2024 at 10:37 AM, oCMANo said:

That's the reason I wouldn't go down to 18%-20%, but 25% seemed to be a good middle ground.  Anywhere between 25-30% is likely a good compromise for FPS vs focus.

This actually helped me out quite a bit..  I found I was able to get enough overhead to stay around 90fps most of the time, which meant I could increase my HMD refresh from 72hz to 90hz (Motion smoothing doesn't work for me and having a frame rate lower than the refresh rate means ghosting which I try to avoid).   I found that by lowering the focus size I could offset the shimmering at low values by turning on DLAA.  DLAA doesn't work on the DCS menus, so I still a little shimmering on those - but once I start a mission the shimmering in the transition is gone.  So my new sweet spot (crystal, 4090, 13900k) is...

• PD 1.0
• DLSS Off
• DLAA On
• Anti Aliasing 16x
• no MSAA
• HMD 90hz, Max Res
• no motion smoothing
• Quad Views: focus size 20%, offset -10, foveate res: 125%, Peripheral: 5%, Turbo Mode: On

This lets me crank up most of the visuals and keep the frame rates above 90 in most instances.  very nice.

[oCMANo]

Updated the original post for the new Pimax Play version 1.33.01.01 that has the OpenXR built in.  You will need to remove a couple of the stand alone apps, but keep QuadViews Companion.

[oCMANo]

Updated and able to get 120 fps now with Anti Aliasing off.  Seems to help spotting with it off.  Items are more recognizable at a distance and not all 'muddy' due to the smoothing.

[oCMANo]

Figured out a app to measure your IPD on your phone.  Used a app "PD Meter" and was able to finally get a good measurement.  Thanks to Refracted Simulations on YouTube for the idea!