Pimax Play SW 1.33.01.01 Quadviews Issues and DFR

[Justin1Ntime]

My PC crashed, and I had to redownload DCS and Pimax. I just installed the latest version of the Pimax Play SW to find out if the newest version of Pimax Play has XR and quad views (QV) built in. So now my problem is that DFR shows Off, and the quadviews companion does not appear to affect the visuals anymore. Eye tracking in DCS is working. According to Pimax support, the DFR is just a bug and will get fixed, and they did not mention any fix to the companion. Does anybody know where I can download the old pimax play sw. I can't seem to find it anywhere. 

[sleighzy]

The QuadViews companion app only works with the Quad-Views-Foveated API layer, so make sure you have that installed. 
 

https://github.com/mbucchia/Quad-Views-Foveated

Make sure you tick the “Quad Views” box in the DCS in game VR settings as well.

[Justin1Ntime]

@sleighzy That fixed it. I redownloaded it and repaired my installation, and It is now working with the new version of Pimax Play. 

[sleighzy]

Note, the new PimaxPlay has native support for Quad Views (there is a tick box for it in the PimaxPlay settings). You can use this instead of the Quad-Views-Foveated API layer, so can uninstall that layer to test it out (still need to have the Quad Views box in DCS), but you will lose the ability to use the Quad Views companion app so will be restricted to the three options that PimaxPlay offers.

You can also optionally install the https://github.com/fredemmott/OpenXR-API-Layers-GUI tool and just untick the quad views layer vs. uninstalling it completely. Might be convenient if you're wanting to test out PimaxPlay native Quad Views vs. Quad-Views-Foveated layer to see what performance / visuals difference you get between the two.

Edited December 28, 2024 by sleighzy
Fix typo "use" -> "lose"

[Monkman911]

Maybe a little off topic but since this is a Pimax Crystal thread, maybe someone can help me. I updated my Pimax Play to 1.33.01.01 and now when I load the game, I am moving out of the hanger to the point I am outside. Hitting 5 on the num pad brings me back to start menu but I start moving outside again. Thoughts?

Thank you in advance! 

[hsth]

@Monkman911  Since the update I have this weird 90 degrees view when I start DCS, it shows the menu on the left or right side over my shoulder. The only way to correct this is to go back into Pimax Play and do the room setup. After that DCS starts in the correct view. But i have to do this every time after Pc start.

[Johnny Dioxin]

6 hours ago, Monkman911 said:

Maybe a little off topic but since this is a Pimax Crystal thread, maybe someone can help me. I updated my Pimax Play to 1.33.01.01 and now when I load the game, I am moving out of the hanger to the point I am outside. Hitting 5 on the num pad brings me back to start menu but I start moving outside again. Thoughts?

Thank you in advance! 

This sort of issue usually happens when an axis or button is assigned (intentionally or not) to a view movement function.

I strongly suggest checking through all the assignments - including axes, to see if that has happened.

Just cos you didn't assign it, does not necessarily mean it isn't happening! (has happened to me before, too).

Edited October 10, 2024 by Johnny Dioxin
brain slower than fingers

[BIGNEWY]

15 minutes ago, hsth said:

@Monkman911  Since the update I have this weird 90 degrees view when I start DCS, it shows the menu on the left or right side over my shoulder. The only way to correct this is to go back into Pimax Play and do the room setup. After that DCS starts in the correct view. But i have to do this every time after Pc start.

I had this yesterday, I had to go into PIMAX play, make sure the headset is level and hit the horizontal calibration in the device tab. 

[Keith Briscoe]

The dreaded 'floating away' issue.  That is what plagued me and why I unplugged my PCL and went back to G2.  I hope to return and was hoping to hear that the new PP software thoroughly addressed tracking issues.

That said, I really hope i find a controls conflict like @Johnny Dioxin mentions... but that would just be too easy (still hoping though).

I too have tried doing a 'room setup' every time before starting up DCS, or even sometimes after starting DCS.  Haven't had full success with any technique... yet.

[Blackhawk163]

For those that start DCS off axis, why not just map the vr center to a button? I have mine on set to tab. Solves that issue without having to take the hmd off. 

[avgyst]

Guys, can you tell me, in dcs on pimax crystal light, stopped fixing the frequency of 90hz, began to show 50-60 with statters, although the headset is set to 90.

[avgyst]

5 часов назад, avgyst сказал:

Guys, can you tell me, in dcs on pimax crystal light, stopped fixing the frequency of 90hz, began to show 50-60 with statters, although the headset is set to 90.

Problem solved

[avgyst]

10 часов назад, avgyst сказал:

Problem solved

In general as it turned out the problem is not solved, yesterday was fine, today started dcs and here it is again. My assumption is that it is related to openxr toolkit, when I turn on quad view everything is normal

[avgyst]

Can you tell me why the CPU Bound is red when I turn on Quadviews?

 

[Chief_Biv]

Quadviews requires a good CPU to run alongside DCS. What is your CPU?

[avgyst]

7 часов назад, Chief_Biv сказал:

Quadviews requires a good CPU to run alongside DCS. What is your CPU?

5800X3d. I also have CPU virtualization enabled, maybe that's the reason ?

Edited October 26, 2024 by avgyst

[Chief_Biv]

That one is plenty strong.

Make sure you are not running stuff in the OpenXR Toolkit if you are running Quadviews. It is safer to disable the toolkit. See if that fixes things.

[avgyst]

3 часа назад, Chief_Biv сказал:

That one is plenty strong.

Make sure you are not running stuff in the OpenXR Toolkit if you are running Quadviews. It is safer to disable the toolkit. See if that fixes things.

Yes, I disable toolkit completely, it doesn't change the situation. When I use toolkit with turbo mod with the same settings I get more fps and cpu bound yellow lettering

Edited October 27, 2024 by avgyst

[Chief_Biv]

14 hours ago, avgyst said:

Yes, I disable toolkit completely, it doesn't change the situation. When I use toolkit with turbo mod with the same settings I get more fps and cpu bound yellow lettering

 

Is does not make sense that you are CPU bound with an X3D CPU chip. I have read that when Turbo mode is on that the CPU/GPU bound indicator is no longer reliable - see here; DCS World Performance and Settings Guide | Osean Air Force 8492nd Squadron

What is your GPU and how much RAM do you have? Does the Toolkit also tell you that you are CPU bound when turbo mode is off? Does the DCS fps frame counter that you pictured above also tell you that you are CPU or GPU bound in agreement with the Toolkit fps counter? When trying Quadviews have  remembered to turn on Quadviews with the new tick box within the DCS settings? Are you using Motion Smoothing in Pimax Play?

Edited October 28, 2024 by Chief_Biv

[avgyst]

1 час назад, Chief_Biv сказал:

Is does not make sense that you are CPU bound with an X3D CPU chip. I have read that when Turbo mode is on that the CPU/GPU bound indicator is no longer reliable - see here; DCS World Performance and Settings Guide | Osean Air Force 8492nd Squadron

What is your GPU and how much RAM do you have? Does the Toolkit also tell you that you are CPU bound when turbo mode is off? Does the DCS fps frame counter that you pictured above also tell you that you are CPU or GPU bound in agreement with the Toolkit fps counter? When trying Quadviews have  remembered to turn on Quadviews with the new tick box within the DCS settings? Are you using Motion Smoothing in Pimax Play?

 

4090, 64gb. Yes, when turbo mode is off, toolkit reports that I am cpu limited. Quadviews in dcs settings is enabled. I don't use motion smoothing in Pimax Play

[Chief_Biv]

Ok. So you are CPU limited. It is going to be difficult for me to help you. You have a better GPU than me and therefore I cannot speak with any experience with a rig like yours. If Quadviews tips you over from being GPU to CPU limited combined with a drop in fps then there must be something else swamping your CPU's capacity. You will have to investigate what else is consuming CPU resource in the background. Use the Windows Task & Resource Performance manager to observe all this. Does it show your CPU at 100% capacity, are you temperature throttled, are all your CPU cores being utilised?

Also, you may want to try turning off any data export apps you may have running in conjunction with DCS (e.g. Tacview, Winwing's SimAppPro, etc). I also assume you are running the very latest version of DCS too. I am running out of ideas. But it looks like something has maxed out the critical core in your CPU.