SOLVED.
Restarts at the time it did not help. After I closed down and returned just now the problem seems to be solved so if it happens to anyone they should do a complete cold restart.
Date: 22/04/2022 Issue Title: Pitool v1.01.0.1.277 has caused SteamVR faiure.
**Description:**Cannot get SteamVR to run.Critical error. I have uninstalled and re-installed SteamVR. MSFS will switch to VR view but the view is stationary and will not move.
HMD Model: Pimax 8K plus First 3 Numbers Serial: 206 Pitool Version: v1.01.0.1.277 HMD Firmware: v2.1.255.273 Tracking: single station
Well - as far as I can judge, there seems to be no major need to update from .275 to .277 for me. So Iāll leave that red notification dot in PiTool untouched
I have been using V275 for a while and am experiencing the same freeze with MSFS2020.
The probability of this happening is much higher if I use steamVR auto-start when I start VR mode.
My guess is that this is happening when the HMD is not in detection range of the base station when auto-starting.
It seems that the HMD is missing its position and is failing to initialize.
If I start MSFS and then manually start steamVR before putting it into VR mode, it is fine. If this still occurs, please place the HMD in the detection range of the base station.
I have not experienced any freezes with that usage.
Okay, I did the trial because the forumās release notes state some āAdditional bug fixes and optimizations.ā, too.
Positive:
PiTool seems to recognize the 8k-X now instantly again as it was before .275 when I used .270.
Negative:
SteamVR failure:
I already did a cold boot, no change.
Iāll give a SteamVR reinstall a try now - but at least, this certainly isnāt what is supposed to happenā¦
EDIT:
Okay, seems to work again:
I did a clean re-install of PiTool .277 including deleting manually the four Pimax/Pitool folders in AppData and reboot.
At first, it did not work yet - it took me a moment to realize that there is a new feature in SteamVR which locks the Pimax PlugIn - so I had to unlock this PlugIn.
Now, I have image again.
Apart from this, as mentioned above already, the headset is recognized at once again
But the issue with pi_overlay.exe crashing when closing PiTool still persists:
Yeah, no kidding. Itās not just Pimax; companies in general have mostly done away with the detailed update/upgrade notes we all used to rely on to determine whether we really wanted to do the install. Itās almost always now vague language about ābug fixes and optimizationsā (even though, ironically, a release may actually be both buggier and slower.)
I would sure love to know a little more about this release. (Please, PLEASE tell me I can use Smart Smoothing again! That 1/3 rate needs to go away. Permanently. Forever. Gone. Bye bye!)
This is unfortunately out of his hands. Quorra, @PimaxUSA and myself have been pressing for quality release notes without much success. I imagine even @SweViver whom has demonstrated with @arminelec have also requested professional release notes.
We last had quality release notes iirc 2 years ago.
I get an error failed download at various MB (changes each time I try) - could the server be busted? I guess I donāt care as I donāt have tundra trackers or leap motionā¦
Ya. it would be nice to have a list of what is unresolved and being worked on. It would reveal something of what Pimax thinks is still in need or improvement.
Well after update to V277 my PIMAX 5+ cannot connect failure 20300, although it is connected to DP Port like before. Nothing has changed within my hardware.
Although plugged/unplugged ports and cold-started PCā¦ nothing helpedā¦what should I do ?
If nothing else help, then unplug cable from HMD side, and replug it again. PC side will not help.
It solved once same problem to me; also didnĀ“t change anything in my hardware, and that was inctructed by Pimax helpdesk.
20300 usually mean that there are too many USB devices, You may first try to remove some unnecessary USB devicesand tips provided from the community .
If it still 20300, we suggest you to log a ticket at our helpdesk.
Our technician is ready to provide assistance to you.
Okay, unfortunately that worked only that one Windows session on 04/22/22 correctly - since then I am still and again having the problem, the headets isnāt recognized directly: First #10600 for 3-5 seconds, then #20300 for 1 second, then, the headset is identified and everything is working properly, just as it was with .275 before, too.
As I had another problem with fholgerās vperfkit not launching since two or three days (.277), I did the try and made a downgrade to .270.
Result - really weird:
During downgrade I did three Windows restarts - two after uninstall and folder deletion, a third after PiTool .270 installation.
=> The HMD was recognized properly and I could play for half an hour.
I then shut down the PC completely during lunch, restarted it 15 minutes ago - and PiTool wasnāt able to recognize the 8K-X any more. Same as I had two months ago when I first went to .275, had the aforementioned problems, wanted to downgrade to .270 - and at that time, too, first launch after having done only āwarmā reboots was no problem. But as soon as the PC was completely shut down over night, I wasnāt able to convince PiTool .270 to work with the 8K-X any more. So I upgraded back to .275, got the initial detection and pi_overlay.exe crash problems back - but at least the HMD was working again.
So, as far as I can judge, firmware version 2.1.255.299 isnāt downward compatible properly, for whatever reason.
Besides: Back then in February, even trying a firmware downgrade to the corresponding version of PiTool .270 didnāt workā¦
=> So really be careful for the moment. If you have no need to upgrade beyond .270, donāt do so - stay with .270 or before and remain happy that everything is working
