Yes that is correct. Since we only had one left, we didn’t want to add it to the webshop. We saved it for you. Shipping to UK is 172 SEK.
2 Likes
Cable received and sparkles are gone.
Many thanks.
1 Like
The headset is still turning off and back on again over and over so it seems that wasn’t a cable issue.
1 Like
Sorry to hear that. Do you still use the same firmware and version of pimax play as before?
Yeah they are the latest ones. I might try going back to an earlier Pimax play and see if it helps.
At least the RGB sparkles are gone.
Yes the sparkles are almost 100% an issue of a bad cable. The newest pimax play versions aren’t optimised for older headsets. Pitool are still best for the older headsets. We do have the best version if you want to try it out. But going back to an older version of pimax play might do the trick as well.
2 Likes
Which Pitool/PiPlay version would you suggest for older headsets? Thanks.
I actually preferred Pitool. The versions of Pimax Play prior to this one caused this problem:
I’d be happy to try out the best version.
I rolled the Pimax Play back to version 1.29.01.01 and at first I couldn’t get it to connect and then all my USB devices turned off.
After rebooting it works fine and the headset stays on all the time.
I don’t know if there is any advantage to using the the piplays newer than this version. If so I could try upgrading until I get to one that is unstable and roll back to the one before.
It may depend on the game, but I did try 1.38 and it has an issue that it stays in “space” until I recenter in the game, which actually works weird because sometimes only one eye is in game another stays in space … until more recentering. Also, as I run OpenXR game I found that 1.38 is slower than 1.29+PimaxXR so I am also on 1.29, although I suspect for P2 HMDs even older versions might be better.
1 Like
Tbh, there isn’t really any benefit to the newer version for your headset. It only really benefits the crystal series so I would just stay put with what works.
2 Likes
Thanks. The one thing I did find was useful was bypassing login. I could block Pimax Play in the firewall and then it would allow me to skip having to login.
I mean, logging in as guest is OK but it’s annoying to have to click that little checkbox all of the time.
2 Likes
I am still getting this problem and I never had before I got the new cable so I wonder if it’s related. If I plug the Pimax into a USB 3.0 port it works fine apart from the fact that the audio is crackly and drives me nuts.
So I plug it into a USB 2.0 port, the very one I used to run it for years on, and the audio is fine but moments after turning it all on my keyboard and mouse go off and then BSOD. One time it didn’t BSOD and Device Manager says, “Windows has stopped this device because it has reported problems. (Code 43)”
I don’t remember this happening with the old cable so I don’t know if it’s cable related.
Obviously I would suspect driver issues but I booted into my Windows 11 installation that obviously has newer drivers installed and either the crackling remains on the USB 3.0 port or it just won’t connect. USB 2.0 turns off the keyboard and mouse again like in my main installation.
I uninstalled Pimax Play and installed the last version of Pitool and the issue remains.
Pimax Support say the new cable is faulty so I am right back to square one again.
Wish I noticed this sooner. I was testing things that didn’t have much sound in it. Then I recently played a game that had music in it and was constant crackling.
1 Like