Gotta confirm this with Silvan.
1 Like
Silvan confirmed Pimax OpenXR is now working on Live 
4 Likes
@PimaxQuorra this is great news, but brings other issues into focus, namely loss of SteamVR Desktop and FPSVR.
- Pimax Desktop is considerably lower resolution than SteamVR Desktop, and no resizing fixes it. Iām using it now, why is this? I had to increase the desktop size just to make the text clear enough to read and write. SteamVRās curved screen is nice too.
- Mouse cursor is very underdeveloped and hard to use. No consistent clear cursor across the entire desktop, unlike SteamVR Desktop. I have to use the controller pointer to be able to select anything easily, again unlike SteamVR Desktop.
- Is there any plan to work further on the feature? Does PiPlay 2.0 have any improvements for this? I donāt have access to it yet.
- I canāt check VR performance now without FPSVR. Any plans to create a VR metrics utility? We really need an alternative to FPSVR. Apparently OpenXR has some metrics but fiddly to set up. EDIT - just found out thereās a simple Pimax FPS tool when adding a new window in the VR UI. Going to check this out now
Added these requests to a dedicated post here: Pimax Play VR tools feature request
1 Like
@Shazboticus checked and confirmed, Parallel Projections is no longer required! 
1 Like
Yes, I talked to him earlier and received this news before the patch went live.
1 Like
Itās still required if youāre using SteamVR unfortunately. Not required if using OpenXR.
1 Like
Let me check with Silvan, as he mentioned that he has tested it with the Super.
Hi, could you please tell if this is still the case? That you can use native (not parallel) projections in Star Citizen and that it indeed performs faster this way?
I am trying and having double vision.
Hi, yes absolutely it still works and it reduces the performance overhead on the GPU - you must also use Pimax OpenXR as the runtime, and not anything else such as SteamVR runtime. You can check and switch this within PiPlay. This also provides an additional performance and stability gain.
I have this set up with PiPlay 1.43.6 (have not tried 2.0 yet):
With Star Citizen due its launcher and separate exes, the only way to apply settings is to use the Common Settings profile under Device Settings ā Games.
So yes, changes here affect every app using the generic Common Settings profile unfortunately. Thereās currently no other way from my understanding, as itās not possible to have a Star Citizen-specific profile that takes effect. Not sure if thereās a way in future.
3 Likes
Not sure if its just me but I cant get my micro-oled working in Star Cotizen at all. Iāve tried all recent versions of Piplay, I made sure that VR is enabled in the launcher. Iāve tried openXR and steamXR, and followed any trouble shooting tips I can find.
I had it working on my crystal OG in version 4.5 before I upgraded my headset, but no luck with the Micro-Oled.
I donāt get the experimental VR options in Starh Citizen settings, so it doesnāt look like the headset is being detected properly, but if I join the game, the image on my monitor moves as I move the headset, but I just have a back screen inside the headset.
Is this a known issue?
No, this is the first time Iāve come across this. Iāll report it to Silvan and see if he has any insights.
EDIT: Nvm, updated to latest PTU patch and problem has gone. I can only assume the Pimax update affected something fed to SC, and that was fixed by updating to a new build
@PimaxQuorra I have a new issue in SC since installing 1.43.9. Never had this problem until now and have not made any other changes, same SC PTU build before and after. Headset is 8KX (btw Dream Air should have arrived yesterday, but has been held for 5 days in China, customs are waiting for export documents from Pimax!)
Ofc I donāt know if itās purely an issue with the latest software, or it has triggered a problem with SC. I am not alone in this issue either, but not pinpointed the cause as of yet.
- Issue is in headset only, and with SCās game menus before loading into 3D. Instead of showing the whole menu as before, it is now zoomed in on the top left quarter, and in addition the mouse cursor is offset. So I cannot access most of the UI to progress - thankfully the monitor window is still fullscreen, so I can peek from my headset and progress that way.
- Screenshotting the menu doesnāt work, the images appear as normal.
- Loading into 3D works fine, the game runs as normal
- If I go to Options and change the 2D resolution to something else and back under Graphics, this will fix the issue (although the mouse still seems to be locked to a border until tabbing out and then back into the game) - my default matches my monitor at 2560x1440.
- Have you had anyone else report this for 1.43.9, and if so does it affect particular headsets or applications?
- Iāll try and roll back to 1.43.7 to compare later - what is the best way to do this? Uninstall current version and then install the older one? Any risk of losing settings?
- I havenāt tried any other VR apps lately but will see if others are affected.
Thanks 
Good to hear that the issue has been resolved; I was about to reach out to the SC team.
Iām guessing the holiday may have affected the shipment process. The status should be updated within the next few days.
1 Like
Ah thanks. Iāll keep an eye on things ofc in case the problem comes back 
Yes only just heard about the long holiday and Customer Support confirmed that. Hope you had a good break!
UPDATE
I was able to fix the problem by disabling eye tracking in openXR VR layers.
After that it works perfectly, though I thought that eye tracking was supposed to work, so maybe thats an issue too.
Hmm, it should be working though. So just to confirm ā with ET enabled, the image simply doesnāt appear inside the headset?
If Iām not mistaken, Silvan also has the micro-OLED version for debugging purposes. Have you reported this to Silvan before?
No, this is the first time I have reported it.
Yes, I have a black screen when the eye tracking is enabled in openxr layers.
Noted. Let me forward this to Silvan.
The eye-tracking is disabled in Pimax Play or OpenXR toolkit?
Openxr toolkit is disabled, but eye tracking is enabled in Piplay. Itās juts in openxr layers where I need to disable it.
1 Like
Iām currently using 1.43.19 and seem to be only getting 3DOF consistently in SC with the Dream Air, no issues with 8KX. The DA seemed to be tracking 6DOF in DCS, so not sure what the cause is yet. Trying a few different configurations. Iāll also check SteamVR compared to PimaxOpenXR.
Iām generally writing up my thoughts on the new headset, but was away for the weekend, need to test some more.