Pimax Play v1.41.1

[Rufuz64]

3 hours ago, Calvin.Pimax said:

The repository will be created — I’ve submitted the request, and the team is looking into it.
The latest firmware for the OG Crystal is 05_31, unless they’ve opted into the WiFi Airlink beta test.

Thanks. Patch works.

[Massifontana]

Il 07/08/2025 at 09:27, Calvin.Pimax ha scritto:

Do you have mbucchia's QuadViews installed?
I suspect that might be the cause, as we've discovered compatibility issues between PimaxOpenXR and QuadViews in DCS, which can lead to game freezes. The dev team is aware and currently working on a fix.

Calvin I've tried today the latest update but it looks exactly as it was before.. PIMAX CRYSTAL OG

the settings I had before were like this:

Refresh rate 90Hz

Render Quality-- HIGH (1.0)

DFR - Pimax openXR Quadviews - Quality

I had 60/70 fps in Nevada (RTX 5090 I9 14900K)

Now with the customizable quadviews I set

35% horizontal\vertical gaze area

100%  gaze area 

40%peripheral

Disabled Mbucchia Layer  and Quadview foveated

and:

 

The frame rate is unplayble (around 30fps) and when I enable the Motion Compensation Open XR the game crashes instantly

 

 

 

[Peedee]

@Calvin.Pimax

Quote

III. Firmware Update:
Crystal Super Firmware V1.0.8:

• Fixed several known issues.

I am on V1.0.7 on the Super. What is actually fixed in V1.0.8?

 

[Massifontana]

3 ore fa, Massifontana ha scritto:

Calvin I've tried today the latest update but it looks exactly as it was before.. PIMAX CRYSTAL OG

the settings I had before were like this:

Refresh rate 90Hz

Render Quality-- HIGH (1.0)

DFR - Pimax openXR Quadviews - Quality

I had 60/70 fps in Nevada (RTX 5090 I9 14900K)

Now with the customizable quadviews I set

35% horizontal\vertical gaze area

100%  gaze area 

40%peripheral

Disabled Mbucchia Layer  and Quadview foveated

and:

 

The frame rate is unplayble (around 30fps) and when I enable the Motion Compensation Open XR the game crashes instantly

 

 

 

Ok, after the patch and updating the openXR Motion Compensation to the latest version it works! 
BUT,  MY HONEST and questionable OPINION is that: in the headset even with ULTRA preset and no upscaling looks and runs smooth and fine...BUT with this update, even trying to play around with the settings I'm not able to have a good enough quality in the screen recording as I had with the older PimaxPlay version and Tally Mouse QuadViews Companion.. the %'s do not match and the screen recording looks way worse..so I rolled back to 1.40.1.. I know that screen recording it's something that a lot  of players don't care about but I do! 

[Rufuz64]

17 hours ago, Massifontana said:

Ok, after the patch and updating the openXR Motion Compensation to the latest version it works! 
BUT,  MY HONEST and questionable OPINION is that: in the headset even with ULTRA preset and no upscaling looks and runs smooth and fine...BUT with this update, even trying to play around with the settings I'm not able to have a good enough quality in the screen recording as I had with the older PimaxPlay version and Tally Mouse QuadViews Companion.. the %'s do not match and the screen recording looks way worse..so I rolled back to 1.40.1.. I know that screen recording it's something that a lot  of players don't care about but I do! 

Screen recordings with Quadviews have a fundamental problem. The recorded image can only come from the peripheral, i.e., low-resolution view.
How did you manage to record good quality before?

[Calvin.Pimax]

21 hours ago, Massifontana said:

Calvin I've tried today the latest update but it looks exactly as it was before.. PIMAX CRYSTAL OG

the settings I had before were like this:

Refresh rate 90Hz

Render Quality-- HIGH (1.0)

DFR - Pimax openXR Quadviews - Quality

I had 60/70 fps in Nevada (RTX 5090 I9 14900K)

Now with the customizable quadviews I set

35% horizontal\vertical gaze area

100%  gaze area 

40%peripheral

Disabled Mbucchia Layer  and Quadview foveated

and:

 

The frame rate is unplayble (around 30fps) and when I enable the Motion Compensation Open XR the game crashes instantly

 

 

 

You have the v1.41.2 hotfix patch installed?

[Calvin.Pimax]

21 hours ago, Peedee said:

@Calvin.Pimax

I am on V1.0.7 on the Super. What is actually fixed in V1.0.8?

 

Unfortunately, I can’t share in very detailed, but the focus is mainly on audio, connectivity, and performance.

[Massifontana]

2 ore fa, Rufuz64 ha scritto:

Screen recordings with Quadviews have a fundamental problem. The recorded image can only come from the peripheral, i.e., low-resolution view.
How did you manage to record good quality before?

I know.. and you can capture only one eye.. good or bad quality is subjective heres a video from my channel

to me this is good "enough"... with the last update quality is way lower

[Massifontana]

3 ore fa, Calvin.Pimax ha scritto:

You have the v1.41.2 hotfix patch installed?

Now Yes, that was missing...  

anyway, I choosed to revert to previous version (1.40.1) I like it more

Edited Thursday at 12:35 PM by Massifontana

[jnr4817]

CPU resource utilization is still an issue. Im not coder, but it appears the complexity of the code with 9 different pimax processes running in the background with piserver.exe being the worst is bring cpu use to its needs. Add QV with DCS and CPU are managing a lot processes. It is a little better after last 2 updates with hotfix, but can be a lot better.

[Marshallman]

20 hours ago, jnr4817 said:

CPU resource utilization is still an issue. Im not coder, but it appears the complexity of the code with 9 different pimax processes running in the background with piserver.exe being the worst is bring cpu use to its needs. Add QV with DCS and CPU are managing a lot processes. It is a little better after last 2 updates with hotfix, but can be a lot better.

I have all CPU's checked in DCS . exe task manager, but Im only seeing 2-3 max used in game,is this slowing things down i wonder?

Edited 22 hours ago by Marshallman

[oCMANo]

I'm on 1.41.2 and getting a lot of tracking lag.  Anyone else experience tracking lag while in DCS?  Sometimes it's fine, but today was really bad.

[Marshallman]

1 hour ago, oCMANo said:

I'm on 1.41.2 and getting a lot of tracking lag.  Anyone else experience tracking lag while in DCS?  Sometimes it's fine, but today was really bad.

Yes Ive upgraded this afternoon to the same......Flying both F16 and F18 the cockpits are consrtantly Vibrating or shaking, anyone else getting this??

[Moxica]

3 hours ago, oCMANo said:

I'm on 1.41.2 and getting a lot of tracking lag.  Anyone else experience tracking lag while in DCS?  Sometimes it's fine, but today was really bad.

Me to.
Same old sameold.

[oCMANo]

3 hours ago, Marshallman said:

Yes Ive upgraded this afternoon to the same......Flying both F16 and F18 the cockpits are consrtantly Vibrating or shaking, anyone else getting this??

So found a couple things. 

The jitters and shaking that's when staying still, not tracking related, was from the Nvidia Driver 580.97 I believe.  Rolled back Nvidia Driver to 580.88 and it's gone.

Tracking lag, where it went very low fps and tracking isn't accurate, was from the 1.41.2 client.  I'd installed it over the 1.40 client.  Went back and removed Pimax in Add Remove Programs.  Stopped the Tobii VR4PIMAXP3B Platform Runtime service and deleted all Pimax folders, even those under user/AppData.  Rebooted and reinstalled the  1.41.2 Pimax Play.  Then tracking was much better.  For how long, don't know.  Haven't been able to use it for more than a few hours so far.  But it had been fine yesterday, seems to get worse over time.

Edited 15 hours ago by oCMANo

[Marshallman]

14 minutes ago, oCMANo said:

So found a couple things. 

The jitters and shaking that's when staying still, not tracking related, was from the Nvidia Driver 580.97 I believe.  Rolled back Nvidia Driver to 580.88 and it's gone.

Tracking lag, where it went very low fps and tracking isn't accurate, was from the 1.41.2 client.  I'd installed it over the 1.40 client.  Went back and removed Pimax in Add Remove Programs.  Stopped the Tobii VR4PIMAXP3B Platform Runtime service and deleted all Pimax folders, even those under user/AppData.  Rebooted and reinstalled the  1.41.2 Pimax Play.  Then tracking was much better.  For how long, don't know.  Haven't been able to use it for more than a few hours so far.  But it had been fine yesterday, seems to get worse over time.

Dammit i wondered about the nvid driver I’ll roll that back!!!  Cheers for that!

[jnr4817]

I’m still getting core 0 and 1 maxed out with dcs. I take piserver off those cores 

[heloguy]

Still can't use MBucchia's Quad Views after the patch.

[Marshallman]

7 hours ago, jnr4817 said:

I’m still getting core 0 and 1 maxed out with dcs. I take piserver off those cores 

In the DCS main page, with the fps views up I am getting  loads of cores being utilised. 
Soon as I’m flying it’s now 1.8 cores … could this be the problem of stuttering??

 I’m not that savvy on the motherboard aspects

[Rufuz64]

No tracking problems, no stutters (lighthouse). Always reinstall QV after the patch and check layers.

I can check inside-out tracking if you want.

Edited 2 hours ago by Rufuz64

[Moxica]

8 hours ago, heloguy said:

Still can't use MBucchia's Quad Views after the patch.

Re-install/repair MBucchia QV.
That also seem to help when the client starts to lag the tracking.
 

[Calvin.Pimax]

9 hours ago, heloguy said:

Still can't use MBucchia's Quad Views after the patch.

Please try reinstalling—it should resolve the issue. We’ve already had several DCS users test this hotfix patch.