Just recently I have noticed that my rift sensor loses connection then reconnects straight away. Only does it in ED. Can play other Rift games there's no problem at all. All my USB hubs are set to non power saving. It's really frustrating and immersion breaking to have to go into rift home to reselect the game. Any help greatly received. Only been doing this last couple of weeks.
CV1 problem
- Thread starter RaistlinUK
- Start date
you really not supposed to use USB powered hubs for the Rift. Check the compatibility guide on the Oculus Support side for specific recommendation otherwise this issue will get only worse over time and you have a lot more frustration. Hubs mean shared bandwidth between ports and the CV1 requires dedicated bandwidth for each subcomponent (sensor, HMD and later the Touch). The Xbox controller--if used--can be plugged into a hub.
https://support.oculus.com/1709142099318823
https://support.oculus.com/1709142099318823
What a coincidence. I have recently been experiencing the exact same problem.
My sensor momentarily disconnects then reconnects almost straight away. I do not have any powered usb hubs - only the installed ports from the motherboard. Going to oculus home and fumbling for the remote to reset back to the game during a hazrez sesh is no fun!
I have never had this issue before about a week ago and nothing has changed on my system.
Now I have to point out that I only have the cv1 plugged into a usb3. My sensor has to use usb2 as my mb has incompatible usb3 chipset (made by via), and as my mb is a microATX, the PCIe port is underneath my 970 grafix card! (so I cant use my recommended 'inatek' usb3 card). The usb2 connection to oculus sensor has worked perfectly for tracking since my cv1 arrived in June (I play ED for minimum 20hrs/week).
This issue has me at a loss right now. I thought it must be a problem unique to my setup - but as you have experienced the exact same thing at about the same time - there could be a link.
I'll keep playing around and see if I can resolve it. I would be interested if anyone finds a resolution.
CMDR Blastard
Last edited:
Where does it say cannot use powered usb?
I recently suffered computer freezes and crashes due to dying ram. In the course of my troubleshooting, I was in contact with Oculus and the representative admitted to me that in addition to Windows 10 anniversary update causing USB ports to not be re-powered after being powered down, Oculus's drivers also currently have a problem where the the sensor sometimes can't be detected. The only way for me to fix that problem so far is to reconnect the sensor the sensor.
Oculus is aware of that problem and to my knowledge is still working on a fix.
Oculus is aware of that problem and to my knowledge is still working on a fix.
There are at least a couple of issues that are causing sensor disconnects.
1. Windows 10 has a power-saving feature whereby it can disables and reenable USB ports. The anniversary update broke this and apparently hasn't been fixed yet.
Workaround: One work around is to go into device manager, right click on the USB port(s), go to the power management tab and uncheck the box that allows windows to turn the port off. You can also customize your power-management profile in settings and turn off the above feature.
2. Oculus released an update that unfortunately also started causing sensor disconnect issues. They released a patch for it, but some people (including myself) are still experiencing disconnects.
1. Windows 10 has a power-saving feature whereby it can disables and reenable USB ports. The anniversary update broke this and apparently hasn't been fixed yet.
Workaround: One work around is to go into device manager, right click on the USB port(s), go to the power management tab and uncheck the box that allows windows to turn the port off. You can also customize your power-management profile in settings and turn off the above feature.
2. Oculus released an update that unfortunately also started causing sensor disconnect issues. They released a patch for it, but some people (including myself) are still experiencing disconnects.
![[HJ]-RedRaven](https://forums-cdn.zaonce.net/data/avatars/m/67/67389.jpg?1553527112){kind=avatar}
It was a Oculus Rift update that caused it, like Redwalljp said above. They've released a fix but its not working 100% for me still. https://forums.oculus.com/community/discussion/42135/fix-for-sensor-disconnection-issue#latest
Last edited:
Same here.
Mine drops and comes back, sometimes not till I go back home.
Beats me.... I'll try the fix and see what happens.
Mine drops and comes back, sometimes not till I go back home.
Beats me.... I'll try the fix and see what happens.
Ive started getting this since the last Oculus update a couple of weeks back (the one that was released to fix this problem) and now I can't play Elite nor any game for longer than a few minutes before getting kicked back into Oculus home. Ive read the thread about it in the Oculus forum and it looks like its a Motherboard issue for most. Does anyone else have an Asus Maximus Hero VII board and manage to get this fixed?
This is a disaster! I can't beta test 2.2 now
(((
This is a disaster! I can't beta test 2.2 now
(((