Jump to content

Recommended Posts

Posted (edited)

After several weeks of testing the Pimax Super, I’d like to share my impressions. First of all: my setup consists of a full cockpit mounted on a motion platform – which makes tracking especially challenging. Some of my observations may therefore not fully apply to a “normal” desk setup.

 


1) Setup with Pimax Play

In short: absolutely straightforward and without issues.


2) Headstrap

The already much-criticized tiny screws are indeed a bit of a joke. On top of that, the headstrap positioning is unfortunate, since its front edge overlaps with the face gasket. Tightening the strap puts more pressure on the gasket than on my head – not a workable solution.

Workaround: By chance, I found out that mounting the strap underneath the face gasket works perfectly. This does not compromise the secure fit or the light seal in any way, but the strap now sits firmly on my forehead and provides solid support.


3) Setup for DCS

With Pimax Play alone, performance is underwhelming even with QV settings. Thanks to Tally’s brilliant video on setting up the Super with QV Companion, I now get excellent results – limited to 72 Hz though. I almost never reach 90 Hz in complex missions, but 72 Hz are rock-solid, except during missions with heavily populated airports.

Important:

  • After every Pimax update, QV Companion must be reinstalled.

  • Using the OpenXR API Layers GUI, always double-check that the right VR APIs are enabled (e.g., QV Companion) and others (like OpenXR Toolkit) are disabled.

 


4) Image Quality

The resolution is simply stunning – even the tiniest cockpit labels are perfectly readable. Colors look vibrant, and night flying is very convincing.

When it comes to Foveated Rendering, the size of the high-resolution area is crucial. If set too small, you’ll notice quality drops in your peripheral vision, especially at night with ground lights. Personally, I prefer flying "only" at 72 Hz with a larger FR zone, which feels much more natural.


5) Tracking

This is where the Super struggles most. From the start, inside-out tracking was unstable for me: incorrect positioning, jittering in the cockpit, and especially deteriorating stability during long sessions.

In my case, the cockpit itself blocks 40–50% of the headset’s visible tracking area. Combined with the motion platform movement, the Super must only rely on the static room environment. My Reverb G2, by the way, never had issues with this.

What actually happened: As long as I was looking straight ahead, tracking was somewhat stable. But whenever I turned my head – left, right, or especially backwards – the headset lost orientation and tracking broke down completely. QR codes on the front walls helped a little, but once I looked away from them, chaos returned. After longer sessions, the problem got even worse.

The solution:

  • I placed QR codes not only in front but also to the sides and behind me (my platform stands in a corner of the room). Suddenly, the headset tracked much better while turning around.

  • I also suspended QR codes from the ceiling in front of the cockpit, so the headset can pick them up just 1 m away instead of several meters further out.

Another crucial step: Before flying, I always scan the entire room with the headset once. Only after that do I recenter VR or calibrate motion compensation. If the headset discovers new QR codes during flight (e.g., when turning around), it seems to re-calibrate mid-air, which in combination with motion compensation led to complete chaos.

Since following this procedure, my tracking has been solid and jitter-free.

Tracking summary:

  1. Place as many QR codes as possible on walls (also sides and rear), and even hang some from the ceiling, close to the seat position.

  2. Before each flight, scan the whole room (left/right, up/down).

  3. Only then recenter VR and calibrate motion compensation if needed.


6) Mura Effect

Until recently, I didn’t even know what “Mura” was. Now I can identify it: a slight “smearing” effect, noticeable when I look at white clouds while my pupils are focused on the near range.

But honestly: in real flying, this doesn’t matter to me. When looking into the distance, I can’t see it at all. When focusing on cockpit panels, the busy background of instruments masks it completely.

It’s comparable to driving on the German Autobahn with a dirty pair of glasses at 250 km/h (which I actually do every day). In theory, there’s a smear on the lens, but in practice you’ll never notice it – your eyes are focused elsewhere.


Conclusion

After solving my tracking issues, I’m very impressed with the Pimax Super. Resolution, colors, stability – fantastic!
Despite the (for me solved) weaknesses in the headstrap and tracking, I would buy it again without hesitation.

Edited by MadMonty
  • Like 2

PC: Asus ROG Strix B650E-F Gaming | AMD Ryzen 7800X3D | Palit GeForce RTX 4090 Game Rock OC | 64 GB Patriot VIPER VENOM DDR5-6000

Input: Brunner CLS-E FFB Base | Thrustmaster Warthog Joystick & Throttle | Thrustmaster TPR Pendular Rudder | WinWing Phoenix MIP (VR) - F16 ICP - PTO2 | VPC SharKA-50 Collective 

VR: Pimax Crystal Super 50PPD

Motion-Platform: Motionsystems PS-6TM-150 | Monstertech MTX

Youtube: https://www.youtube.com/@madmontys6dofmotionplatfor386/featured

Posted

@MadMonty

Thank you for your work!

I want to address one thing.

The Eye Tracking switch in the DCS VR settings does nothing for a Pimax Headset and causes problems with the XRNeckSafer tool.

You should never use this switch if you want to use XRNeckSafer.

To date, I am not aware of any Headset that require this switch.

  • Like 1

CPU: AMD Ryzen 9800X3D, System-RAM: 64 GB DDR5, GPU: nVidia 5090, Monitor: LG 38" 3840*1600, VR-HMD: Pimax Crystal/Super, OS: Windows 11 Pro, HD: 2*2TB and 1*4 TB (DCS) Samsung M.2 SSD

HOTAS Throttle: TM Warthog Throttle with TM F16 Grip, Orion2 Throttle with F15EX II Grip with Finger Lifts

HOTAS Sticks: Moza FFB A9 Base with TM F16 Stick, FSSB R3 Base with TM F16 Stick

Rudder: WinWing Orion Metal

Posted
3 minutes ago, Nedum said:

@MadMonty

Thank you for your work!

I want to address one thing.

The Eye Tracking switch in the DCS VR settings does nothing for a Pimax Headset and causes problems with the XRNeckSafer tool.

You should never use this switch if you want to use XRNeckSafer.

To date, I am not aware of any Headset that require this switch.

Great... After Necksafer worked initially, I now had problems (not needing Necksafer so desperately anymore after a wider FOV). I will try deactivating Eye Tracking in DCS to see if it resolves the current problem.

PC: Asus ROG Strix B650E-F Gaming | AMD Ryzen 7800X3D | Palit GeForce RTX 4090 Game Rock OC | 64 GB Patriot VIPER VENOM DDR5-6000

Input: Brunner CLS-E FFB Base | Thrustmaster Warthog Joystick & Throttle | Thrustmaster TPR Pendular Rudder | WinWing Phoenix MIP (VR) - F16 ICP - PTO2 | VPC SharKA-50 Collective 

VR: Pimax Crystal Super 50PPD

Motion-Platform: Motionsystems PS-6TM-150 | Monstertech MTX

Youtube: https://www.youtube.com/@madmontys6dofmotionplatfor386/featured

Posted
1 hour ago, MadMonty said:

After several weeks of testing the Pimax Super, I’d like to share my impressions. First of all: my setup consists of a full cockpit mounted on a motion platform – which makes tracking especially challenging. Some of my observations may therefore not fully apply to a “normal” desk setup.

 


1) Setup with Pimax Play

In short: absolutely straightforward and without issues.


2) Headstrap

The already much-criticized tiny screws are indeed a bit of a joke. On top of that, the headstrap positioning is unfortunate, since its front edge overlaps with the face gasket. Tightening the strap puts more pressure on the gasket than on my head – not a workable solution.

Workaround: By chance, I found out that mounting the strap underneath the face gasket works perfectly. This does not compromise the secure fit or the light seal in any way, but the strap now sits firmly on my forehead and provides solid support.


3) Setup for DCS

With Pimax Play alone, performance is underwhelming even with QV settings. Thanks to Tally’s brilliant video on setting up the Super with QV Companion, I now get excellent results – limited to 72 Hz though. I almost never reach 90 Hz in complex missions, but 72 Hz are rock-solid, except during missions with heavily populated airports.

Important:

  • After every Pimax update, QV Companion must be reinstalled.

  • Using the OpenXR API Layers GUI, always double-check that the right VR APIs are enabled (e.g., QV Companion) and others (like OpenXR Toolkit) are disabled.

 


4) Image Quality

The resolution is simply stunning – even the tiniest cockpit labels are perfectly readable. Colors look vibrant, and night flying is very convincing.

When it comes to Foveated Rendering, the size of the high-resolution area is crucial. If set too small, you’ll notice quality drops in your peripheral vision, especially at night with ground lights. Personally, I prefer flying "only" at 72 Hz with a larger FR zone, which feels much more natural.


5) Tracking

This is where the Super struggles most. From the start, inside-out tracking was unstable for me: incorrect positioning, jittering in the cockpit, and especially deteriorating stability during long sessions.

In my case, the cockpit itself blocks 40–50% of the headset’s visible tracking area. Combined with the motion platform movement, the Super must only rely on the static room environment. My Reverb G2, by the way, never had issues with this.

What actually happened: As long as I was looking straight ahead, tracking was somewhat stable. But whenever I turned my head – left, right, or especially backwards – the headset lost orientation and tracking broke down completely. QR codes on the front walls helped a little, but once I looked away from them, chaos returned. After longer sessions, the problem got even worse.

The solution:

  • I placed QR codes not only in front but also to the sides and behind me (my platform stands in a corner of the room). Suddenly, the headset tracked much better while turning around.

  • I also suspended QR codes from the ceiling in front of the cockpit, so the headset can pick them up just 1 m away instead of several meters further out.

Another crucial step: Before flying, I always scan the entire room with the headset once. Only after that do I recenter VR or calibrate motion compensation. If the headset discovers new QR codes during flight (e.g., when turning around), it seems to re-calibrate mid-air, which in combination with motion compensation led to complete chaos.

Since following this procedure, my tracking has been solid and jitter-free.

Tracking summary:

  1. Place as many QR codes as possible on walls (also sides and rear), and even hang some from the ceiling, close to the seat position.

  2. Before each flight, scan the whole room (left/right, up/down).

  3. Only then recenter VR and calibrate motion compensation if needed.


6) Mura Effect

Until recently, I didn’t even know what “Mura” was. Now I can identify it: a slight “smearing” effect, noticeable when I look at white clouds while my pupils are focused on the near range.

But honestly: in real flying, this doesn’t matter to me. When looking into the distance, I can’t see it at all. When focusing on cockpit panels, the busy background of instruments masks it completely.

It’s comparable to driving on the German Autobahn with a dirty pair of glasses at 250 km/h (which I actually do every day). In theory, there’s a smear on the lens, but in practice you’ll never notice it – your eyes are focused elsewhere.


Conclusion

After solving my tracking issues, I’m very impressed with the Pimax Super. Resolution, colors, stability – fantastic!
Despite the (for me solved) weaknesses in the headstrap and tracking, I would buy it again without hesitation.

Thanks!

And this pretty much sums up my experience too. Except that I don't use motion platform and really haven't had any tracking issues. And the extra headstrap solution - I gave up mounting it. Too difficult for my fingers. And also during mounting, before I gave up, I found out what you experienced too, that it's too close to/or would touch - the face gasket. I understand that you have found a solution, but my fingers and my patience can't take it...  What were Pimax thinking while making this solution?

I also have followed Tallymouse's video, except for that I didn't care to make DCS launchable from the Pimax Play Menus. I just use the DCS launcher. Also, I never made the even higher resolution shadows thingie that Tallymouse did. I use 72hz too. 90hz is too much, I'd rather have a few more details and some headroom and have everything buttery smooth without any stuttering. I believe that you not only have to re-install Tallymouse Quadviews companion app after Pimax update, but also Mbucchias Quadviews solution? 

The Mura effect, I agree with you on this too.  Because while flying and looking outside out on the sky (where it would be visible) I have to de-focus my eyes to make it appear. And therefore, for me, it is not a problem. I accept that some might have gotten headsets with more mura than mine, but if anyone is complaining about a mura effect that only is visible when you focus on something else than what you are actually looking at - then I don't get it. One would simply be making issues just to make issues. 

No headset is perfect, but the Crystal Super is as close as it can get for me now. Fantastic clarity and colors. Very good FOV. Good head tracking. 

I am waiting for some equipment for my F-16 "cockpit" these days, so until I get that in the mail, I am trying the the Super in other games (which is something I have not done before!). Now it is Skyrim VR with some graphic and user interface mods too. And it is fantastic! And coming from an OG Crystal I think it so nice to spend hours and hours in a game without worrying about the batteries. 

  • Like 2

System 1:  Intel I9 13900K, ASUS ROG Strix GeForce RTX 4090 OC, 32 GB RAM@6000Mhz.
System 2: 
AMD Ryzen 9 9950X3D, ASUS ROG Astral GeForce RTX 5090 OC, 64 GB RAM@6000Mhz. 
Thrustmaster TPR Pendular Rudderpedals. Realsimulator FSSB-RL MKII ULTRA Joystick base + Realsimulator F16SGRH V2 grip. WingWing Throttle with F 16 grip. Moza Force feedback base + Thrustmaster F-18 grip, Virpil F14 grip, Thrustmaster A-10 grip.

VR: Pimax Crystal Super, Crystal OG, 8KX, Pico 4, Quest 3. Buttkicker Gamer Pro. Next Level Motion Platform V3.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...