Pimax Play v1.41.1

[Nuggetz]

Using Pimax Play 140.4, QVFR, QV Companion @120% I get:

Marianas mostly 90fps, low level over Guam 65-75 fps. (Ultra Shadows- Low might yeild 90) On the ground at Anderson 90 fps. 

Germany mostly 90 fps. Berlin low level 55-65 fps (side view awful).

Sinai mostly 90 fps. 

Conclusion: despite some attractive features the latest Pimax Play it appears to be inferior to version 140.4 with QVFR & QVC in pure performance terms. 
 

Hopefully Pimax have some new PP under development  

 

Edited August 18 by Nuggetz

[Moxica]

The PiServer keep crashing. I havent even started Pimax Play, just by starting my PC, this is in event viewer:

Programnavn med feil: PiServiceLauncher.exe, versjon: 0.0.0.0, tidsangivelse: 0x671f43f7
Modulnavn med feil: ucrtbase.dll, versjon: 10.0.22621.3593, tidsangivelse: 0x10c46e71
Unntakskode: 0xc0000409
Feilforskyvning: 0x000000000007f6fe
Feil prosess-ID: 0x0x70C
Feil starttid for program: 0x0x1DC0F7CDB6C112B
Feil programbane: C:\Program Files\Pimax\Runtime\PiServiceLauncher.exe
Feil modulbane: C:\WINDOWS\System32\ucrtbase.dll
Rapport-ID: 3cfe5fc9-ea39-4bdb-b596-759607f41710
Fullstendig navn på feilpakke: 
Relativ program-ID for feilpakke: 

Edited August 17 by Moxica

[Calvin.Pimax]

On 8/17/2025 at 2:57 AM, Nuggetz said:

Using Pimax Play 140.4, QVFR, QV Companion @120% I get:

Marianas mostly 90fps, low level over Guam 65-75 fps. (Ultra Shadows- Low might yeild 90) On the ground at Anderson 90 fps. 

Germany mostly 90 fps. Berlin low level 55-65 fps (side view awful).

Sinai mostly 90 fps. 

Conclusion: despite some attractive features the latest Pimax Play it appears to be inferior to version 140.4 with QVFR & QVC in pure performance terms. 
 

Hopefully Pimax have some new PP under development  

 

For sure! The devs will be reviewing the QV parameters and working on revisions to improve performance based on user feedback.

On 8/18/2025 at 12:19 AM, Moxica said:

The PiServer keep crashing. I havent even started Pimax Play, just by starting my PC, this is in event viewer:

Programnavn med feil: PiServiceLauncher.exe, versjon: 0.0.0.0, tidsangivelse: 0x671f43f7
Modulnavn med feil: ucrtbase.dll, versjon: 10.0.22621.3593, tidsangivelse: 0x10c46e71
Unntakskode: 0xc0000409
Feilforskyvning: 0x000000000007f6fe
Feil prosess-ID: 0x0x70C
Feil starttid for program: 0x0x1DC0F7CDB6C112B
Feil programbane: C:\Program Files\Pimax\Runtime\PiServiceLauncher.exe
Feil modulbane: C:\WINDOWS\System32\ucrtbase.dll
Rapport-ID: 3cfe5fc9-ea39-4bdb-b596-759607f41710
Fullstendig navn på feilpakke: 
Relativ program-ID for feilpakke: 

Please file a support ticket, our engineers will reach out to you shortly.

[Papamiraculi]

Hi, I have updated to the latest hotfix. How do I now use the original Mbucchia QV? Do I need to uncheck Quadviews in Pimax Play for DCS but enable it in DCS to use the original?

I have tried that but it didn't work, but I haven't de- and reinstalled Mbucchia QV yet (I have just read I am supposed to do that).

Does enabling quad views in Pimax Play generally override Mbucchia QV? 

 

I get jittering in DCS. Generally the whole experience is far from smooth. DCS frame counter gives me constant 90fps and constant frametimes, but I get jittering all the time which makes it very much unplayable, it at least not enjoyable.

[Rufuz64]

On 8/20/2025 at 3:15 PM, Papamiraculi said:

Hi, I have updated to the latest hotfix. How do I now use the original Mbucchia QV? Do I need to uncheck Quadviews in Pimax Play for DCS but enable it in DCS to use the original?

I have tried that but it didn't work, but I haven't de- and reinstalled Mbucchia QV yet (I have just read I am supposed to do that).

Does enabling quad views in Pimax Play generally override Mbucchia QV? 

Reinstall mbucchia QV and uncheck QV in PP.

And yes, QV in PP overrides mbucchisa's QV.

[Papamiraculi]

vor 18 Stunden schrieb Rufuz64:

Reinstall mbucchia QV and uncheck QV in PP.

And yes, QV in PP overrides mbucchisa's QV.

Ok, thanks, this worked. 

I find the original much better than the PP QV. mbucchia QV allows for turbo mode and to reduce the border size. I think the PP version doesn't do this.

[Gun Jam]

I have version 1.41.2

Using quadviews If I want to supersample the Foveated section in the center of the FOV to 150% is the following the correct method?

Note: "Gaze area resolution" can not be set past 100. This would be the logical way to supersample the foveated part of the display... but no.

1) Set image quality "CUSTOM" set slider to 150% 

2) Set quadviews "Gaze area resolution to 100%

This means that the whole image is now 150% boosted and I would have to reduce "peripheral area resolution" by 50% to get it back to the same value as it was when "set image quality" was at 100%???

Is this the proper way to SS the foveated section in PP?

Thanks!

[MadMonty]

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?

Edited Wednesday at 08:10 AM by MadMonty

[Gun Jam]

11 hours ago, MadMonty said:

but I had big problems only achieving 35 FPS and a lot of stutter.

@Calvin.Pimax Im having almost the exact same issue.

1) I started out with 4.41.2 and nothing else.

2) i used Quadviews in PP only and right away got a good 75ish FPS on the ground and about 85 to 90 in the air. It was working well.

3) I tried some other setting only within PP like using "start" in the games tab within the "DCS" game after making setting adjustments. I also tried "smart smoothing" and lock to half frame rate.

4) after doing the steps describe in 3 FPS dropped to 35 and was not usable. I could not solve this problem by reversing the settings. I gave up and installed  1.40.4 and quadviews. This ran great (at least as good as in step 2) but DCS would crash frequently. 

5) I switched back to 4.41.2 and tried only the PP quadviews. same problem 35 fps. Reinstalled (repair option) mbuccha quadviews and using that I get 75-90 fps again.

6) but dcs still seems to crash a lot. Im worried its a cable issue. am investigating.

[Gun Jam]

@Calvin.Pimax

In order to help trouble shoot the crashing issue I simply enabled quadviews within PP its my understanding that they overwrite the mbuccha quadviews. I was expecting to fly around at 30fps but wanted to see if it would crash.

to my surprise I was getting the same FPS as with mbucca's QV

1) I dont know why its working now

2) I havent figured out how to replicate the issue yet

3) This seems to have stopped the constant crashing will keep testing this

Thanks!

[Papamiraculi]

I get jittery movement no matter what I do. It's not only in DCS. I can see the controller jittering in Pimax and Steam VR home. In DCS the whole cockpit jitters. This is at 72 and 90Hz, running on 9800x3d and 5090. Today is my last day of the 14 day trial. Tech support sent me a bunch of SLAM files and another pi_Server.exe. 4 different versions, nothing helps. Any ideas? 

[Marshallman]

Im back on 1.40 guys...... Only way I can get relatively smooth flying.

Launch direct from DCS with QVC running before I launch  (repaired  after using Pimax launch)

PLUS ---- Go into Task manager... click on DCS .exe ... go into details and set Priority as High....... without that last part...I only get one to two threads working on my CPU's, that changes to several and makes a difference.

Regards

[Papamiraculi]

"Relatively smooth". This is the best we get? I have just put on my quest 3 again and it is buttery smooth. Night and Day. I won't settle for "relatively smooth" on a 1800$ headset. This is very disappointing tbh.

[MadMonty]

39 minutes ago, Papamiraculi said:

"Relatively smooth". This is the best we get? I have just put on my quest 3 again and it is buttery smooth. Night and Day. I won't settle for "relatively smooth" on a 1800$ headset. This is very disappointing tbh.

I am completely smooth and super happy with the Super 

[Marshallman]

1 hour ago, Papamiraculi said:

"Relatively smooth". This is the best we get? I have just put on my quest 3 again and it is buttery smooth. Night and Day. I won't settle for "relatively smooth" on a 1800$ headset. This is very disappointing tbh.

Germany and Marianas are the maps ...thats all.

Everything else is good..

Edited Thursday at 10:21 AM by Marshallman

[Peedee]

54 minutes ago, Papamiraculi said:

"Relatively smooth". This is the best we get? I have just put on my quest 3 again and it is buttery smooth. Night and Day. I won't settle for "relatively smooth" on a 1800$ headset. This is very disappointing tbh.

My Pimax Crystal Super is buttery smooth at its full resolution, though with eye tracking and Quadviews activated. But because the eye tracking is so darn good, it´s increadibly clear and super smooth. Usually I am between 80-90 fps, but I have locked it to 72 to have some headsroom and keep it stable and avoid stutter. 

Why people have issues - I don´t know. I see some of them use task manager to change priorities for the CPU, others use special programs to choose which core does what in DCS and Windows and Pimax Play ...  I have not done that at all. No changes in windows. Game Mode ON probably. Not sure. HAGS ON, GameBar ON, Everything is at stock setup for Windows 11 and in the Bios too. No overclocking either. I have AMD 9950X3D, RTX 5090, 64Gigs of RAM @6000Mhz speed.

ALSO - this is on a new machine with a totally clean install of Windows 11. No Open XR Toolkit either. I am using mbucchias quadviews with its companion app to set quadviews settings, and have not activated Pimax Play Quadviews because of that. Can´t have both. 

I think that my clean Windows 11, with no other headset installs before this one, keeping everything as they are supposed to be (besides using the external quadviews install and its companion app) --- makes it stable, crystal clear and smooth. 

It is possible.

[Papamiraculi]

vor 58 Minuten schrieb Peedee:

My Pimax Crystal Super is buttery smooth at its full resolution, though with eye tracking and Quadviews activated. But because the eye tracking is so darn good, it´s increadibly clear and super smooth. Usually I am between 80-90 fps, but I have locked it to 72 to have some headsroom and keep it stable and avoid stutter. 

Why people have issues - I don´t know. I see some of them use task manager to change priorities for the CPU, others use special programs to choose which core does what in DCS and Windows and Pimax Play ...  I have not done that at all. No changes in windows. Game Mode ON probably. Not sure. HAGS ON, GameBar ON, Everything is at stock setup for Windows 11 and in the Bios too. No overclocking either. I have AMD 9950X3D, RTX 5090, 64Gigs of RAM @6000Mhz speed.

ALSO - this is on a new machine with a totally clean install of Windows 11. No Open XR Toolkit either. I am using mbucchias quadviews with its companion app to set quadviews settings, and have not activated Pimax Play Quadviews because of that. Can´t have both. 

I think that my clean Windows 11, with no other headset installs before this one, keeping everything as they are supposed to be (besides using the external quadviews install and its companion app) --- makes it stable, crystal clear and smooth. 

It is possible.

Yeah I don't understand it. For some everything's fine.

 

I don't have a fresh Win11 install (but it's basically stock settings) and I have both Meta Oculus and Virtual Desktop installed. Might be it.

[Dawgboy]

1 hour ago, Peedee said:

My Pimax Crystal Super is buttery smooth at its full resolution, though with eye tracking and Quadviews activated. But because the eye tracking is so darn good, it´s increadibly clear and super smooth. Usually I am between 80-90 fps, but I have locked it to 72 to have some headsroom and keep it stable and avoid stutter. 

Why people have issues - I don´t know. I see some of them use task manager to change priorities for the CPU, others use special programs to choose which core does what in DCS and Windows and Pimax Play ...  I have not done that at all. No changes in windows. Game Mode ON probably. Not sure. HAGS ON, GameBar ON, Everything is at stock setup for Windows 11 and in the Bios too. No overclocking either. I have AMD 9950X3D, RTX 5090, 64Gigs of RAM @6000Mhz speed.

ALSO - this is on a new machine with a totally clean install of Windows 11. No Open XR Toolkit either. I am using mbucchias quadviews with its companion app to set quadviews settings, and have not activated Pimax Play Quadviews because of that. Can´t have both. 

I think that my clean Windows 11, with no other headset installs before this one, keeping everything as they are supposed to be (besides using the external quadviews install and its companion app) --- makes it stable, crystal clear and smooth. 

It is possible.

I am in the same situation, still awaiting my headset and absolutely no software installed other than base simulators (DCS, BMS, MSFS); that said, this is promising info.  Thanks!

[Calvin.Pimax]

On 8/28/2025 at 4:26 AM, Gun Jam said:

@Calvin.Pimax

In order to help trouble shoot the crashing issue I simply enabled quadviews within PP its my understanding that they overwrite the mbuccha quadviews. I was expecting to fly around at 30fps but wanted to see if it would crash.

to my surprise I was getting the same FPS as with mbucca's QV

1) I dont know why its working now

2) I havent figured out how to replicate the issue yet

3) This seems to have stopped the constant crashing will keep testing this

Thanks!

Please keep me posted if you have encountered the crash issue.

 

On 8/28/2025 at 3:35 PM, Papamiraculi said:

I get jittery movement no matter what I do. It's not only in DCS. I can see the controller jittering in Pimax and Steam VR home. In DCS the whole cockpit jitters. This is at 72 and 90Hz, running on 9800x3d and 5090. Today is my last day of the 14 day trial. Tech support sent me a bunch of SLAM files and another pi_Server.exe. 4 different versions, nothing helps. Any ideas? 

Is the issue still persisting? Could you please share the ticket number with me? I’ll try to request an extension of the trial period until the problem is resolved.

 

On 8/27/2025 at 1:22 PM, MadMonty said:

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?

You gotta tick the "Controllerless mode" in Pimax Play. It's off on default.

[Papamiraculi]

vor 46 Minuten schrieb Calvin.Pimax:

Is the issue still persisting? Could you please share the ticket number with me? I’ll try to request an extension of the trial period until the problem is resolved.

 

Ticket #108937. I've already received an extension and have scheduled a remote support session for tomorrow, but honestly, I don't know what else to do here.

[Calvin.Pimax]

12 minutes ago, Papamiraculi said:

Ticket #108937. I've already received an extension and have scheduled a remote support session for tomorrow, but honestly, I don't know what else to do here.

Please keep me posted after the remote support session.

[MadMonty]

2 hours ago, Calvin.Pimax said:

You gotta tick the "Controllerless mode" in Pimax Play. It's off on default.

Thank you - will try tonight...

[Nedum]

On 8/28/2025 at 12:22 PM, Peedee said:

My Pimax Crystal Super is buttery smooth at its full resolution, though with eye tracking and Quadviews activated. But because the eye tracking is so darn good, it´s increadibly clear and super smooth. Usually I am between 80-90 fps, but I have locked it to 72 to have some headsroom and keep it stable and avoid stutter. 

Why people have issues - I don´t know. I see some of them use task manager to change priorities for the CPU, others use special programs to choose which core does what in DCS and Windows and Pimax Play ...  I have not done that at all. No changes in windows. Game Mode ON probably. Not sure. HAGS ON, GameBar ON, Everything is at stock setup for Windows 11 and in the Bios too. No overclocking either. I have AMD 9950X3D, RTX 5090, 64Gigs of RAM @6000Mhz speed.

ALSO - this is on a new machine with a totally clean install of Windows 11. No Open XR Toolkit either. I am using mbucchias quadviews with its companion app to set quadviews settings, and have not activated Pimax Play Quadviews because of that. Can´t have both. 

I think that my clean Windows 11, with no other headset installs before this one, keeping everything as they are supposed to be (besides using the external quadviews install and its companion app) --- makes it stable, crystal clear and smooth. 

It is possible.

@Peedee

I think it's all about the CPU, if the 5090 can't deliver enough FPS. And I can say that the FPS are different from the AC and the map.

Since I have "updated" from a 7950X3D to a 9800X3D, I am completely CPU bound in VR. Even in 2D 99% of the time I am CPU bound. It could have somthing to do with an update, but I am not 100 % sure.

I believe the 9800X30 is a very good CPU, but not good enough for DCS. Perhaps I will buy a 9950X3D. Every extra power/MHz will translate in "moar" FPS.

My test maps are Afghanistan and Germany (Berlin) and the AC's are the F16 and the AH64-Apache. Try the Apache over Berlin, low level flying or the F16 Cold Start in Afghanistan. Do you always get 72 FPS in those situations?

On 8/28/2025 at 9:35 AM, Papamiraculi said:

I get jittery movement no matter what I do. It's not only in DCS. I can see the controller jittering in Pimax and Steam VR home. In DCS the whole cockpit jitters. This is at 72 and 90Hz, running on 9800x3d and 5090. Today is my last day of the 14 day trial. Tech support sent me a bunch of SLAM files and another pi_Server.exe. 4 different versions, nothing helps. Any ideas? 

Guys, I think the "Jitter" @Papamiraculi is talking about has something to do with the Headset-tracking and the Room Lightening frequency.

@Papamiraculi try to change the frequency. Some old lights flicker. If you enable pass through, and you see a fast flicker, that's the thing that's causing the issue.

 

[Papamiraculi]

vor 1 Stunde schrieb Nedum:

try to change the frequency. Some old lights flicker. If you enable pass through, and you see a fast flicker, that's the thing that's causing the issue

I have tried both 50 and 60Hz. I only have DC LED lighting in this room, so AC frequency should be irrelevant anyway. 

I will, however, try your tip and look for flickering in passthrough.

 

It is definitely the tracking. If I disable tracking (recline mode) everything is fine.

Edited 4 hours ago by Papamiraculi

[Gun Jam]

@Calvin.Pimax Ive been doing what I can to get pimaxplay 1.41.2 to run DCS with quadviews.

I have multiple issues with DCS crashing that appear related to quadviews. Im using only quadviews within PP. I have uninstalled the openrx items.

1) without quadviews I get a pretty soil 35fps and DCS seems crash free. (im using syria instant action f14 takeoff from turkey the night one as a test)

2) with quadviews I get a pretty solid 35 fps or 60fps or 85 fps it just depends on how it feels during that launch I guess I cant find anything related to this not even resolution / global settings vs game settings. More resolution I get maybe 85 fps then i dial it back and I get 35 fps

2) with quadviews running like crap (35 fps) and settings low say 70% render resolution dcs wont crash or wont crash quickly.

3) with quadviews running great like 80-90 fps at 100 or 150% render resolution It usually crashes in a minute to 10 minutes or on final load screen just before you click "fly" or whatever with the background and cockpit visible behind that window.

there is no consistency or obvious pattern to which outcome im going to get.  

Is there anything I can submit or provide you that could help isolate this issue?