Skip to main content
New Participant
December 11, 2025
Question

Passthrough over link not available?

  • December 11, 2025
  • 10 replies
  • 1636 views

I have a verified developer account. I have a quest 3 with developer mode turned on and linked to a windows pc running the meta quest link app. No matter what I have tried there is no Beta settings option at all. So no way to enable the passthrough over link option? Has it been removed or what am I missing to see the Beta settings?

10 replies

New Participant
December 16, 2025

I'm currently in the same situation and can't use Unity's pass-through function.
Have you solved it yet? I'm also looking for a solution.

 

New Participant
December 16, 2025

I am in crunch for a project right now, and this feature randomly being disabled has come at the worst time. I need it back, and now. This is exactly why developing for Meta platforms has always been terrible. It's as stable of a platform as a bowl of dog water. 

Participant
December 17, 2025

Same issue!
Link passthrough is a time saver for quest development. Please re-enable it!

New Participant
December 24, 2025

I had the same problem. Meta's (AI) support was useless.

By analyzing the Link logs with the official debug tool, I found the following registry keys. Below is the .reg file you can run:

Debug Tool: C:\Program Files\Oculus\Support\oculus-diagnostics\OculusDebugTool.exe

Menu: Service -> Logs -> pick a log file

Registry File:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Oculus VR, LLC\Oculus]
"VRPreviewLaunchLink"=dword:00000001
"ExperimentalExtensions"=dword:00000001
"PassthroughOverLink"=dword:00000001
"SpatialDataOverLink"=dword:00000001

 

New Participant
December 27, 2025

andrea.511384​ , thank you very much! That did the trick for me too 🙏

I do think that Meta should fix this issue directly in the Link App. Maybe file a bugreport somewhere? (I didn't search for the option yet)

Up and Coming
December 27, 2025

There's been 100's of bug reports, but support says its not an issue since it still works for some users on wireless, so they're not seeing this as an issue for now. Been dealing with them now for 3 weeks and the consensus from all responses is that if u want to see this added back as a feature to keep submitting feedback for march's update else they don't see the issue being an issue since the headset can "still" perform.

 

Source: Meta support/engineers directly

steve40
Honored Contributor
January 10, 2026

This was posted in another thread today, regarding the missing Beta tab saga: