Advice needed: Rift S Guardian resetting multiple times per session

Hello all. I did a lot of research before posting here, but haven't found any conclusive answer yet.

I've had my Rift S for about six months, and I've played E:D in spurts several times during that period. Up until a week ago, the only issue I ever had was the seating position abruptly changing itself now and then, but I found ways to mitigate that, though not prevent it entirely.

About a week ago (more like 4-5 days ago) I suddenly started getting a much more serious error. I'd get the grey-out that you get just before a tracking reset, but it would last longer than usual, and then the Oculus software would take me right out of the game and prompt me to set up Guardian. At its worst, it can happen multiple times, just minutes apart, and at best I get maybe a couple of hours without being interrupted.

The lighting in this room hasn't changed significantly in the past week, but after googling the issue I turned on an extra lamp to give the headset some extra tracking data. I can't tell if it's helped at all - the issue keeps happening, and I'm not sure if the frequency has changed. Tonight it happened three times in the space of about half an hour, and I damned near threw my headset across the room, I was so frustrated.

Has anyone else had this issue and been able to resolve it? It seems to only happen in E:D - I played Batman Arkham VR for a few hours about a week ago and it didn't drop out once.

In case this is helpful, I'm running Windows 10 and have a GTX 1080, controlling the game with an X-52 Pro, and I run the game from Steam (I hate having that extra software overhead, but what can ya do). I don't know if this makes a difference, but I will often listen to podcasts via YouTube on Firefox while playing.

Any thoughts? Thanks everyone.
 
I cannot relate to this exact fault, but think about things like which USB port you are plugged into, any other USB powered peripherals drawing power from the USB sockets, particularly the USB socket 'paired' with the one that you have the Rift connected to.

Do not use extension cables to connect the rift, or connect it through USB hubs. Maybe try a different USB port, ensure that you have power saving options turned off on the port that has the rift connected...

Other than that, it could be a faul developing in the headset or cable. One othet thought...You could try reseating the cable at the headset end (unclip/remove the face surround, then you can disconnect the cable from the back of the headset and reconnect it)
 
Thanks for the thoughts. I knew about the potential issues with hubs, so I connected it directly to the back of the PC (weirdly enough to a USB 3.0 port labelled "VR ready").

I now suspect that YouTube running in Firefox is part of the problem. I played without a podcast the other night, and had the smoothest experience - quick loads, smooth framerates, no headset tracking dropouts (not even those quick self-resets). I suspect it's a CPU issue - the browser, YouTube, and audio decompression as all CPU-intensive, and so is the inside-out tracking on the Rift S. I think in future I'll download my podcasts and play them on Groove, because it's very lightweight in the system.
 
Following up for others with similar issues: now 99% sure it's either an issue with maxing out the CPU or running out of physical RAM and having to switch to RAM-disc. If you're having the problems I described above, try closing down background programs you aren't using (like your browser, iTunes, and other known system resource hogs) before loading the game up. I've left my browser open but closed unnecessary tabs and I'm playing podcasts from a dedicated low-resource podcast player, and my performance is MUCH better. Not perfect, but a vast improvement. I'll report back if I learn anything new.
 
I'm also getting better results from loading Steam VR from Oculus and then launching ED from within Steam Home, instead of launching directly from Oculus. Don't know why it makes a difference, but I've had zero tracking issues tonight.
 
Back
Top Bottom