Link connection get freezed
ENG: Since the major OS update, the Link cable connection has been failing and randomly disconnecting for a moment, freezing the VR image and making it impossible to reconnect without fully restarting the PC. I mainly use the headset for sim racing (iRacing, LMU), and this happens quite frequently. My headset settings are not aggressive. After several attempts and configuration changes, it can sometimes last a few hours without issues, but then it suddenly freezes again. The game and the headset itself continue working — I can still see on the monitor that the headset movements are being tracked in-game — but I cannot see anything through the headset anymore. I do not currently use an official Link cable (although I have ordered the official €80 cable to test whether it solves the issue), but I never experienced problems like this before. Everything started after the major Meta OS update. Since then, I have also experienced zombie processes that would not close properly, causing the image to run at 2 FPS and leading to crashes. Now this. SPA: Desde la gran actualización donde se cambia el SO, el cable link falla y se desconecta por un momento, congelando la imagen de VR y haciendo imposible volver a conectar sin reiniciar el PC entero. Suelo jugar a Simracing con ellos (iRacing, LMU) y me pasa con bastante asiduidad. La configuración de las gafas no es agresiva. Después de varios intentos y cambios ha aguantado unas horas sin quejarse hasta que de repente se congela. El juego y las gafas siguen funcionando, incluso en la pantalla sigo viendo como las gafas están aun provocando movimientos en el juego, pero no puedo ver nada desde ellas. No tengo un cable Link oficial (he pedido el cable de 80 euros para ver si con esto se arregla) pero nunca había tenido problemas así, solo desde la gran actualización del SO de Meta. Desde entonces, procesos zombieficados que no se apagaban, provocando que la imagen fuera a 2 Fps y crasheos. Y ahora esto... PD: I tried a clean install of Nvidia Drivers + Turn off Meta Notifications. After some days testing, Meta Link crashed again and freezes. Doesnt work
Steam link not working
So I keep trying to air link my head set to my steam vr app on my computer with the steam link app on my headset but when I get them to connect I hit continue then goes to a screen that says I am in the wrong session as my computer. I have checked that all my drivers are updated and pretty much anything I could think of but it still doesn’t work. Can someone please help me find out why I can’t get them to connect?
Meta PC software can't reach Meta Quest Link services.
as you can see in my screenshot somethings not right. ive searched the internet but i found nothing, i use windows and this error came when i installed the software and it went through a scan to verify everythings alright. I also tried the "repair" button many times and uninstalled and reinstalled the program a couple of times but its still not working. (also restarted my pc many times and i also have a stable internet connection.) Does anyone know what i could try?The Meta Quest Link window for adding a new device cannot be resized to fit my display resolution
In the Meta Quest Link app on my PC (Windows 11), when trying to add a new device, the window that shows all the Meta headsets to choose from is much larger than the display size of my monitor (1980x1020), so the "previous" and "next" buttons cannot be accessed. This is a problem with the Meta Quest Link software not scaling its windows properly. The Meta Quest Link window cannot be resized (the little square in the top right corner for resizing the window is greyed out), and my PC monitor is already set at its maximum supported resolution. Lowering the display resolution only makes the problem worse. While I can scale my Windows display to make everything larger, it is not possible to downscale the windows below 100%, so I have no way to make the Meta Quest Link window fit on my screen. So basically, I am stuck and can't navigate forwards or backwards from this screen.
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
Oculus Quest 2 Horizon Link pairing stuck issue
Hello there, I`ve bought Oculus Quest 2 and wanted to pair it with Horizon Link I`ve downloaded mobile app then opened it and started pairing process, so I also have turned on my Oculus Quest 2 then typed 5-symbol code to app and it was paired successfully, I can see it in my devices but there is a problem - Mobile App said that I need to continue configuring my Oculus Quest 2 actualy on my device, but then I weared it on there was nothing changed, It steel shows link code and nothing happens. Then I also tried to reset it with recovery mode -> went to boot menu and selected factory reset, when it booted it steel shows this link code and steel nothing happens. Did someone had same issue, how did you solved it ?
