MadMonty

I had the same problem ending up outside the cockpit. Try scanning your whole room by turning left / right / up / down with your headset on and then recenter VR and then start flying. That helped me to stay within the cockpit (even on a motion rig). Seems like Pimax is adapting tracking / positioning when capturing new objects in the room. Therefore it seems mandatory to make a scanning process before flying...

Understood - I have not been aware that Eye Tracking Switch even makes a difference with the Super, but using Necksafer I just found out that having it OFF resolves any Necksafer problems with a blurry sight

Yesterday, I had my first flight in a campaign in the dark of night and unfortunately have to confirm that the Super is causing problems here. I have a bright corona around the aircraft, sometimes the aircraft disappears because the headset seems to dim on its own, and when I go into the cockpit, everything is gone until the headset brightens up again. It almost seems as if some kind of glare function is integrated. The sunrise looked disastrous and completely unnatural. I've only just discovered this thread and will try to change the settings tonight. If necessary, I'll have to revise my positive review of the headset due to its lack of nighttime suitability...

OK, did some testing yesterday... My problems with Necksafer had nothing to do with the Eye Tracking Switch in DCS. In my case Nechsafer API has to be in #1 rank within the OpenXR API Layers GUI, otherwise it won´t work. So my API-order is: #1 Necksafer API #2 Motionsystems API (for motion compensation) #3 QV Companion API Only than I get Necksafer to run without a problem. However - the Eye Tracking Switch in DCS makes a big difference in Necksafer: Having it ON I have a very blurry sight when looking back. It seems that the Foveated Rendering Area stays at my actual head positioning of 110° while my view snaps to 160° and therefore is out of the high rendering area. Having it OFF it works perfect, the Foveated Rendering Area also snaps back to 160° while I am only looking at 110°

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.

An excerpt from my review thread on tracking: 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 can 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: 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. Before each flight, scan the whole room (left/right, up/down). Only then recenter VR and calibrate motion compensation if needed. So for me, placing QR codes very close together across the entire field of view (including to the sides and behind me) solved the tracking issues, even though I’m on a moving platform!

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: 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. Before each flight, scan the whole room (left/right, up/down). 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. A quick addendum – the Pimax Super does seem to have a (software) issue, there are a few problems at night. My tests above were all done in sufficiently bright dawn conditions, which is why I didn’t notice it earlier. Still, I was able to make a bit of progress:

Have you tried Tally‘s setup guide? The only way for me to get good results (despite having no crashes using only Pimax Play).

I definitely don't have MURA with my Super. Initially, I had a grey veil caused by QV that looked like a rectangle on the higher resolution area, but disabling SSAO got rid of that too. In other posts, users initially mention MURA, but say that you get used to it and it goes away over time. Maybe, at the beginning of my 50s, my eyes are simply too bad to see it anymore. From this perspective, MURA will disappear over time in any case.

I had my first longer session with the Super and DCS after my summer break yesterday. Tracking on my platform was fine at the beginning but gradually got worse as the session went on. I’ve read somewhere that taking off the headset can worsen tracking results, and I can confirm that from my own experience. So, tracking starts out fine - but once the headset is taken off a few times during a session, things deteriorate, and I just don’t understand why. Overall, I’m still happy with the Super. The tracking issues aren’t bad enough to make the headset unusable, but they are definitely quite annoying.

I have the Brunner CLS-E FFB-Base, which is not as good as the Moza. But I am still waiting for the new WinWing FFB Base, which will be (regarding the force) the next ultimate FFB Base. Seems there is a delay in development, but they still keep 2025 as the release year...

That´s the 1 Percent missing

Why are u using MSAA as AA and not DLSS?

Don´t use hand tracking, but I am sitting on a quite exiting platform. Link in my signature. The leap from an office chair to a platform is comparable to the leap from 2D to VR. VR with a platform is 90% like real flying, and with a seat belt tensioner it's already 99%

Thank you - will try tonight...

I am completely smooth and super happy with the Super

After summer break, I upgraded to 1.41.2, reinstalled QV Companion (just as a precaution) and got everything to run smooth again at 72Hz without having to change anything. Tried PP Quadviews (while deactivating QVC), but I had big problems only achieving 35 FPS and a lot of stutter. But one thing bothers me - pressing volume + button on the Super does not open the Pimax Menu anymore, just keeps increasing volume. @Calvin.PimaxDo I have to activate it in the settings or is this mandatory feature gone?

Try switching SSAO off in DCS

Well - in my case it eliminated the problem completely... It seems that everyone has very individual problems with PP and the Super.

Turn SSAO off and it‘s gone

You can select the size of the „sharp“ area via Quadview companion or as it seems now also in Pimax Play. Everything outside the area is a bit blurry. But since the Super has eye tracking, there is simply no chance to look directly at the blurry area, since the sharp focus area moves with your eyes. So it is a trade between size of the sharp focus area and PC performance. I only noticed the blurry area at night when lights of the cities went from crispy sharp light to very blurry ones at the edge of my focus area. So I increased the area while still having good performance and have no problems left regarding any blurry effects.

I am s new Pimax Customer und fortunately one of the early Super owners. I was worried about Pimax hard- and software quality as also a (very) bad customer service since the forum is full of bad post regarding the service. From my perspective, the hardware is just perfect (ok, smallest screws in the world for headstrap, that‘s the only complaint). Software runs very well and is being developed step by step with some nice improvements. Tracking has some issues, but that will for sure be resolved and lighthouse faceplate will be available in a few month. I habe found quite fast and helpful responses by @Calvin.Pimax within this forum as also within the one ticket I opened in support (regarding a grey veil being visible). For sure there are some frustrated customers, I just wanted to point out that there are also very happy ones lile me around.

FOV is of course way better than the G2, to be honest I have hoped to experience an even wider FOV, but of course it is quite good. I will definitely try the ultra wide, as soon as possible.

Running the Super with a 4090 without any performance problems. Neither I have any reliability problems. Switched from a G2 and the Super is worth every cent,

Have you tried 72Hz with a FPS setting of at least 120 FPS in DCS? I can´t run on 90Hz, my rig does not have the performance for it.