So, the other day i was changing a lot of No Man's Sky settings, all at once. The headset had an aweful fit after i pressed the confirm changes button in-game.
I seen weird static distortions and I thought I had killed my headset. For real.
I tried numerous times to re-install various versions of pitool, and even re-installed my graphics drivers, checked window settings, and did a complete operating system re-installation with new partioning schemes..
but then I found the problem. it's Windows 10 (64bit if it matters).
Somehow, windows had seen my headset crash and decided to identify it as something it could, and should, claim as it's own. So it did. Windows was keeping my headset broken. (it had it listed as some kind of amd usb device and who knows whatever else).
• you can see your green light on, or flickering on / off between 2-10 hz/s.
• you can see that the headset power indicator is red instead of green or purple
• you can see that there is no render displayed on headset lenses
• plugging in the dvi? connector for headset results in odd windows artifacting and glitching on your regular tv display (as if windows is trying to display the vr render to your tv)
my personal solution:
*edit-before the next steps, I had also did a hard reset of both of my motherboard bios and then a pointless dry bootup without power to the gpu. the point of resetting a bios is to attempt to reduce os->uefi crosstalk or implanting of certain driver or mac entries. the no-gpu boot has helped me in the past when windows goes to infinite loading screen at boot-up (idk why but unplugging the power of gpu and doing a dry boot without it seems to fix whatever uefi entries prevent windows from loading for me. i think it's related to the security firmware that ships with the card since windows and amd are both on the board for UEFI).
• do a complete wipe of all drives and partitions. Re-install windows.
• before you install ANY drivers, right-click your start menu icon (windows icon) and then click on "Computer Management". Find and click on "Services and Applications", then click on "Services".. Scroll down the list until you find a windows service called "Device Setup Manager". Right click this service and choose properties, then 'Stop' the service, 'Disable' the service, and finally click on 'Apply' or 'OK'.
Continue installing your drivers and software as you usually would, but be aware that windows 10 has 'remediation' services that can reset your chosen services settings back to default if it sees fit.
I have done this and the computer is actually running faster, oddly.. Perhaps driver hijacking has been keeping me down and out longer than I know.
*edit - Oh, and yes, It did fix my headset. No more symptoms. However, for those who plug in the usb power / audio cables for the headset and still only see the red on the power indicator.. It took a few tries for me as well, and in the past too.. I try different ports, and I believe it actually matters about synchronous insertion of the usb cables into the ports. If you do it one at a time, it may still be red.. if you do them both together, maybe you get lucky like i have and the headset comes to life. it's very strange, but trust me, this method got my headset working. Also, when the headset finally loads back up, pitool will say it is not tracked.. just go to settings and cycle between 'lighthouse' mode and '9-axis' mode (remain on 9-axis mode if you don't have a lighthouse tracking station yet)
Hope this helps someone who is in fear of a broken headset.
Add a Comment
About This Community
Stay Up to Date With PiMAX VR Products, Orders, Experiences, Pitool, VR Ready PCs, Medium, Developers, Content and More… Read Guidelines
|Asked: 9/7/20, 4:48 PM|
|Seen: 26 times|
|Last updated: 9/7/20, 5:26 PM|