cancel
Showing results for 
Search instead for 
Did you mean: 

Odd issue with Rift S (PLS help)

knifebutterreal
Honored Guest

for a few months I have assumed my rift s has bitten the dust and is in the grave, though, when I started it up today to see if I can maybe fix it, I tried connecting it to a 2.0 USB. For context I tried every USB 3 and 3.1 slot on my pc just for it to say my display port connection is not working, and as expected the display doesn't not work and nothing else with it, so I thought the cable was damaged and I would just have to wait to get a quest. Back to the USB 2.0, it started working, the only issue was the sensors didn't work, which I just think is the fact that it is not compatible with 2.0, so, WHAT GIVES?!!! Why does it not work at all on every single supposedly compatible port except for the one its not supposed to work with, If its working there it surely has to work with the other ones like it did before... if I can get any help on this it would be amazing. Thank you to anyone who may come across this.

1 ACCEPTED SOLUTION

Accepted Solutions

OK so yeah, my S is ok in all of the USB 3 ports on my PC and same as you, no controller or headset tracking (other than the internal inertial headset tracking) when plugged into USB 2, as expected.

I can only suggest double checking your PC's internal connections, if you're using a USB PCI-e card, reseat it, if you're using motherboard USB headers, disconnect and re-connect. Also, check the motherboard power connections and check you're getting the correct voltages... a tired PSU can throw up all sorts of weird little faults when it's on its way out!

I suppose it's still possible to be a cable problem or pin damage that gives the behaviour you're getting, just that it only manifests itself with USB 3? I'm not an expert though and really I'd look to it being a fault with your PC or it's USB controllers or internal connections, maybe even a controller driver issue if you've had an update of some sort.

13700K, RTX 4070 Ti, Asus ROG Strix Z790-A Gaming, Corsair H150i Capellix, 64GB Corsair Vengence DDR5, Corsair 5000D Airflow, 4TB Samsung 870 , 2TB Samsung 990 Pro x 2, DK2, CV1, Rift-S, Quest, 2, 3, Pro

View solution in original post

5 REPLIES 5

Hi @knifebutterreal are all of your USB 3 ports on the same hub? are they on your motherboard or on an expansion card?

13700K, RTX 4070 Ti, Asus ROG Strix Z790-A Gaming, Corsair H150i Capellix, 64GB Corsair Vengence DDR5, Corsair 5000D Airflow, 4TB Samsung 870 , 2TB Samsung 990 Pro x 2, DK2, CV1, Rift-S, Quest, 2, 3, Pro

knifebutterreal
Honored Guest

They are all Motherboard USB 3 ports, I even tried the 3.1 ports. I experimented with 3rd party software and for some reason the rift s does not work with the oculus app entirely before and after the 3rd party software, I used it and after it now favors using openxr runtime for steamvr and even then its hit or miss, knowing this, it must be a software issue. I also know my headset is no longer supported by meta which kind of sucks for me, a past consumer, but I cannot fix that. I did some research and it seems to be corrupted USB drivers each time after using it with the headset from the oculus software itself, and was told the only way to fix it is to completely reinstall windows 10 onto my windows 11 machine. I am heavily disappointed and would like another way to fix this...

knifebutterreal
Honored Guest

I have pretty much given up on it for the past month after trying and trying to find other ways, I will just purchase the current Meta Quest 3 headset even though I have a completely fine pcvr headset that could be used.

I'll dig out my Rift-S and see if I have the same issue. It might give a clue as to whether there's been an update that's messed with the headset or whether it's something specific to your setup. Will report back!

13700K, RTX 4070 Ti, Asus ROG Strix Z790-A Gaming, Corsair H150i Capellix, 64GB Corsair Vengence DDR5, Corsair 5000D Airflow, 4TB Samsung 870 , 2TB Samsung 990 Pro x 2, DK2, CV1, Rift-S, Quest, 2, 3, Pro

OK so yeah, my S is ok in all of the USB 3 ports on my PC and same as you, no controller or headset tracking (other than the internal inertial headset tracking) when plugged into USB 2, as expected.

I can only suggest double checking your PC's internal connections, if you're using a USB PCI-e card, reseat it, if you're using motherboard USB headers, disconnect and re-connect. Also, check the motherboard power connections and check you're getting the correct voltages... a tired PSU can throw up all sorts of weird little faults when it's on its way out!

I suppose it's still possible to be a cable problem or pin damage that gives the behaviour you're getting, just that it only manifests itself with USB 3? I'm not an expert though and really I'd look to it being a fault with your PC or it's USB controllers or internal connections, maybe even a controller driver issue if you've had an update of some sort.

13700K, RTX 4070 Ti, Asus ROG Strix Z790-A Gaming, Corsair H150i Capellix, 64GB Corsair Vengence DDR5, Corsair 5000D Airflow, 4TB Samsung 870 , 2TB Samsung 990 Pro x 2, DK2, CV1, Rift-S, Quest, 2, 3, Pro