This is an issue I've struggled with for the better part of a couple of weeks now. This is an issue that many other users seem to have struggled with both recently and years past from now. This isn't even the first time I've encountered an issue like this. And without a doubt this is something that Oculus/Meta/whatever is already more than aware of. But I 'think' I've identified a root cause for this issue, it's just a matter of figuring out where to go from here.
Context/Symptoms - As I have already said, this issue arose a couple of weeks back. Went to don my headset, and the first thing I see is a black screen with three blinking dots in the middle of my line of sight. I can still hear the sound coming out of my headset though. Chances are, you already have an idea of what I'm talking about.
I went straight into the device setup for my Rift S device, thinking just a simple 'reset' would fix it. But then:
You can kind of guess where this is going.
After a lot of futilely attempting every basic workaround I could find online, eventually going into the Device Manager I noticed something. For the uninitiated, when your Rift S headset is in fully working order, your Device Manager should show two separate 'Rift S USB Hub' entities under the Universal Serial Bus section. But for me, it looks more like this:
(Also included the other USB devices here to give a better idea of what I'm working with - maybe something here is relevant?)
For the record, this shows up usually when I have the headset plugged in to the powered USB 3.0 hub I bought specifically to combat this issue. Otherwise, when plugged into the computer itself, sometimes only the single Rift S hub shows up, but not the second. Perhaps something to do with how much power the headset is receiving, which is apparently a possible factor? Which is the reason I got that powered hub to begin with, but I digress.
Anyway yes, I've tried every port, and yes, I've ensured that it is always a 3.0 (blue) port. Something else that might be worth noting is that the blue light on the front of the headset isn't turning on, as if the sensors aren't being activated whatsoever.
So now that I've identified (or at least I think I have) that the issue 'might' be driver-related, I tried a load of other workarounds and solutions - which I will list further down - but none of them have yielded any positive results, which leads me here. This is my last ditch effort to fix this, and if this ends up going nowhere I'll most likely ditch this PoS entirely and find some other VR kit that will actually work - preferably not from Oculus/Meta. (Don't worry, all of my VR games are on Steam, so I will be losing literally nothing)
Attempted Solutions - Oh boy, this is probably gonna be so long that I'll likely miss something, but here goes nothing:
What I Haven't Tried -
Computer Specs (cause I know someone will inevitably ask about this) -
Motherboard: AMD Ryzen 5 3400G with Radeon Vega Graphics 3.70 GHz
16GB of RAM
GPU: NVIDIA GeForce GTX 1660
OS: Windows 10 Home
This machine is 100% VR-capable, I have without a doubt played VR titles on this machine with performance issues only arising if I have GeForce Experience screen-recording/instant replay enabled.
Maybe there's more, idk, I just mentioned everything I thought was relevant.
I have not made any modifications to this machine since I bought it, this is the hardware it came with.
And last but not least: Logs -
***EDITED MESSAGE TO REMOVE PII***
I think that about covers everything. I tried to be as thorough and comprehensive in this post as I possibly could because I just want to know once and for all if this is a problem that can actually be fixed or if I should just give up on Meta VR for good. I'm heavily leaning toward the latter atm, so consider this my last hope.
Hey again! We just wanted to check back in with you. If you still need assistance please select our name to get to our profile page, or click here. Next, click "Send a Message" to privately message us! Please remember, you must be signed into the community first to send us a private message.
I don't have the adapter, I was only asking if someone else has tried this method and yielded good results. I might get it and try, but I am not sure it will work. It should theoretically work, since the USB-C has more power for the headset as well, I don't see why it can't be a win-win with the adapter.
I'll get back with a reply if this works for me.