Pimax Play v1.33.01

[Spud257]

Thanks mate, I uninstalled Pimax 1.33 and reinstalled and now it works. 

[T24_Martin]

vor einer Stunde schrieb f14billy:

Make sure quad views is checked in the DCS VR Settings, it was disabled after the update and needed to be checked again and make sure the new eye tracking option underneath is unchecked. After reinstalling Pimax Play make sure quad views is also enabled there and reinstall quad views 1.1.3 (QV 1.13 is not necessary but it gives me better performance and I can customize the box size).

 

Thanks! That did the trick! T updates at the same time... didn't expect QV to be switched off in DCS 

[Elidji]

I have a problem with the new update where the screen flickers but just where I am not looking.

I'm using a Pimax Crystal, I have the problem even outside DCS.

I tried reinstalling Pimax play but it didn't change anything.

Edited October 1, 2024 by Elidji

[Johnny Dioxin]

22 hours ago, Dangerzone said:

 Just wondering what alternatives are available for this (in VR) if any?

I use fpsVR - but I don't know if it can be used outside of SteamVR. It gives a running data on many things - even down to battery charge for wireless headsets - and gives you a summary with average figures at the end of the session. You can get it to keep logs and have it display on the monitor if desired. Some examples below

[Dangerzone]

1 hour ago, Johnny Dioxin said:

I use fpsVR - but I don't know if it can be used outside of SteamVR. It gives a running data on many things - even down to battery charge for wireless headsets - and gives you a summary with average figures at the end of the session. You can get it to keep logs and have it display on the monitor if desired. Some examples below

 

Thanks. I used to use that when I went through steam, but after going OpenXR - don't have access to it anymore. That's where I found OXRTK invaluable as it gave me that information. 

I've got another question, but don't want to derail this thread so will start a dedicated thread here:

 

[Convoy]

Updated to 1.33 for my PCL, tested Pimax OpenXR vs SteamVR. SteamVR has much less latency and frametimes than running through Pimax. SteamVR is much smoother at the same FPS. 

 

Only issue is now that switching between the 2 deleted my SteamVR boundaries and now they won't save, so every time I turn on the headset, I have to redo them. If anyone knows a way to save them, I'm all ears. 

 

For those that are staying on 1.30 I wish I'd done the same. 

[Peedee]

29 minutes ago, Convoy said:

Updated to 1.33 for my PCL, tested Pimax OpenXR vs SteamVR. SteamVR has much less latency and frametimes than running through Pimax. SteamVR is much smoother at the same FPS. 

 

Only issue is now that switching between the 2 deleted my SteamVR boundaries and now they won't save, so every time I turn on the headset, I have to redo them. If anyone knows a way to save them, I'm all ears. 

 

For those that are staying on 1.30 I wish I'd done the same. 

I have not updated my headset or Pimax Play for quite some time, so I am on Crystal Headset (not Light) FIRMWARE 1.3.0_au0531 and PIMAX PLAY 1.25.01.01. I use the "external" PimaxXR app to control OpenXR settings, I have Quadviews installed and use the Quadview companion app to adjust Quadview settings. It´s very stable, frame rate is good, Eyetracking working as expected, everything is smooth and everything looks good. I don´t think I will do any upgrades for a while until it all settles a bit. . I started another thread in this part of the forum if I should upgrade anything or not, but I think I have gotten my answers here - as long as this "old" solution works as expected

[Panzerlang]

I think the best attitude to have towards any Pimax software is "Hope for the best, expect the worst".

[paul2437]

23 hours ago, Peedee said:

I have not updated my headset or Pimax Play for quite some time, so I am on Crystal Headset (not Light) FIRMWARE 1.3.0_au0531 and PIMAX PLAY 1.25.01.01. I use the "external" PimaxXR app to control OpenXR settings, I have Quadviews installed and use the Quadview companion app to adjust Quadview settings. It´s very stable, frame rate is good, Eyetracking working as expected, everything is smooth and everything looks good. I don´t think I will do any upgrades for a while until it all settles a bit. . I started another thread in this part of the forum if I should upgrade anything or not, but I think I have gotten my answers here - as long as this "old" solution works as expected

Yes returned to 1.30 with external files etc more stable.

 

22 hours ago, Panzerlang said:

I think the best attitude to have towards any Pimax software is "Hope for the best, expect the worst".

Your not wrong.

[nephilimborn]

Hi all, just received PCL yesterday...my previous experience is the Q3 in DCS. Have the following set in PPlay (attached)...my ignorant question is with both QV and FFR selected in PP, what is the effect? I am assuming the PXRuntime is requesting QV from DCS ... BTW, love the high res and color clarity of the PCL, however do not care for the lens-apparent? barrel effect nor the inconsistent focus, blurriness outside of the small sweetspot - as much as i hate meta, the edge2edge clarity of the pancake lenses seems superior or maybe i just need to get use to Pimax VR. Anyone else with a similar experience?null

Edited October 10, 2024 by nephilimborn

[Kiwispirits]

Autumn Tree Texture Flickering Problem and Solution

Not sure if this recent visual problem was because of Pimax Play or the last two updates in DCS, but I have been having problems with flickering autumn tree textures.
I am using a Pimax Crystal powered by an RTX3080 and got this problem while flying in the Caucasus in Autumn with foveated rendering enabled. Trees on the mountains that were in the outer zones of my vision at about 45 degrees from my flight path would flicker to a different texture and color (but still autumn colors) when I moved my eyes from directly ahead towards the mountains. It was not one or two trees but more like whole hillsides. This problem persisted with any of the three foveated settings (performance, balanced or quality) and render quality from 1.0 to 1.6 . My test flight was the free flight in the Caucasus in the JF-17, which starts mid-air in the position described above. Not the only mission to see it though.

I fixed the problem by changing my visibility range from high to extreme, which is now possible with the performance increase from foveated rendering.

Edited October 11, 2024 by Kiwispirits

[WipeUout]

After a few flight with 1.33 and the latest DCS update, my GPU frame time jumped by 0.5 ms.  Going back to 1.29 and re-installing PimaxXR resulted in going back to the same performance I had before, which rules out the latest DCS update as a probable cause.  Having OpenXR runtime built-in Pimax play is a good idea but for me, it is decreasing performance significantly.  I think there is room for optimization here.

I am still running Windows 11 pro 23H2 and my Nvidia driver is 552.44 (still the best for 4090).