MadMonty

It´s not a bug, I had the same problem. They have integrated a new setting in the menu. Look in your settings and tick "Controllerless mode"

Try rolling back to the version before, I haven´t made the last update on Sept 10th

Are you guys using latest NVidia drivers? Have read about troubles and therefore did not update from the penultimate one

Good hint is to use passthrough (just double tab the headset to switch to passthrough) and watch if any light sources are flickering. If so, shut them off, cover them or try to reduce lighting until you don´t see a flickering. My room was way too bright at the beginning and I had to reduce the light sources.

1.42.1 PP (latest version) and the latest firmware, which comes with 1.42.1 (being in office, not nowing the firmware number)

Look at my report regarding tracking…

No shut downs on my side… Keep fingers crossed it stays that way!

No, works just perfect. Even with Necksafer. Everything is fine from my point of view… Only night visuals remain a problem no matter what PP version.

1.42.1works with M-QV, you might have to reinstall M-QV after Pimax update. 1.41.1 had troubles with M-QV, but that has been resolved with a hotfix for PP (happend before the later release of current 1.42.1)

Oh boy - I already lost faith for the so needed pilot body for the A10C II. Now you reminded me on something I have nearly forgotten after so many years. Makes me kind of sad…

Are you using the OpenXR API Layers GUI tool according to Tallys Video? If so, please have a look that Necksafer is on #1 in the ranking (before QV). In my case, that resolved the problem with Necksafer. And also deactivate Eye Tracking in DCS when using Necksafer.

Here we go.... Running QV via QV companion and everything according to Tallys video PS: Hope you don´t mind the settings in German language!

Yes, QV leads to the grey veal ("white box"). But - in my case turning off SSAO while using QV solved the problem. Had a thread regarding this issue a couple of weeks ago:

try turning SSAO in DCS OFF

Honestly - I don‘t know. But since all of us have night visibility problems, I don‘t think it is hardware related, since the displays should be capable of showing black without halo and the other stuff… As you see, the problem with sunrise/clouds can already be solved by settings in the software. Maybe Pimax / Calvin can make a statement here…

I’ve updated my original post to include the issues with the Pimax during night missions – it’s not quite perfect after all.

Hey guys - quick update... I have now extensively tested the issues and adjustment options in a night mission (Syria, June, 4 a.m.) and a dawn mission (Syria, June, 04:15–04:30 a.m.): Problems: HALO around bright objects, especially the aircraft in external view Indefinable dark mass from the horizon downward; the transition from the stars over the horizon to the ground is not a clear line, but a constantly shifting “something” Partial “blackout”: when rotating the external view of the jet, brightness suddenly dims completely (across everything); when I then switch into the cockpit, everything is pitch black and the headset gradually brightens again Chromatic Aberration at sunrise / clouds, as described at the beginning of the thread Adjustment options: Contrast & Brightness in PP Local Dimming in PP Gamma in DCS Modifying the profile.json file as described by missioncmdr Upfront, everything that doesn’t work or has no effect: Problems: HALO does not go away, no matter what I do Horizon-to-ground transition remains undefinable Blackouts are still present Adjustment options: 2. Local Dimming in PP makes no difference 4. Modifying the profile.json (simply adding the line with the value, as it is not there initially) causes changes, but in my view nothing that Brightness couldn’t also achieve The only progress so far: Problem: 4. The Chromatic Aberration at sunrise or sunset on the horizon and in the clouds can be removed. Workaround: Set Brightness in PP to -2 and Gamma (previously 1.8 for me) to 2.8 (!). This results in beautifully smooth transitions without artifacts. I tried calibrating the correct brightness against the stars: everything I can see at B=0 and G=1.8, I can also see again at B=-2 and G=2.8. The problem then is with daytime missions: here, with B=-2, Gamma needs to be set to about 2.2–2.4, otherwise it looks too bright. You can fine-tune this a bit by setting Contrast to -2. Then Gamma can stay at 2.8 without affecting nighttime visuals, and during the day you get roughly the same brightness, although the colors appear a little more muted. On the other hand, Gamma can be changed during flight (for day/night missions). So – currently I’m using: In PP: Brightness -2 Contrast -2 In DCS: Gamma 2.8 Fun fact: If Pimax Play is completely closed and restarted, you still get the Chromatic Aberration despite Brightness -2 and Gamma 2.8. I need to briefly move the Brightness slider in PP, set it back to -2, hit Apply, and then the setting works again. This seems to be another bug. @Calvin.Pimax – please have your team take a look at this. It should all be solvable!

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).