Have any of you had issues with 2.0.3? Any issues of any sort I’d like to know as I was using it with a brand new headset and two changes at the same time get confusing for fault finding.
I have a new Dream Air Slam and I got eye tracking working but PP quadviews made my sim awful with scenery jumping in and out and flashing screens.
I immediately turned QV off in PP and rebooted but then I had a Jumpy mouse and keyboard. I had to turn off eye tracking to stop this.
I did try EVO before this and that did not end well with my PC refusing to Boot.
Any input gratefully received as I would like this working and ideally I’d like EVO working too.
Thanks everyone.
The PC refuse to boot when EVO is installed?
No After I uninstalled it and SBOYS driver the night before. Next night it refused to boot.
That’s strange.
Did you try to do a clean installation instead?
Yes I always do clean installation for everything. I think my PC had some unresolved issues with my controllers not having up to date firmware and the Win 11 reinstall maybe settled the issue but I now have a very nice Sim with the Dream Air running at full native resolution at 90Hz and getting 45fps locked.
I won’t be trying EVO again for a while so Thank you very for trying to help, I really appreciate it.
1 Like
Pimax play version 2.03 does not retain resolution settings per game, it switches to automatic as soon as the game is launched from App Library, is there a fix for this?
Index controllers emulation dont work.
Fingers are not tracking on Pimax controllers.
Haptic feedback don’t work etc.
same thing in 2.0.4
Since updating the firmware on my PCL, I keep getting ‘Sensors cannot track headset’ errors.
When this happens, the screen stay locked to the current view.
Exiting the game makes no difference, as it’s still locked in SteamVR and Pimax home.
Restarting the headset works for s few minutes, then it does it again.
Is there any way to roll back to v1.0.21?
Interesting, I am experiencing an issue with my Dream Air SLAM where I start flying and suddenly lose tracking shortly after. I have to unplug and re-plug the headset USB to clear this fault but once done it is fine for the rest of my flights. once I shutdown and re boot my PC it returns.
As this is an odd fault I wasn’t sure if it was linked to EVO so I uninstalled EVO and reinstalled PP only but the fault persists.
This isn’t caused by Windows Power save shutting down my USB’s either.
Surely this is a simple fix Pimax?
I think I may have found the issue.
The cameras seem to be much more sensitive to my room lighting.
If I reduce the brightness of my room, the tracking behaves again.
I’m wondering if the v1.0.22 firmware has increased the camera sensitivity?
Possibly may be your issue, if your Dream Air has had a firmware update?
Or maybe it’s the new version of Play.
I played for several hours yesterday without any loss of tracking.
Have a go at reducing the light in your room and see if it helps.
Hi, thank you. My room light is a very bright single overhead LED bulb as I thought that would help with tracking. Next time I fly I will try a less bright one and report back.
Oddly though I flew hundreds of hours in the Crystal Light with the same lighting and never had one tracking failure.
I also got Pimax to send me an earlier version of Pimax Play to try but haven’t had chance to experiment yet with it. Again I’ll try it and report back.
I was even considering a chessboard type of arrangement on the facing wall. Black and white high contrast squares thinking that may assist tracking.