cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

"Oculus isn't working properly" and "Oculus Link stopped working" no matter what I do

Anthony9980
Level 3

Hello, everyone. Have to post here as a last resort, since I don't know what else to do ๐Ÿ˜ž

 

I have bought a Quest 2 two weeks ago. and on the first day of the purchase Link worked properly, and the experience was amazing. On the day after that - it just stopped working, with no apparent reason. The PC was new, USB port never used before, cable was a brand-new Oculus Link. But all I get is three dots for a few seconds, and then I am back in Oculus Home. Oculus app passes all tests, and I can easily transfer files to the headset, but no ability to use Link

 

I have contacted support, who after a generic reply just ignores me for two weeks already. And I have read countless forums, reddits, watched countless videos with no end in sight

 

What I did already:

1. Check compatibility (Ryzen 3600 & AMD 5700 XT) - compatible

2. Downgrade AMD drivers

3. Opt it an out of beta in Oculus App

4. Factory reset Oculus, re-install the app

5. Manually downgrade the Oculus app

6. Install/Remove Virtual Desktop Streamer, including directly removing any leftover drivers

7. I have bought also another compatible cable, so I have official Facebook Link and third party-one, both not working

8. Set Real-time priority to any oculus-related process in the Task Manager

9. I also did a full re-install of Windows, also with no results

 

The only possible issue which I still see, myself, is that the version of Oculus on the headset and the Oculus app do not match exactly, and I was not able to match them... Headset is on v27, while my app is still v26. If I use the Beta channel, the app can be upgraded to v27, but the full version number is still a bit different

 

The logs show several interesting parts, which I honestly don't get. Does anyone, maybe, know what I should be looking into? I am beyond desperate right now ๐Ÿ˜ž

 

-----------

[Service_2021-04-03_09.26.13.txt] 03/04 09:26:17.417 {!ERROR!} [OAF ERROR] software\oculussdk\pc\oaf\liboaf\os\file.cpp(1012) : Failed to open file: Access is denied. (1971052)
[Service_2021-04-03_09.26.13.txt] 03/04 09:26:17.417 {!ERROR!} [OAF ERROR] software\oculussdk\pc\oaf\liboaf\os\file.cpp(1012) : Failed to open file: Access is denied. (1971052)

-----------

[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.056 {!ERROR!} [PluginManager] Failed to load HeadsetPlugin: EmulationPluginAddition; got error code: -1010
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.118 {!ERROR!} [xrstreaming] Unable to get H264 max temporal layers: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.118 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.118 {!ERROR!} [xrstreaming] Unable to get H264 fixed slice mode support: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.118 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.118 {!ERROR!} [xrstreaming] Unable to get H264 num hw instances: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.118 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.134 {!ERROR!} [xrstreaming] Unable to get H264 max temporal layers: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.134 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.134 {!ERROR!} [xrstreaming] Unable to get H264 fixed slice mode support: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.134 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.134 {!ERROR!} [xrstreaming] Unable to get H264 num hw instances: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.134 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.134 {!ERROR!} [xrstreaming] Unable to get H264 max temporal layers: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.134 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.134 {!ERROR!} [xrstreaming] Unable to get H264 fixed slice mode support: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.134 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.134 {!ERROR!} [xrstreaming] Unable to get H264 num hw instances: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.134 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.150 {!ERROR!} [xrstreaming] Unable to get H264 max temporal layers: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.150 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.150 {!ERROR!} [xrstreaming] Unable to get H264 fixed slice mode support: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.150 {!ERROR!} [xrstreaming] Unable to get H264 num hw instances: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.150 {!ERROR!} [xrstreaming] Unable to get H264 max temporal layers: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.150 {!ERROR!} [xrstreaming] Unable to get H264 fixed slice mode support: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.150 {!ERROR!} [xrstreaming] Unable to get H264 num hw instances: 11
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:33.483 {!ERROR!} [os/file] Unable to open path 'C:\AMD\Win10-Radeon-Software-Adrenalin-2020-Edition-20.10.1-Oct19\Bin64\RadeonInstaller.exe [5]
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:34.329 {!ERROR!} [Kernel:Error] [Aggregated 5 times] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:34.632 {!ERROR!} [MobileConfigWrapper] getBool() received invalid param: oculus_store:is_rift_redesign_enabled
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:42.927 {!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.
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:42.927 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:42.927 {!ERROR!} [xrstreaming] Failed to parse PCI vid and pid from string ""
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:42.927 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:42.927 {!ERROR!} [xrstreaming] Failed to parse PCI vid and pid from string ""
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:42.927 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:42.927 {!ERROR!} [xrstreaming] Failed to parse PCI vid and pid from string ""
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:42.927 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:42.927 {!ERROR!} [xrstreaming] Failed to parse PCI vid and pid from string ""
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:42.927 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:42.951 {!ERROR!} [xrstreaming] inbound data processing loop exited: transport closed (12)
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:42.951 {!ERROR!} [xrstreaming] Failed to parse PCI vid and pid from string ""
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:42.951 {!ERROR!} [xrstreaming] Failed to parse PCI vid and pid from string ""
[Service_2021-04-02_20.29.32.txt] 02/04 20:29:45.230 {!ERROR!} [PluginManager] shutdown(): Plugin (handle = 4) with serial no headset serial yet still held but proceeding with shutdown

17 REPLIES 17

Exact same problem here too. No response from oculus yet...

I kind of got it to work again.  Had to uninstall the software,  then remove all related folders and registries in windows.  Do a fresh install after restart and it started to work again.  However,  if i tried to change the refresh rate,  the problem occurs again,  so pretty much stucked at 72 hz now. 

abieluu
Level 2

I got the same problem,  no reply from support.  After a day of trying,  I kind of got it to work again.  Had to uninstall the software,  then remove all related folders and registries in windows.  Do a fresh install after restart and it started to work again.  However,  if i tried to change the refresh rate,  the problem occurs again,  so pretty much stucked at 72 hz now. 

CompSciGod
Level 2

I got it working. You can use airlink to force link into a working state. With 90 hertz as well

Anthony9980
Level 3

So after more than a month, after I dug in every direction, the only thing which helped me was an absolutely clean Windows re-install

 

Most likely the issue I had was about the conflict between some Virtual Desktop Streamer files and Oculus Link. Mind, though, that solutions like "uninstall Virtual Desktop Streamer and its service" don't help, because this does not remove the drivers. I have also manually deleted drivers and played with some Windows services - to no avail

 

If someone encounters this problem and nothing from other posts helps you - try the full re-install, but also keep in mind that you need to have a clean installation. Using Windows factory reset will not help - I have tried

 

This also should help in case Air Link does not work. It was not working for me with the same winusb error in logs - but all started working as a charm after Windows re-install

View solution in original post

same problem for about a 2 or 3 weeks, OCulus support can't help

r-lupus
Level 2

Hi,

Same problem for me again, since the V29 is installed. And what I don't understand is the fact that there is no option to come back on a previous version. This could really help to find the reason between hardware issues, automatic drivers installation and so one. Oculus should work on this...

Exact same problem here, and most likely not a VD isdue, since it started before I got VD