cancel
Showing results for 
Search instead for 
Did you mean: 

After update oculus link not working

deathrament
Honored Guest
Says a quest software update is required for oculus link beta. Install the update from the about section of your setting in your headset.
But in my headset there is no update showing. I opted out of the public test channel but that did nothing.
49 REPLIES 49

Zitronenarzt
Honored Guest
I say it in general. Update 13 is a disaster for "link". 
On my Youtube channel I only have comments with error messages.
I myself cannot test anything because neither of my "Oculus Quest"
glasses can find an update. Messages like: USB cable no longer
works. - PC and Quest Version 13 on both devices you still get
the message that an update must be made. Aborts from the link
connection. Public Test Channel is already at version 14.
Version 13 is already on the computer and the quest does not update.
People are extremely angry in the comments. It's a mess.
You are welcome to look at what people write. But is in German.

youtu.be/E5u0Dttj_9o

AquaHeaD
Explorer

Replect said:

[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.537 {!ERROR!} [RemoteHeadset] matchCount != kVirtualDeviceCount
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.749 {!ERROR!} [xrstreaming] VolumeControl::findDevice() Headphones device not found
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.749 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.749 {!ERROR!} [xrstreaming] VolumeControl::initialize() can't find virtual audio headphones!
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.749 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.749 {!ERROR!} [RemoteHeadset] Failed to create volume control. Result=-1002.
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.749 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.757 {!ERROR!} [xrstreaming] WinUsb_WritePipe(handle:0x0000000000000000, ep:255, len:1024) failed: (6) Das Handle ist ung�ltig.
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.757 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.757 {!ERROR!} [xrstreaming] sendHaptic failed with 13 (Stream terminated? Failed to write schema to topic: I/O error)
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.757 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.757 {!ERROR!} [xrstreaming] Failed to send haptic: -1002
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.757 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.777 {!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicWrite(struct XrspTopic *,const void *,unsigned __int64): topic
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.777 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.777 {!ERROR!} [xrstreaming] XrspTopicWrite(sliceTopics_[sliceIndex], &header2, sizeof(header2)) failed with reslut=6 (topic does not exist).
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.777 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.777 {!ERROR!} [xrstreaming] failed to send frame. result=-1002
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.777 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.783 {!ERROR!} [xrstreaming] Failed to process frame. result=-1002
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.783 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.938 {!ERROR!} [xrstreaming] getAudioControl failed on 0 call with 13 (Stream terminated? Insufficient data returned to read schema: I/O error) after reading 0
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.938 {!ERROR!} [xrstreaming] getAudio failed with 13 (Stream terminated? Insufficient data returned to read schema: I/O error)
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.938 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.938 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.938 {!ERROR!} [RemoteHeadset] Error getting audioControlfrom session. Result=-1002.
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.938 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.960 {!ERROR!} [RemoteHeadset] Error getting hands from session. Result=-1002.
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.960 {!ERROR!} [xrstreaming] getTracking failed with 13 (Stream terminated? Insufficient data returned to read schema: I/O error)
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.960 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.960 {!ERROR!} [RemoteHeadset] Error getting hand skeleton data chunk from session. Result=-1002.
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.960 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.960 {!ERROR!} [RemoteHeadset] Error getting tracking from session. Result=-1002.
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.960 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:38.960 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:39.105 {!ERROR!} [xrstreaming] failed to initialize session when calling sessionWillInitialize: unknown error (21)
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:39.105 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2020-02-06_17.19.14.txt] 06/02 17:37:39.231 {!ERROR!} [RemoteHeadset] matchCount != kVirtualDeviceCount

These are the errors in the log I get when I try to start link now after the new version (v13 Quest and v14 PC). I made sure that I looked at the exact time when I activated Link, so I'm sure the errors are related to the issue. I've tested it twice that way and the errors seem to be the same each time.
—————————————————————————
It seems that Oculus has made a really nice job with this update. ?





KarstenS80
Adventurer

iTesla8 said:

Encode Resolution is set to 0 


"Zero" at this point means "use the default value".

Anonymous
Not applicable
The Oculus team should be ashamed of something .. Is not something tested before ... How shit is that please. I have not been able to use my product for 2 days. And for that I paid 550 euros. For what? for that I can not use it .. The Oculus are incompetent programmers.

Anonymous
Not applicable



iTesla8 said:

Encode Resolution is set to 0 


"Zero" at this point means "use the default value".



Yes, after update all values i changed were set to default, but i changed back and is still working not sure why for others not work.

lenne0815
Adventurer
Headphone device not found... same issue here, trying some thing to get the headphone streaming working correctly but so far no dice 😞

Anonymous
Not applicable
See if the Headphones are available in Device Manager.7hwtkpvel65f.png

lenne0815
Adventurer
Jeah, its there. I un / reinstalled the drivers multiple times now, i disabled anything i could possibly think of etc pp, i cant get the audio to work properly.

BuckR72
Honored Guest
So, this issue remains. After several hours with Support it boils down to this; the latest Oculus Quest firmware is v13. The PC software is on 12 and the Public Chanel PC version is on 14. Apparently the PC Version 13 is being rolled out but it is not available in all territories just yet, but it will be ‘soon’. So, unless both PC and OQ are on the same version number, the Oculus Quest using Oculus Link will not work...for now! I reinstalled the PC software, changed USB port power settings and a few other things for nothing, so save yourself the time and just watch the version numbers!!