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?
This was posted in another thread today, regarding the missing Beta tab saga:
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
I apologize, but could you please explain to me how to run this? I'm comfortable with computers but I've never had to mess with this stuff for my quest pro. This update has broken the ability to use face tracking in VR. I was able to find the files and all but I'm unsure of how to actually "run" this. Any help is greatly appreciated <3 sincerely, someone who just bought this headset for it to be updated into the shadow realm.
This isn't a fix for quest pros / face tracking over link, this is more for Q3's and other features that people use. The runtimes simply are not exposing them per debug logs.
However to answer your question, you can simple copy / paste her script (as its in a code snippet to ensure u copy what's needed) into a text file, save it as a .reg file extension. If you don't see it, then save it as a text and in explorer you can right click and rename to .reg, after that just double click to run ( it will apply the values)
if you don't see the extension of the file then make sure in explorer u click
VIEW -> SHOW -> File name extensions if on Windows 11
Windows 10 will be folder properties -> scroll down to show file extensions.
Likewise I've been using htis headset since last year but this is the first time I've seen them force break it as a "feature" vs bug. Per support they have 0 plans to treat this as a bug and will consider it for the March update, they've been aware of the issue since Dec 6th however PER support: "Since it works for some users(over wireless in this case) they don't see this as a critical or big issue and would rather not risk breaking it for the few it does work for therefore if you'd like to see the feature added, please submit feedback, as bug reports do not get attention since they come from the headset and not the desktop app.
They follow this up with Happy holidays and glad your day is going well.
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)
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
Same issue!
Link passthrough is a time saver for quest development. Please re-enable it!
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.
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.
