Issues with Oculus Software Update 1.97.0 and Meta Quest 3 WiFi 6 Mode
After updating to Oculus Software version 1.97.0, I have encountered issues with the mouse cursor on my Windows 11 PC. Specifically, the mouse cursor displays a continuously blinking blue circle, which is highly disruptive during computer use. Identified Cause This issue appears to be caused by the Oculus VR Runtime Service, which starts automatically with the system and remains active even after the Meta Quest Link application is closed. Temporary Solution To mitigate this problem, you can use one of the following methods: Using Services Manager: Press Win + R, type services.msc, and press Enter. Locate Oculus VR Runtime Service, double-click it, change the "Startup type" to Manual, and confirm with OK. Using Command Prompt: Open the Command Prompt as an administrator and type: cmd Copy code net stop OVRService While this stops the cursor blinking temporarily, the issue reoccurs when the Meta Quest Link application is launched again. WiFi 6 Mode Issues on Meta Quest 3 (Build 71.0) Another issue arises with the Meta Quest 3 when connected to a WiFi 6 network after updating to build 71.0. Upon activating Air Link, the headset nearly freezes, and the display is filled with artifacts. The system only stabilizes after disconnecting WiFi on the PC and disabling Air Link on the headset. Observations The issue does not occur when using a USB cable or connecting to a WiFi 5 network. In these scenarios, the system functions smoothly even at high resolutions (4128 x 2208), 120 FPS, and a bandwidth of 200 Mbps. My setup includes an ASUS RT-AXE7800 router with WiFi 6E, ensuring excellent signal quality. Speeds are as follows: WiFi 5: 1200 Mbps WiFi 6: 2402 Mbps Workaround To resolve this, I enabled the 160Hz frequency for 5GHz channels on my router. When the Meta Quest 3 connects to this network, it recognizes it as WiFi 6, achieves speeds of 2402 Mbps, and Air Link works as expected. Unfortunately, not everyone uses an ASUS router. Request for Assistance I am uncertain whether these issues are related to the Oculus Software version 1.97.0, Meta Quest 3 build 71.0, or a combination of both. Previously, everything worked flawlessly. Please investigate these issues and release a fix as soon as possible. Thank you.
Air Link searching for PCs
Hi, We are a VR studio with multiple released titles, Two weeks ago all of our headsets (a mix of Quest 2 and Quest Pro) stopped seeing our computers via Air Link, they spin in "Searching for PCs..." forever. Cable Link works normally. Since we have a fairly complicated network setup I contacted our network consultants to see if anything had changed on that side. Nothing had changed, but they still tried to reset our Wi-Fi Access Points, to no avail. The headsets are on the right subnet, with the right DNS server. We tried: * a factory reset of one headset * moving to and back from PTC * disabling the windows firewall of the target PC * connecting the PC to the Wi-Fi AP the headset is connected to Without success. Using MQDH we are able to connect to the devices via USB and then transition to ADB over Wi-Fi without any problem. Inspecting the logs in MQDH shows that a non factory-reset headset still thinks it's paired to a computer, but is unable to DNS resolve to it's host mdns: DNSServiceProcessResult failed with 0, failed to resolve the network address for boris::TREB-PC-016 We have a Windows Active Directory Domain, so we host our own DNS. It is accessible and can successfully resolve TREB-PC-016. It would be nice if headsets in Development Mode could Air Link to a specific IP. This is a big productivity hit for us because everyone is used to Air Link and we don't have enough Link Cables to plug all the headsets. Do you have any suggestions?
Oculus + Air Link causes computer crashes when the headset disconnects from WiFi.
As usual, it's hard to pinpoint exactly where the issue originates due to all the handoffs between apps. My Quest 2 is connected via Air Link through the Oculus App, to SteamVR, which is then running VR in Unreal's editor. If the connection is active and the headset is awake, I can successfully run in editor as many times as I want. If the connection is not active (only SteamVR is open, Oculus is closed and not set up), Unreal will successfully fall back to a spectator pawn. If the connection is active but the headset has disconnected, my computer will freak out and eventually crash whenever I interact with VR. So far, those crash events occur when I open Unreal (which presumably makes contact with the VR setup) and when I hit that Play in VR button in the editor (as when the headset's fallen asleep between uses). As soon as one of these actions is initiated, I hear cable whine from my PC--the only time I've found that it does this--and I have a very short time to catch it before the mouse freezes, the screen stops, and the computer needs to be restarted. If I'm able to get my headset on, dismiss the lost connection dialogue, and reconnect to my PC over Air Link, it has a decent chance at recovering. I think I've had this happen with Unreal closed, though the above is my primary observations so far. SteamVR has been opening and closing for ages and never caused this on my computer. I previously used VirtualDesktop for this and also never had issues there, though this was largely before my current PC was built so that's not a clear indicator. The computer itself is very new and, on paper, shouldn't be a problem. GPU - 3080 Ti CPU - 5950x RAM - 64gb
Uncertain Graphics Card Compatibility
Just upgraded from an old sluggish laptop with a Intel UHD Graphics 620 graphics card to a i7 Dell Laptop, purely with the intention to get a much better gaming experience in VR. But, only to discover that the Nvidia Quadro T2000 GPU, is not compatible with the air link. With it working on my last I assumed it would work with this. I've seen suggestions that Quadro T2000 isn't a high enough spec, but how is true if it can run on other lower spec GPU's and other Nvidia GPU similar to the T2000? Meta only state a hand full of compatible GPU's on their website, making it impossible to know what other GPU's are compatible. This is meant to be a user-friendly experience for almost everyone, I shouldn't be gambling on whether I can connect to airlink.
Feature Request: Boot in Oculus Link
Greetings, As the title implies it would be a neat feature to turn on within the Oculus app that would allow users to boot right away into Oculus Link as opposed to the standard OS. It would be a great quality of life improvement to offer users who are predominantly PCVR players a quicker way to play games.
