Hey ED gang!
Sooo I apologize that this is a bit of a read but I'm not 4 weeks without VR and I can't find help anywhere else (including Oculus support).
I first started playing ED:Horizons in November and from November to January I had the most fun you could possibly have with pants on. Friend and I both grabbed copies off Steam, been flying Multi-crew missions since Christmas and we couldn't be happier unless someone dumped a carrier on my lap. About 4-5 weeks ago my Rift S headset started 'crashing' which I'll describe below. At first it was roughly every 2hrs which wasn't terrible because it reminded me it's time to stretch the legs, but as days went on that window narrowed to the point where now I have the 'crash' occur as soon as the game loads and I'm in a station dock (so < 30 seconds given SSD load times). I am currently at the point where I can't load the game in either Oculus or Steam VR and upon contacting Oculus they looked puzzled that there was a problem with one of their god-toys.
The "crash" is simple and I'll describe about a week into the incidents. Game would load, I'd fly around for 15-20 minutes and then the cameras stop tracking in the headset. I'd hear an audible sound that Windows makes when you unplug a USB device and plug it back in. Full system unresponsiveness but Audio would still be playing and the game itself would still be playing on my monitor even though the pilot looked like she was having a seizure because the game was still trying to follow the Rift S. When the devices (mainly mouse and keyboard) came back online after about 20 seconds the pilot seizure would stop but the colors in-game were incredibly dull. My bright orange cockpit would now be a fuzzy-orange glowstick and nothing looked right (It would be as though someone went from 4K Vivid-colors and when the screen refreshed they swapped it out for a CRT tv with a busted antennae). See attachments for comparison
I can alt-tab out of Elite which was the only way to kill it via task-manager (remember, ED stopped reading USB input after the 'crash') and I'd be back to the launcher. Putting the headset back on I can see static in the passthru lenses (like poltergeist level static) so I knew something was off. Even after killing the Oculus server running and restarting the Rift I would come back to a headset that now 'worked' but there would be absolutely zero 6DoF (Degrees of Freedom) so I could only look up/down/left/right (no vertical, head tilt rock forward and backward,etc.).
So here's a 4-week grocery-list of things I've already done
I'm out of guesses at this point and I'm really hoping there's someone browsing the forums that can offer to try something I haven't yet. I'm even at the point where I'm RMAing my Motherboard in case something's died but this has been a gradual death and given I've done several power-swap tests I don't think it's the power supply either. Oculus won't admit the headset is the problem because re-seating the cables did nothing, so I'm literally drifting towards a star and no way to call the Fuel rats of VR and I'm almost in tears because of the time I've invested in this.
Please... anyone give me a reasonable suggestion I haven't already tried. Thank you pilots, hope to see some of you in-station when this is finally fixed.
Sooo I apologize that this is a bit of a read but I'm not 4 weeks without VR and I can't find help anywhere else (including Oculus support).
I first started playing ED:Horizons in November and from November to January I had the most fun you could possibly have with pants on. Friend and I both grabbed copies off Steam, been flying Multi-crew missions since Christmas and we couldn't be happier unless someone dumped a carrier on my lap. About 4-5 weeks ago my Rift S headset started 'crashing' which I'll describe below. At first it was roughly every 2hrs which wasn't terrible because it reminded me it's time to stretch the legs, but as days went on that window narrowed to the point where now I have the 'crash' occur as soon as the game loads and I'm in a station dock (so < 30 seconds given SSD load times). I am currently at the point where I can't load the game in either Oculus or Steam VR and upon contacting Oculus they looked puzzled that there was a problem with one of their god-toys.
The "crash" is simple and I'll describe about a week into the incidents. Game would load, I'd fly around for 15-20 minutes and then the cameras stop tracking in the headset. I'd hear an audible sound that Windows makes when you unplug a USB device and plug it back in. Full system unresponsiveness but Audio would still be playing and the game itself would still be playing on my monitor even though the pilot looked like she was having a seizure because the game was still trying to follow the Rift S. When the devices (mainly mouse and keyboard) came back online after about 20 seconds the pilot seizure would stop but the colors in-game were incredibly dull. My bright orange cockpit would now be a fuzzy-orange glowstick and nothing looked right (It would be as though someone went from 4K Vivid-colors and when the screen refreshed they swapped it out for a CRT tv with a busted antennae). See attachments for comparison
I can alt-tab out of Elite which was the only way to kill it via task-manager (remember, ED stopped reading USB input after the 'crash') and I'd be back to the launcher. Putting the headset back on I can see static in the passthru lenses (like poltergeist level static) so I knew something was off. Even after killing the Oculus server running and restarting the Rift I would come back to a headset that now 'worked' but there would be absolutely zero 6DoF (Degrees of Freedom) so I could only look up/down/left/right (no vertical, head tilt rock forward and backward,etc.).
So here's a 4-week grocery-list of things I've already done
- Updated Windows and all drivers
- Reinstalled USB drivers specifically and turned off all power-management for all USB devices through the Device Manager and Windows Power plans
- Uninstalled the Oculus software and Steam VR. Purged ALL Oculus folders including C:\Users, Program Files (including x86), and App Data
- Reinstalled Oculus first, still happened. Reinstalled Steam VR, still happened.
- Updated my Asus motherboard's bios
- Reformatted ALL my drives and re-installed Windows 10 Pro, same thing
- Grabbed a PCIe USB Hub (has 8 USB slots and 2 USB-C slots, nifty card) and also grabbed an external USB hub (6 slots) with its own power supply
- Still a problem so I borrowed a 1000w power supply from a co-worker (new in box) but that had no effect
- Pulled off the facemask of the Rift S, removed and re-seated both Audio jack and display port cable
- Contacted Oculus support and sent them as many Log files as they asked for using the Diagnostics tool in the Oculus install directory (they can't figure it out)
I'm out of guesses at this point and I'm really hoping there's someone browsing the forums that can offer to try something I haven't yet. I'm even at the point where I'm RMAing my Motherboard in case something's died but this has been a gradual death and given I've done several power-swap tests I don't think it's the power supply either. Oculus won't admit the headset is the problem because re-seating the cables did nothing, so I'm literally drifting towards a star and no way to call the Fuel rats of VR and I'm almost in tears because of the time I've invested in this.
Please... anyone give me a reasonable suggestion I haven't already tried. Thank you pilots, hope to see some of you in-station when this is finally fixed.
