WIFI connection issues with Meta Quest 3
Hey guys, so i recently got a Meta Quest 3 for VR Gaming (MSFS2024) and i read quite a lot on how to properly set everything up to have a great experience. So eventuelly i decided to install Virtual desktop on the headset and the Streamer app on my PC. Furthermore, i bought a separate router (TP-Link Archer AXE75 AXE5400 Tri-Band Gigabit Wi-Fi 6E Router) and configured it as an access point. So the main router is in the living room, then an ethernet cable is going directly into my office, then i have the TP-Link router as access point (WAN is internet IN and LAN1 is out to PC) and then another ethernet cable to my PC). The access point sits on top of my PC case, so just 1m away from where i am sitting. I have the options of having 2.4GHz, 5GHz and 6GHz Wifi networks, but i only enabled 2.4 and 6GHz. Now i come to the issue: The problem i have is that if i power my headset on, it doesn't connect to the 6GHz Wifi since it states 'unable to connect'. I also have to keep the 2.4GHz enabled, otherwise the 6GHz would need even be recognized from the headset. In the WIFI list, the 6GHz WIFI is sometimes recognized, sometimes it vanishes and then i have to turn the WIFI on the headset OFF and then back ON. AFter some tries, if finally connects. Sometimes it loses connection again. Any idea on what i can do in order to improve the connecting issues? Many thanks for the support.
Air Link stuck in infinite loading loop – OculusDash.exe keeps crashing (COM initialization failure)
When trying to connect horizon link with airlink, loading is keep going over and over, never end. First of all , i stated to observe task manager. and i found the OCULUS-DASH.exe process was keep shutting down, whenever start link to horizon. Here is the Oculus Dash Log 2026-01-19T17:24:28.866133 [I]: C:\Program Files\Meta Horizon\Support\oculus-dash\dash\bin\OculusDash.exe startup: 2026-01-19T17:24:28.867130 [W]: Invalid prop name: oculus.signalFenceInDX 2026-01-19T17:24:28.868127 [W]: Invalid prop name: oculus.signalFenceInDXEarly 2026-01-19T17:24:28.868127 [W]: Invalid prop name: debug.saveLogToMiniDump 2026-01-19T17:24:28.868127 [I]: CLAYLOG - Entering App::run 2026-01-19T17:24:28.868127 [I]: LOGFILE: C:/Users/PC/AppData/LocalLow/Oculus/Dash/log/Dash.log 2026-01-19T17:24:28.893061 [I]: App::run isVRMode m_windowShouldClose 0 2026-01-19T17:24:28.893061 [I]: OculusUtil::_init() 2026-01-19T17:24:29.478517 [I]: OculusUtil::_initHMD() 2026-01-19T17:24:29.478517 [I]: HMD: Oculus Quest2 (FW -11901.0) 2026-01-19T17:24:29.479522 [I]: HMD: (2816x1472) 2026-01-19T17:24:29.479522 [I]: RT : L(4160x2096) R(4160x2096) 2026-01-19T17:24:29.479522 [I]: OculusUtil::newControllerFactory() 2026-01-19T17:24:29.479522 [I]: Medium: Branch [systemux] Build [0] 2026-01-19T17:24:29.480517 [W]: Unable to find loader for Texture resource at path 'textures/test/checkerboard'. File may not exist. 2026-01-19T17:24:29.592752 [I]: Audio will play through VR device '헤드폰(Oculus Virtual Audio Device)'. 2026-01-19T17:24:29.706830 [I]: OAF Initialized 2026-01-19T17:24:29.709811 [I]: Dash Ready 2026-01-19T17:24:29.710318 [I]: RenderDeviceSystem::_onAddedToScene() 2026-01-19T17:24:29.714985 [I]: NVAPI initialized: driver version 57602 2026-01-19T17:24:29.714985 [I]: RenderDevice::RenderDevice() 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_device_group_creation (1) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_external_fence_capabilities (1) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_external_memory_capabilities (1) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_external_semaphore_capabilities (1) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_get_physical_device_properties2 (2) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_get_surface_capabilities2 (1) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_surface (25) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_surface_protected_capabilities (1) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_KHR_win32_surface (6) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_EXT_debug_report (10) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_EXT_debug_utils (2) 2026-01-19T17:24:29.833803 [I]: Vulkan supported extension: VK_EXT_surface_maintenance1 (1) 2026-01-19T17:24:29.834813 [I]: Vulkan supported extension: VK_EXT_swapchain_colorspace (5) 2026-01-19T17:24:29.834813 [I]: Vulkan supported extension: VK_NV_external_memory_capabilities (1) 2026-01-19T17:24:29.834813 [I]: Vulkan supported extension: VK_KHR_portability_enumeration (1) 2026-01-19T17:24:29.834813 [I]: Vulkan supported extension: VK_LUNARG_direct_driver_loading (1) 2026-01-19T17:24:29.905648 [I]: INFO: ovr_GetSessionPhysicalDeviceVk inHmd = 00000234B29F8048 vulkanDevice = 00000234B3744220 vulkanDevice->m_instance = 00000234B390C080 2026-01-19T17:24:29.906188 [I]: INFO: ovr_GetSessionPhysicalDeviceVk vulkanDevice = 00000234B3744220 vulkanDevice->m_physicalDevice = 00000234B3FCFB40 2026-01-19T17:24:29.906188 [I]: INFO: API 0.64.65.47 2026-01-19T17:24:29.906188 [I]: INFO: DRV 144.0.128.0 2026-01-19T17:24:29.906188 [I]: INFO: VEN 0x10de 2026-01-19T17:24:29.906188 [I]: INFO: DEV 0x2216 "NVIDIA GeForce RTX 3080" 2026-01-19T17:24:29.982235 [I]: gpu vendor id is 10de 2026-01-19T17:24:29.994762 [W]: Unable to find loader for Texture resource at path 'textures/test/color_ramp'. File may not exist. 2026-01-19T17:24:29.996757 [W]: [GuardianDraw.glfx:269]: Program 'GuardianDrawFloor': can't find depth state 'depth' 2026-01-19T17:24:30.104946 [W]: Unable to find loader for Mesh resource at path 'models/tools_hand/ToolOrient_CursorLeft'. File may not exist. 2026-01-19T17:24:30.105917 [W]: Unable to find loader for Mesh resource at path 'models/tools_hand/ToolOrient_CursorRight'. File may not exist. 2026-01-19T17:24:30.105917 [W]: Unable to find loader for Mesh resource at path 'models/tools_hand/Tool_CursorLeft'. File may not exist. 2026-01-19T17:24:30.105917 [W]: Unable to find loader for Mesh resource at path 'models/tools_hand/Tool_CursorRight'. File may not exist. 2026-01-19T17:24:30.107484 [W]: Unable to find loader for Material resource at path 'materials/tools_ui/Crosshair'. File may not exist. 2026-01-19T17:24:30.107484 [W]: Unable to find loader for Material resource at path 'materials/tools_ui/Arrow'. File may not exist. 2026-01-19T17:24:30.108452 [W]: Unable to find loader for Texture resource at path 'textures/tools_ui/Hand_D'. File may not exist. 2026-01-19T17:24:30.108452 [W]: Unable to find loader for Texture resource at path 'textures/tools_ui/Hand_M'. File may not exist. 2026-01-19T17:24:30.248989 [I]: Didn't find existing sound '/UI/Key_Hover' using default '/UI/Button_Hover'. 2026-01-19T17:24:30.249984 [I]: Didn't find existing sound '/UI/Key_Click' using default '/UI/Button_Click'. 2026-01-19T17:24:30.257988 [S]: Could not initialize COM
Quest 3 - connects, but PC no longer sees it (v85)
SITUATION: When I connect my Q3 to laptop, (as I've done for years), it beeps, and charges, but doesn't pop-up in explorer (nor show the access files dialogue box). BACKGROUND: I have used windows explorer for years with no issue across multiple Quest headsets. I don't believe I have changed any settings. I have also looked through Quest device settings (and web), and can't find the way to force the access files pop-up. [possible solution?] PURPOSE: My intent is to download recorded content from my device and edit before publishing to YouTube, etc. HOW TO REPLICATE: Plug in Q3 to PC/laptop with trusted cable. NOTES: Currently on v85 Connecting to my PC brings up the charging indicator light as expected Connecting makes the affirmation beep Link still works (can see desktop, play VR games) SideQuest works The usual pop-up "allow connected device to access files" doesn't show I recently had a temporary warning that it detected water in the port. Yet that was random (no where near water), and went away within 30 minutes. Rebooting both devices doesn't change anything. I've spent a few hours trying to figure this out, and would love any ideas you have.
Unable to add payment method
Just bought a quest 3. My debit card is paired to my meta account. However, i am still unable to add my card as a Payment method on the meta horizon app, and get an error each time. I've tried multiple cards, nothing. No update needs to be performed. I have tried using a computer, phone and the actual headset. Even switching to cellular data. I have bought multiple things online lately, and the bank allows international purchases so I don't think it's on the cards end. I have restarted the device multiple times, tried on different days and nothing seems to work. There are a few cases online with the same problems, but they seem to have been fixed using instagram or facebook, which I tried, and they accepted my card, but it still will not add my card into the 'payment method' slot. Or they only use gift cards, which seems like a serious downgrade. Please help before I go and refund this VR before I ever got to play it.Quest Pro Controller Connection Issue (Quest 3)
Hello. I have owned Quest Pro controllers for several months now with my Quest 3 and have experienced minor issues having to do with connection and tracking. I have been able to solve those issues fairly easily. However, I am now experiencing an issue that I haven't found a solution for after much research. My quest pro controllers are fully charged and turn on just fine. I am able to connect them to my headset, but they don't turn on past that. The meta horizon app shows them as connected, but in my headset neither controllers are on and functional. I have restarted the controllers, headset, and even went as far as factory resetting the controllers, where I had to use my old quest 3 controllers in order to set up the headset (because the pros still have the issue). I have been looking online for people with similar issues and it seems like none of them can figure it out themselves which makes me regret buying these controllers in the first place. Does anyone know how to reach a solution to this issue?
No option to disconnect VR-headset via PC (Air Link)
Situation/Context: I am in a position where I work with multiple Meta Quest 3 VR-headsets (one at a time, but multiple lying around). Since I do not work alone these multiple Meta Quest 3's belong to a pool of VR-headsets, freely usable by anyone around. Problem: When having a Meta Quest 3 linked to a computer via the Meta Quest Link app (Air Link), a new connection with another Meta Quest 3 cannot be established — neither is it possible to have multiple VR-headsets connected at the same time, nor does a new connection (attempt) disconnect the current one. If a VR-headset is connected to some computer and not actively disconnected, it will try to connect to this very computer everytime both devices are turned on and connected to the same WiFi. If the paired VR-headset is now being used by someone else, who is not using the Air Link option, this very connection stays active. As a result the computer, which is still linked to the now-away-VR-headset, cannot be used with another VR-headset — neither via Air Link, nor via a cable connection. There simply is no option from the pc-side to cancel an active connection. Restarting the Meta Quest Link app (through the beta-version feature) will result in the connection being instantly established again. This also happens after restarting the entire computer — as soon as the Meta Quest Link app has started and the WiFi connection is active, the paired VR-headset is connected again. Further questions: Are there any methods to disconnect a vr-headset-pc-connection without access to the vr-headset? Any other tipps to avoid the above described situation (other than 'just disconnect the VR-headset before you stop using it')? Possible solution: Adding a button inside the Meta Quest Link app to actively disconnect a VR-headset would solve this issue in an instant. I would think that there are a couple of people out there who are developing with the Meta hardware and would appreciate such a feature (as to no longer hunt for the currently connected VR-headset and politely ask the current user to disonnect the Air Link connection..). Thanks
