New version has been released folks! Time to experiment!

Here's what changed... (installing now and will test after work today)

Pimax Play

I. New Features and Optimizations
- Added GPU Upscaling feature, improving game performance while maintaining visual quality for a smoother experience.
- Added Quadviews customization, allowing users to adjust based on their preferences.
- Improved clarity of Pimax's Virtual Desktop.
- Optimized anti-aliasing for Pimax's Virtual Desktop.

II. Bug Fixes
Crystal Super & Crystal Light:
- Improved tracking stability.
- Reduced CPU resource usage.
-Fixed occasional freeze during firmware update.

III. Firmware Updates
Crystal Super Firmware V1.0.18:
-Fixed several known issues.

There is now a 'sharpness' slider which may well affect the clarity of DLSS in sim... going to check that out

Well got to say that this is a keeper for me!

Using ULTRA quad views in PP along with .6 sharpen in PP... 80% render in MSFS2024..

Using DLSS Quality as well to see if it helps and the image is very clear indeed...

Anyone else had a go?

 

... change to 80% render in PP and kept MSFS2024 to 100%.. also using TAA again...excellent clarity and performance at 3rd party NZAA

Edited August 2, 2025Aug 2 by vonduck

7 hours ago, vonduck said:

Well got to say that this is a keeper for me!

Using ULTRA quad views in PP along with .6 sharpen in PP... 80% render in MSFS2024..

Using DLSS Quality as well to see if it helps and the image is very clear indeed...

Anyone else had a go?

 

... change to 80% render in PP and kept MSFS2024 to 100%.. also using TAA again...excellent clarity and performance at 3rd party NZAA

Did you leave the Foveated Rendering at the default 0.50000 value in the User Config file or set it lower to a value such as 0.30000?

Just tried this update and now the sim will not let me switch to VR Mode. I get a message that says “The initialization of VR failed. Please check that OpenXR is installed on your computer and your headset can use it.”  Don’t have a clue how to fix that. 
 

Fixed it: I had to disable OpenXR Toolkit. 

Edited August 2, 2025Aug 2 by Gulf76

40 minutes ago, Gulf76 said:

Did you leave the Foveated Rendering at the default 0.50000 value in the User Config file or set it lower to a value such as 0.30000?

Yep, modified to 

FoveatedRenderingScale 0.300000

As for OXRTK i disable that for MSFS2024..had too many conflicts and trying to keep as standard as possible

 

22 minutes ago, vonduck said:

Yep, modified to 

FoveatedRenderingScale 0.300000

As for OXRTK i disable that for MSFS2024..had too many conflicts and trying to keep as standard as possible

 

Awesome! Thanks! Are you able to use another method to display FPS within the headset? That is the only reason I still was using OperXR Toolkit. 

12 hours ago, Gulf76 said:

Are you able to use another method to display FPS within the headset?

I havent found one as i dont really want to see the FPS...i used to be fixated on it to my own detriment so just aim for smoothness now.. but if i find something ill be sure to post it here 🙂

14 minutes ago, vonduck said:

I havent found one as i dont really want to see the FPS...i used to be fixated on it to my own detriment so just aim for smoothness now.. but if i find something ill be sure to post it here 🙂

Thanks! Yeah, I totally understand that fixation. I was hoping to get to a point to just disable it and looks like I’m there.