New Build, Pimax 5k+ is seen as a monitor by Windows and PiTool shows error 10600

Hello All,

My old PC went to crap so had to build a new one. Made screamer except kept my 1080 for now to wait till summer for the 3k series. On old pc everything worked just fine. So on new PC I have my Rift up and working and my Vive up and working, SteamVR is working, my Index Controllers are working, but my Pimax 5k+ is being seen by Windows as a monitor.

The light on HMD is green, the HMD is on and showing a portion of my desktop. SteamVR sees it and it wakes on movement, yet is not actually in sleep mode since it is being used by Windows as a monitor, but SteamVR think it is asleep so it is tracking it on movement. Yet SteamVR does not see it as a VR device in regards to display device type. The HMD icon in SteamVR goes active when the 5k+ is moved, in SteamVR if I go to “Update Device” it opens the list of devices and lists “Headset” with a green check stating up to date. If I go to room setup it says “Headset Off” in greyed out but the 5k+ is on and showing an image of my desktop.

PiTools shows error 10500 when I have the HMD turned off, and when I turn it on it changes to 10600. In SteamVR, a pop up and gives error 422. with a message saying SteamVR failure.

I have tried uninstalling/reinstalling PiTools(deleting local app files as well), Made sure to set SteamVR Direct Display mode to enabled, reconnection changes(tried different dp ports), tried 2.0,3.0 US ports, reboots, HMD restarts, and just a bunch of stuff I have read in other posts to try but none of those had my unique set of behaviors. Most had red lights and no HMD functionality. Mine is kinda half alive.

Anyone got any suggestions for this scenario?

I have the exact same issue!

Does anyone know anything? @Heliosurge

Not off hand I think some whom have had similar issues have had supports assistance in resolving
Can you both post more details? Ie system config.

@cperryb did you back the Pimax kickstarter?

The headset displays had to be specifically listed (by the vendor ID) in Nvidia drivers, in order to not be seen as monitors. This normally works for Pimax headsets, so there are two possibilities: Either the drivers for some reason do not recognize the headset ID, or the headset does not present the correct ID.
Both need however direct access to the hardware and internal knowledge of Pimax hardware and Nvidia drivers, for further analysis.

3 Likes

My issue was fixed with a new firmware file that support sent to me. What amazed me was I opened the ticket on a Friday ight, and they got back to me within 15minutes or so and included the file to try in the 1st reply. I was up and working right away once I applied the new firmware to the HMD. I thought it would take days to maybe get a reply, but boom, they were on it in minutes. Hopefully you have the same luck.

2 Likes

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.