Fix for Sensor Disconnection Issue

[cybereality]

We've just started rolling out a possible fix for the repeated sensor disconnection issue. This is a problem that could cause the sensor to disconnect while idle on certain hardware configurations. Although we had some trouble reproducing the exact problem in our lab, we have a good idea of what the core issue was and believe it may be resolved.

Some customers have already received the update, and everyone else should have it within a few hours. The update should happen automatically, but you'll have to just unplug and replug the sensor to reset its state.

I'd recommend people wait until later this evening to test and see if the fix actually resolves their issue. Either way, please report back so we can understand if the fix was a success. Thanks.

[XMerc]

Yes some apps definitely cause more frequent sensor disconnects than others. Watching videos in the Oculus Video app seems to trigger errors every 5 or 10 seconds for me.

[XlordB]

Im getting the disconnect in apps and also when not using the rift i,e when the rift software is closed..  I cannot pinpoint the problem as literally the problem is so random it is like someone walking in the room and pulling the usb plug out for it. it happens even if i sit and do nothing on the pc. im convinced theres some kind of link between the programming of how the power is being routed through the usb.. whether thats on windows side or oculus i have no idea but it seems to be that ..

[XMerc]

@cybereality , 

Is there somewhere we can download Oculus Home 1.6? I think testing that may shed some light or at least rule out certain potential problems. Thanks.

[fuchsi891]

i got a few disconnections every day...

[Anonymous]

@cybereality logs attached.

Last night I downloaded the
ovr_sdk_win_1.7.0_public files and compiled the x64 release build of the Oculus World Demo hoping to
capture the error in the visual studio debugger. After letting it sit for a
while, the problem did happen but sadly it didnt throw an exception or anything
on the application side. The logs are from a few moments later.  Here is the console output from when it happened:

05/09 20:49:36.303
{DEBUG} [Kernel:Default] Loading ground collision models... 

05/09 20:49:36.303 {DEBUG} [Kernel:Default] done. 

05/09 20:49:36.594 {INFO} [Kernel:Default] [HMDState] Requested to
SetForegroundWindow(1046ell) 

05/09 20:49:36.644 {INFO} [Kernel:Default] [HMDState] Detected the active
window handle changed to 1046ell 

05/09 20:49:36.644 {INFO} [Kernel:Default] [HMDState] Requested to SetForegroundWindow(1046ell) 

05/09 20:49:36.792 {INFO} [Kernel:Default] [HMDState] Requested to
SetForegroundWindow(1046ell) 

05/09 20:59:47.574 {INFO} [Kernel:Default] [HMDState] Requested to
SetForegroundWindow(1046ell) 

05/09 20:59:47.599 {INFO} [Kernel:Default] [HMDState] Requested to
SetForegroundWindow(1046ell) 

The thread 0xc0 has exited with code 0 (0x0). 

The thread 0x2350 has exited with code 0 (0x0). 

The thread 0xe98 has exited with code 0 (0x0). 

The thread 0x65c has exited with code 0 (0x0). 

05/09 21:45:19.858 {INFO} [Kernel:Default] [HMDState] Requested to
SetForegroundWindow(1046ell) 

05/09 21:45:19.859 {INFO} [Kernel:Default] [HMDState] Requested to
SetForegroundWindow(1046ell) 

05/09 21:45:21.973 {WARNING} [Tracking:Filter] Prediction interval too high:
0.118885 s, clamping at 0.100000 s 

05/09 21:45:23.427 {DEBUG} [Kernel:Default] [Client] Disconnected 

05/09 21:45:23.428 {!ERROR!} [CAPI] OVR Error: 

Code: -3003 -- ovrError_ServiceConnection 

Description: Disconnected 

OVRTime: 20236.592336 

Time: 2016-09-05 21:45:23 [428:17:200]

05/09 21:45:23.428 {!ERROR!} [Kernel:Error] HMD
no longer present. 

05/09 21:45:23.428 {!ERROR!} [Kernel:Error] Client disconnecting with active
texture sets. This will lead to instability in the calling application 

The thread 0x2b28 has exited with code 0 (0x0). 

05/09 21:45:23.430 {!ERROR!} [Kernel:Error] Invalid ovrSession provided. 

05/09 21:45:24.430 {!ERROR!} [Kernel:Error] Invalid ovrSession provided. 

[cybereality]

@Ryder35 and @Turranius , it looks like you two are having issues with the USB 2.0 mode. In this case, USB 3.0 may side-step the issue (assuming you can use USB 3.0). Also, do you have any bright windows behind you or something that would interfere with the sensor?

[XlordB]

Update, I fixed my problem for now time will tell if its sticks. So what did i do??

Im on a z97-a motherboard from asus I reinstalled windows 10 home. but before i started the install i disabled all my unused sata devices etc kept all usb on made sure only usb to be plugged in was mouse and keyboard installed windows. Updated it, did not install any drivers from asus site at all. let windows update fully. Did "NOT" update to anniversary.

got the latest nvidia driver ends in 372.70 
used dduninstaller on the generic nvidia driver that the update installs
rebooted installed nvidia driver as custom, picked only the driver the hd audio and the physx nothing else.

all went well.

re enabled my other two storage drives in bios.


Next i installed the oculus setup plugged in the rift etc when it asked me, went through all the steps.. and now... well its been running for about 15 minutes with not one single disconnect.. I am currently refusing to update my windows to anniversary.. until oculus gets a better software patch working with it.

I am also now shattered picked a stupid time of night to try this lol but im glad i did.

oh yes i almost forgot now my rift is recognized in oculus software as being usb 3.0.

[cschlik]

I continue to get the disconnect.  Fresh win10 install with only Oculus software.  inateck usb.

[Jokergod2000]

I'm still getting it every few hours

[UnFknBLievable]

Always. Windows and oculus need to sort some shit out.