Tried to post in the 8k forum but kept getting an error, i assume this category replaced it and is for both 8k and 8k+ so here it is.
This bug is on a pimax 8k, with valve index controllers.
pitool 1.0.1.271
firmware 2.1.255.271
It’s a rather rare set of circumstances, i only noticed it in beat saber recently after keeping my sabers colliding for like 30sec (which give haptic at 100% on both controller for the whole duration).
Whenever the haptic on both controller run for an excessive period on 2 index controller (20-40sec), the headset seem to blank the display, shutting down the backlight or the panels im not sure, but the result is black screen for about 10 sec before it comes back on.
Disabling the haptic on the controller “fix” the issue, but obviously not ideal.
It’s a pretty rare thing to have the haptic motor just running for such long period at 100% power with no interruption for so long and honestly haven’t seen it happen “naturally” in any game yet. but using the saber collision in beat sabers or the chaperone proximity haptic feedback can very easily reproduce it. I assume any application that send haptic at 100% to both controller can cause it to happen.
after some more testings, full haptic on a single controller for a bit longer will also cause it to happen. when it happens, the entire headset “reset” with pitool showing it as disconnected for a few seconds before it comes back online.
i tried everything i can think off in pitool to see if anything had an impact. lowering the blacklight thinking it may be a power issue, lowering the fps, changing the fov etc. nothing made a difference, anything vibrating the haptic for too long cause the headset to crash.
i can confirm its an issue with the headset, im assuming some kind of current overdraw or whatever happen when a signal is sent non stop to the controller.
connecting the controller to the pc with usb instead of the wireless connection in the headset (connect and make sure the controllers are “paired” with the computer before connecting the headset) make the issue go away, until i unplug the controller. at which point in the view you see it disappear and reappear a few seconds later when it pair with the headset again.
obviously playing with cable isnt really ideal, so i ordered some usb dongles to pair my controllers directly with those instead of the hmd, hopefully will “resolve” the issue.
Would really appreciate some kind of software fix tho, even if its just turning off haptic for a few seconds if its going on for more than x sec in a row as a config in pitool, or straight out reseting the controller connection instead of the whole headset crashing whenever that happen.
so in case someone search a similar issue and stumble on this topic, i can confirm with certitude that it is an issue with my headset wireless controller (or whatever the bit that connect to the controllers is called). using watchman dongles to directly connect the index controllers to the pc skipping the headset worked perfectly.
Just gotta make sure i turn the controller on before i turn the headset on so that it doesnt end up autopairing back with it but thats about it, no more blackscreen when the controller vibrate for too long.
I have that same problem with my 5K XR… I have no controllers but screen goes black like power off. Lights are still there in HMD and PiTool gives no error. I also have pixel rain in my screens. I was discussing with staff and they suspecting that connection cable is broken. I checked a store in PiMax pages where cables are for sale and some customers have similar problem. Cables of HMD are not very good quality. I have tried to handle it with care and never put it any stretch or twist… Still it looks like a problem is there…in a cable
not the same problem then, as in my case, pitool did show the headset as rebooting when it happened.
Its also worth mentioning that i was able to get it to crash without moving the headset (leaving it on the desk). just open beatsaber (or any other game where you can easily get haptic vibration going), then get the saber to collide so the controllers vibrates. 20-30sec later, headset crash, restart and a few seconds later its back on.
Its also entirely fixed by using usb dongles to connect the controllers instead of the hmd.
whereas in your case, it seem pretty clear that the problem is either the cable, or the lcd itself since the screen black out but pitool still show everything as correct.