cancel
Showing results for 
Search instead for 
Did you mean: 

Link and AirLink not working on V41

travelmanics
Level 3

Updated to Quest V41 and PTC V41 this morning and neither Airlink or link are working.  Was fine yesterday on version 40.  When you try to connect via either link or Airlink you get 3 flashing dots and then back to the Oculus HOME screen in Quest.  Confirmed oculus software is running and shows as Quest 2 connected.  In the service logs I am getting the following

 

23/06 11:38:31.933 {INFO} [DML:HMDNormal] HMD Reporting state change: {'State':'NotDetected','IsDetected':0,'IsReady':0,'Mode':'Unknown','IsWirelessReady':0,'IsRebooting':1,'IsFirmwareOutOfDate':0}
23/06 11:38:35.070 {DEBUG} [Server] Connection open for pid: 10124, file: OculusDebugTool.exe
23/06 11:38:35.070 {DEBUG} [Server] Accepted a client from pid: 10124(OculusDebugTool.exe) running version (prod = 1).1.73.0(build = 0) feature version = 0. Server is version (prod = 1).1.73.0(build = 0) feature version = 0
23/06 11:38:35.070 {INFO} [OculusAppFramework.cpp] App Event ClientInitialize RequestVersion|Invisible for pid 10124
23/06 11:38:35.070 {DEBUG} [Server] UpdateFocusedVirtualHmd: ConfigureTracking Off (0)
23/06 11:38:35.070 {DEBUG} [Server] Broadcasting VR focus changed (to 0) event to clients.
23/06 11:38:35.070 {DEBUG} [Server] UpdateFocusedVirtualHmd: No connections to focus
23/06 11:38:35.070 {DEBUG} [RemoteHeadset] RemoteHeadsetPlugin::GetHeadsetState VsyncToFirstScanline = 0.011280
23/06 11:38:35.071 {DEBUG} [Server] Broadcasting VR modal system overlay present event to clients.
23/06 11:38:35.071 {INFO} [PermissionServer] APIPermissionServer::AddProcess: Process OculusDebugTool.exe was already present.
23/06 11:38:35.071 {DEBUG} [Server] Hmd_GetHmdInfo
23/06 11:38:35.071 {DEBUG} [RemoteHeadset] RemoteHeadsetPlugin::GetHeadsetState VsyncToFirstScanline = 0.011280
23/06 11:38:35.071 {DEBUG} [Server] AreExperimentalExtensionsEnabled. pid: 10124
23/06 11:38:35.071 {DEBUG} [Server] ArePassthroughExtensionsEnabled. pid: 10124
23/06 11:38:35.071 {DEBUG} [Server] Connection open for pid: 10124, file: OculusDebugTool.exe
23/06 11:38:35.071 {INFO} [Server] Debug console connected. pid: 10124
23/06 11:38:35.071 {INFO} [Dbg:Console] Received cmd: "rift.get_debug_hmd"
23/06 11:38:35.071 {INFO} [Dbg:Console] Command returned: status: 0, output:"0"
23/06 11:38:35.072 {INFO} [Dbg:Console] Received cmd: "asw.Mode"
23/06 11:38:35.072 {INFO} [Dbg:Console] Command returned: status: 0, output:"off"
23/06 11:38:35.081 {INFO} [FastIpc] Connected clientID 3
23/06 11:38:35.083 {INFO} [os/process] Waiting for pid 10124
23/06 11:38:35.126 {INFO} [AppTrackerManager] Adding new tracker: 10124 (oculus-diagnostics)
23/06 11:38:36.865 {DEBUG} [xrstreaming] receive pong: org 97120035700 recv 582150871078 xmt 583620915035 (received at 98590324600), offset divergence 0
23/06 11:38:36.865 {DEBUG} [xrstreaming] new clock offset=485030712906 (rtt: 244943, dispersion: 1073741823500000103, jitter: 50)
23/06 11:38:36.865 {DEBUG} [xrstreaming] receive ping: org 0 recv 0 xmt 583621046650 (received at 98590458200), offset divergence 485030712906
23/06 11:38:41.865 {DEBUG} [xrstreaming] receive pong: org 102130781300 recv 587161823055 xmt 588621305867 (received at 103590516500), offset divergence -101374
23/06 11:38:41.865 {DEBUG} [xrstreaming] new clock offset=485030915561 (rtt: 252388, dispersion: 536870911500037655, jitter: 202655)
23/06 11:38:41.865 {DEBUG} [xrstreaming] receive ping: org 0 recv 0 xmt 588621433575 (received at 103590670400), offset divergence 101281
23/06 11:38:46.505 {INFO} [OVRServer] Graceful shutdown: Exited server event loop. Stopping JPEG, OAF, DXDIAG
23/06 11:38:46.505 {INFO} [HardwareSDKRelay] Service connection readiness changed to false
23/06 11:38:46.505 {INFO} [RemoteHeadset] Plugin mode changed to off
23/06 11:38:46.505 {INFO} [RemoteHeadset] Link plugin shutting down
23/06 11:38:46.505 {INFO} [RemoteHeadset] Received request to stop Link
23/06 11:38:46.505 {DEBUG} [xrstreaming] transitioning XrspSession state to Disconnected
23/06 11:38:46.505 {DEBUG} [xrstreaming] trying to send transactional message BYE
23/06 11:38:46.505 {DEBUG} [xrstreaming] sent transactional message BYE: success (0)
23/06 11:38:46.507 {!ERROR!} [xrstreaming] WinUsb_ReadPipe(handle:0x0000000000000000, ep:255, len:1024) failed: (995) The I/O operation has been aborted because of either a thread exit or an application request.
23/06 11:38:46.507 {DEBUG} [xrstreaming] basic session ending.
23/06 11:38:46.507 {!ERROR!} [Kernel:Error] OVR Error:
Code: -6102 -- ovrError_XRStreamingUSBIssue
Description: WinUsb_ReadPipe(handle:0x0000000000000000, ep:255, len:1024) failed: (995) The I/O operation has been aborted because of either a thread exit or an application request.
OVRTime: 108.232632
Time: 2022-06-23 11:38:46 [507:803:0]

 

Tried system reboots but always the same result.

 

Any help?

1 ACCEPTED SOLUTION

Accepted Solutions

travelmanics
Level 3

Problem is fixed.  After several hours of testing it appears to be an issue with the V41 Quest 2 software rather than the V41 PC software.  Tried this on Windows 10 (V41 PC software oculus) and Windows 11 (V39 software oculus).

 

Issue is related to the "Encode Resolution Width".  Was using either 3664 or 4080 on Version V40 with no issues.  However, if this is set to anything other than 0 link will not load.  Tried this on both versions of windows listed above with Quest headset at V41 software version.  

 

You will get three dots and drop back out to the Oculus home menu on quest.  Doesn't link something associated with the USB. You can see the errors in the OVRServer_x64 service.

 

Oculus please look into this and fix.  Pain in the backside.

View solution in original post

10 REPLIES 10

TomCgcmfc
Level 15

Maybe try doing a factory reset.  Otherwise, contact oculus support I guess.

 

V41 works great for me!

9 9900k, rtx3090, 32 Gb ram, 1tb ssd, 4tb hdd. xi hero wifi mb, 750w psu, Q2 w/Air Link, Vive Pro

OculusSupport
Community Manager
Community Manager

Hey there, travelmanics! 

 

We would love the opportunity to step in and further assist you with your Link errors. Also, please give yourself a pat on the back for helping us out by providing your PC specs. So our team of specialist can dig deeper into this, we ask that you please submit a ticket here: Contact Us! You will be able to have a one-on-one with our team and we advise you to please share every details of your PC with us. 

 

We got your back and hope to hear from you soon! 

Macproracer
Level 4

ME TOO - Since updating to V41 I get - {!ERROR!} [Kernel:Error] OVR Error:  ovrError_XRStreamingUSBIssue,

with the XRStreaming USB error producing an [xrstreaming] couldn't open device USB.

Interestingly when I remove/delete V41 then reinstall V40 all works well as before so IMHO it's a problem with V41 and something maybe to do with the USB. 

I asked how can I stop Oculus downloading and installing V41 as I'm happy to stay with V40 until they sort this out - In reply they asked me what type of USB cable I was using but I had already told them (at least twice) it is a Meta Quest Fibre Link cable (the expensive one) and told me to log a bug report. 

 

All in all it feels a bit like we are just beta testing V41 for Facebook - I'll probably stick mine on eBay and look into getting a more mature product.

 

"Good Luck with your Quest"

I normally use Air Link but I just tried v41 with a pretty standard Link cable and it worked fine.

9 9900k, rtx3090, 32 Gb ram, 1tb ssd, 4tb hdd. xi hero wifi mb, 750w psu, Q2 w/Air Link, Vive Pro

travelmanics
Level 3

Problem is fixed.  After several hours of testing it appears to be an issue with the V41 Quest 2 software rather than the V41 PC software.  Tried this on Windows 10 (V41 PC software oculus) and Windows 11 (V39 software oculus).

 

Issue is related to the "Encode Resolution Width".  Was using either 3664 or 4080 on Version V40 with no issues.  However, if this is set to anything other than 0 link will not load.  Tried this on both versions of windows listed above with Quest headset at V41 software version.  

 

You will get three dots and drop back out to the Oculus home menu on quest.  Doesn't link something associated with the USB. You can see the errors in the OVRServer_x64 service.

 

Oculus please look into this and fix.  Pain in the backside.

So all's well I guess, lol!

9 9900k, rtx3090, 32 Gb ram, 1tb ssd, 4tb hdd. xi hero wifi mb, 750w psu, Q2 w/Air Link, Vive Pro

Hi TravelM - thanks for looking into this - it's a great help when someone takes the time to try and identify the problem. So just to clarify - Post above states "Problem is fixed" (great news) but can you please help me with the steps you took to fix it. Are you saying set "Encode Resolution Width" to 0 (default) and V41 of link PC software will load with either Windows 10 and 11 provided the Oculus 2 headset is up to date (ie V41 also) - Yes??

 

My problem is Link V41 will load up but is unusable - very very laggy (but V40 is OK)

Ohhh - PS TravelM - One more question if you please - don't suppose you know how to stop [PacketManager] doing the update check on core software - because I would be happy to stick with V40 of the Link PC Software until facebook sort this out. Also I prefer to have some element on control over when core software is updated on my PC.  

Thanks Again

Yep. The only step I took was to delete whatever value is in encode resolution width and then restart the oculus service. Sorry cannot help about the packet manager. I assume there is some kind of update service that runs in the background. Anyway at the moment but if I get when I get home will have a look