cancel
Showing results for 
Search instead for 
Did you mean: 

Quest 2 Air Link Connecting but stuck on loading screen

minouuwu
Level 2

I'm having trouble with my Quest 2 Air Link connecting to my laptop. I've used Air Link for a while now and it was working fine on the 19th (9/19/2022) before I ran into the issue of it suddenly being stuck on a loading screen whenever I try to connect.

 

Sometimes It says that the headset is ready and I can even get a notif from Discord saying a new audio device was detected, all green circles too. Then when I wait for the Air Link to go through it just keeps loading.

 

Specs: (I dont know what not to put and what to put, sorry)

CPU: AMD Ryzen 5 4600 with Raedon Graphics

GPU: NVIDIA GeForce GTX 1650

GPU: AMD Radeon(TM) Graphics

 

My laptop has been working just fine since most likely mid-summer up until the 19th and i've tried the following fixes. 

-turned on beta server

-turned off beta serv, restarted app, turned back on beta serv, restart app again

-restart pc as a whole

-restart quest

-change wifi on both

-change wifi on both to different ones

-change wifi to different ones and then back

-plugging it into my laptop to use link cable

-rollback and redownload drivers

-update windows

-set all graphics to prioritize my High Performance graphics rather than to let windows decide.


UPDATE:

Same problem still occurring after changing my graphics card from NVIDIA to AMD that is supported and disabled any type of VPN I may have. 

3 REPLIES 3

OculusSupport
Community Manager
Community Manager

Hi @minouuwu! We sincerely appreciate all the troubleshooting you've done so far to get Air Link working again. We want to jump in and help how we can. To do this, please gather logs following THESE instructions and attach the resulting file to a support ticket HERE. We'll be happy to look into this further. Thanks!

Whenever I attempt to gather logs I can only get to 86% before being prompted with Windows Error Reporting and the small window stating what it is gathering disappears shortly after. Should I simply let the program run in the background until it's done or is there a problem with the program obtaining the logs?

Try to let it run in the background and see if you're able to get the file we need. Let us know if it doesn't work, and send in a support ticket anyway so our teams can start looking into this with you.