Pimax Play v1.42.1

[Calvin.Pimax]

Pimax Play v1.42.1

Download Link:
https://dlappstore.pimax.com/release/play/PimaxPlaySetup_Release_ToC_V1.42.1.177_202509031956.exe

 

Release Notes:

I. New Features and Improvements:

• Added Ticket System in Pimax Play for an easy issue reporting and log uploads.
• Revised Quadview per setting value.

II. Fixed Issues:
Crystal Super & Crystal Light:

• Improved headset tracking stability.
• Improved controller tracking stability.
• Fixed compatibility issues with certain games.
• Fixed several known issues.

III. Rollout Plan:

This version is planned to be gradually sent to all users within the next two weeks.

null

Edited September 4 by Calvin.Pimax

[Marshallman]

https://forum.dcs.world/topic/377066-pimax-play-v1411/page/5/#findComment-5689170

 

[Papamiraculi]

A step in the right direction, but I have to say that tracking still needs improvement. I still get jittering in DCS. It's better now, but not great. And this is after following all tips and tweaks available (covering reflective surfaces, different lighting, reinstall Nvidia drivers, assigning dedicated cores for pi_server, etc...).

New in this version for me: lagging tracking from time to time which goes away if I restart Pimax Play.

Please improve tracking further. I actually believe the tracking just sucks out too much CPU resources. DCS also needs a lot, so that's a bad combination.

[Calvin.Pimax]

Roger that! We had a meeting this morning about the tracking algorithm and CPU utilization optimization. The team is working on both, and we’ll ensure there’s progress in every rollout patch.

[MadMonty]

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:

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.

 

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!

 

[Nedum]

On 9/4/2025 at 9:38 AM, Calvin.Pimax said:

Pimax Play v1.42.1

Download Link:
https://dlappstore.pimax.com/release/play/PimaxPlaySetup_Release_ToC_V1.42.1.177_202509031956.exe

 

Release Notes:

I. New Features and Improvements:

• Added Ticket System in Pimax Play for an easy issue reporting and log uploads.
• Revised Quadview per setting value.

II. Fixed Issues:
Crystal Super & Crystal Light:

• Improved headset tracking stability.
• Improved controller tracking stability.
• Fixed compatibility issues with certain games.
• Fixed several known issues.

III. Rollout Plan:

This version is planned to be gradually sent to all users within the next two weeks.

null

Quad views customize, what is hidden behind all the fancy names?

How does which slider make differences in visuals and better fps/frame times? A single pictures can say more than 1000 words!

I always have to ask companies why they are unable to work with the most powerful human being interfaces, the eyes?

Make a picture of the expected visuals, name the zones with the names of the sliders and tell, what will happen, if you move the slider to the right or the left.

Only one single picture could catch thousands of questions.

What's the reason, companies still trying to compress all the necessary information into 2 text lines, and at the end no question mark of the customer is erased?

Click the Information point (I) and open a single picture with most if not all information. Thousands of questions less for the support, because now most people can !!see!! what each slider will do!

It could be so easy, so good for both sides, and perhaps the good idea behind all the work, would get the attention it deserves.

To let the customer fiddle it out by himself is the worst way to get acceptance of what you try to sell. 

At max 10 hours of work could bring you more customers and spare you thousands off dollars for the support.

Please, give us pictures!

And if PIMAX wants to act like a pro, make an animation pop up, if you change the sliders, and with each move of one of the sliders the customer can see what he is !!doing!, in real-time.

Too hard for Pimax? I don't think so.

Edited September 8 by Nedum

[dutchili]

@Calvin.Pimax
Tracking seems improved under artificial light conditions. 
But still in Pimax home all is good, in DCS tracking can have a hard time when looking over my shoulder.

Natural light coming in at an angle (window on my left) is giving tracking issue when looking either left or right over my shoulder, in DCS, not in Pimax home.

The new sharpness setting was set at .6. Very noticeable, but also reducing overall performance (missing frames).

When changing the sharpness, it is immediately applied. The apply button remains disabled, which breaks with the overall behavior of the application.

When I enabled Smart Smoothing while in DCS, the headset went black. I did not press Apply yet. 

I did not notice any difference with smart smoothing (RTX 5090).

 

Seems that  everything is on the right track, but outside in tracking is definitely in need of more improvements. 

[Calvin.Pimax]

23 hours ago, Nedum said:

Please, give us pictures!

And if PIMAX wants to act like a pro, make an animation pop up, if you change the sliders, and with each move of one of the sliders the customer can see what he is !!doing!, in real-time.

Too hard for Pimax? I don't think so.

Yes, that would be the best approach—providing release notes along with a short video to highlight the latest features and adjustments.

I’ll forward this to the team. Since I usually prepare the release notes, I’ll do my best to coordinate with them to make this happen.

14 hours ago, dutchili said:

@Calvin.Pimax
Tracking seems improved under artificial light conditions. 
But still in Pimax home all is good, in DCS tracking can have a hard time when looking over my shoulder.

Natural light coming in at an angle (window on my left) is giving tracking issue when looking either left or right over my shoulder, in DCS, not in Pimax home.

The new sharpness setting was set at .6. Very noticeable, but also reducing overall performance (missing frames).

When changing the sharpness, it is immediately applied. The apply button remains disabled, which breaks with the overall behavior of the application.

When I enabled Smart Smoothing while in DCS, the headset went black. I did not press Apply yet. 

I did not notice any difference with smart smoothing (RTX 5090).

 

Seems that  everything is on the right track, but outside in tracking is definitely in need of more improvements. 

Roger that.

Regarding the tracking issue—are you experiencing jitter, or is there a delay when turning left or right?

As for the Smart Smoothing feature, it still requires some debugging, since we’ve found it isn’t providing stable performance at the moment.

[dutchili]

Tracking: starts with jitter (the view moving up and down), then usually ending up outside of the cockpit. No delays.
If tracking data is somehow captured, i can send it to you. Just let me know how.
I have a high contrast backdrop, acoustic panels. This should make things easy, while it doesn't. But please note, only in DCS, not in Pimax Home.

[MadMonty]

48 minutes ago, dutchili said:

Tracking: starts with jitter (the view moving up and down), then usually ending up outside of the cockpit. No delays.
If tracking data is somehow captured, i can send it to you. Just let me know how.
I have a high contrast backdrop, acoustic panels. This should make things easy, while it doesn't. But please note, only in DCS, not in Pimax Home.

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

Edited September 9 by MadMonty

[Papamiraculi]

I can't get rid of the jittering. I tried everything. Nothing works. I can only assume this is a hardware defect of one or more of the tracking cameras. I have asked for a replacement. If it is not a hardware issue it means the tracking is absolutely abysmal and I will refund the Super. I can't and won't plaster my room with QR codes (well I tried but it didn't work either). This can't be the solution.

[Calvin.Pimax]

14 hours ago, Papamiraculi said:

I can't get rid of the jittering. I tried everything. Nothing works. I can only assume this is a hardware defect of one or more of the tracking cameras. I have asked for a replacement. If it is not a hardware issue it means the tracking is absolutely abysmal and I will refund the Super. I can't and won't plaster my room with QR codes (well I tried but it didn't work either). This can't be the solution.

If you haven’t heard back from our support team regarding the replacement or any workaround for the jittering issue, feel free to ping me.

20 hours ago, dutchili said:

Tracking: starts with jitter (the view moving up and down), then usually ending up outside of the cockpit. No delays.
If tracking data is somehow captured, i can send it to you. Just let me know how.
I have a high contrast backdrop, acoustic panels. This should make things easy, while it doesn't. But please note, only in DCS, not in Pimax Home.

You can export the log files from Pimax Play and send them to edgar.chen@pimax.com—he’s our engineer in charge for SLAM tracking project.

[Papamiraculi]

vor 36 Minuten schrieb Calvin.Pimax:

If you haven’t heard back from our support team regarding the replacement or any workaround for the jittering issue, feel free to ping me.

Ping

Ticket Nr. #108937

I have exhausted all options. The last thing to do is to try a replacement.

Thanks. I really hope the replacement is better. I want this to work.

 

[Marshallman]

More trials this morning... finding I can achieve  90fps by using FSR and NIS within PP.....Free flight with plenty of cores active......however the Swirls persist....

Vanilla installs of QVM   are constantly broken now....annoying!!!

Anyone tried Nvidia latest ?? came out yesterday.   Version 581.29

Regards

 

UPDATE.
Updated Nvidia driver.... Check your Settings it resets System fallback, shaders etc..

No adverse effects on DCS.

 

Edited September 10 by Marshallman

[HOKUM52]

Now on 1.14.2, with QVC and TM favourite settings.

• Performance on 1.14.2 is back up to solid 90fps and the sharpening in PP is really great (I cap it at 70 anyway and leave headset Hz at 90), still some stuttering when looking towards 3/9 o'clock near the ground where there's lots of objects
• but screenshots below i'm getting a very faint white box in the centre of the FOV 

After further flying the white boxes are not so much white, but more like brighter, very noticeable when looking at darker stuff like water or bottom of the cockpit. I've made some screenshots and edited them them to show an approximation of the effect, although they are more noticeable around the edges than in the centre in real. Something is telling me: its the more focused area being different to the peripheral. If I could just sort this id be square)

Pimax play sharpening at 0.6, Upscaling off, smart smoothing off, pp quadviews off.

 

thanks

 

5090 MSI Suprim soc

DDR5 6200

19-14900K

Edited September 10 by HOKUM52

[MadMonty]

1 hour ago, HOKUM52 said:

Now on 1.14.2, with QVC and TM favourite settings.

• Performance on 1.14.2 is back up to solid 90fps and the sharpening in PP is really great (I cap it at 70 anyway and leave headset Hz at 90), still some stuttering when looking towards 3/9 o'clock near the ground where there's lots of objects
• but screenshots below i'm getting a very faint white box in the centre of the FOV 

After further flying the white boxes are not so much white, but more like brighter, very noticeable when looking at darker stuff like water or bottom of the cockpit. I've made some screenshots and edited them them to show an approximation of the effect, although they are more noticeable around the edges than in the centre in real. Something is telling me: its the more focused area being different to the peripheral. If I could just sort this id be square)

Pimax play sharpening at 0.6, Upscaling off, smart smoothing off, pp quadviews off.

 

thanks

 

5090 MSI Suprim soc

DDR5 6200

19-14900K

try turning SSAO in DCS OFF

[PRLJpoisoncobra]

I have this exact same problem also as HOKUM52. The whitish squares are the focus areas and follow my eyes around distinctly as they are tracked. The squares shimmer and lines can also be seen in them when twisting the head.  The overall effect is that the focus areas appear lighter then the rest of the screen creating very noticeable boxes that follow your eyes.  A visual effect i wouldn't/am not happy to play with it. It destroys the otherwise perfect image and performance.

I also have  pimax super and pimax crystal OG.  On the Pimax OG this issue was ironed out. For my pimax super I can't seem to get rid of it no matter what settings I change. We need a Pimax software fix for this issue.

1 hour ago, HOKUM52 said:

 

• but screenshots below i'm getting a very faint white box in the centre of the FOV 

After further flying the white boxes are not so much white, but more like brighter, very noticeable when looking at darker stuff like water or bottom of the cockpit. I've made some screenshots and edited them them to show an approximation of the effect, although they are more noticeable around the edges than in the centre in real. Something is telling me: its the more focused area being different to the peripheral. If I could just sort this id be square)

 

 

 

 

 

 

 

[PRLJpoisoncobra]

Just gave that a try, still there i'm afraid

7 minutes ago, MadMonty said:

try turning SSAO in DCS OFF

 

[Calvin.Pimax]

On 9/10/2025 at 5:34 PM, Papamiraculi said:

Ticket Nr. #108937

 

Roger that.

[Moxica]

17 hours ago, MadMonty said:

try turning SSAO in DCS OFF

It is NOT SSAO; it is the QV!

[MadMonty]

7 minutes ago, Moxica said:

It is NOT SSAO; it is the QV!

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:

 

Edited September 11 by MadMonty

[Peedee]

5 hours ago, MadMonty said:

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:

 

No, it does not solve the problem. The «box» is still there. If you got rid of it, then good! That means it’s possible for the rest of us too when we find out how your other settings differ from ours  I have seen Calvin also suggest this. But, no’:)

[MadMonty]

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!

 

Edited September 12 by MadMonty

[Nedum]

Please Guys,

 

if you want help, then help those who want to help you. Show us your DCS settings. It's strange that those who want to help you post pictures more often and more frequently than those who want this help. Problems are often just symptoms, frequently triggered by multiple settings in the DCS system.

Are mods installed? If so, which ones?
Do you have the fxo and metashaders2 folders in the game settings section under DCS?
If not, do so.
Shader problems are not always solved by simply toggling the switches in the DCS settings.

 

 

Edited September 12 by Nedum

[Ollie]

May not be magic for any of the issues users are experiencing, but for me turning off HAGS made a world of difference to smoothness when using my PCL in DCS.