Meta Horizon Link app does not show beta tab in settings

https://communityforums.atmeta.com/discussions/link-v83-troubleshooting/v83-link-workaround-fix-for-quest-proft/1359379

Sadly no, even with the backup u won't be able to use link with steam or pcvr related stuff if u want to use FT the client flat out deny's steam from loading over during this. It's 100% gone till they add it back, and from the looks Meta's out for the holidays cuz we're gonna be on 2 weeks soon with 0 response from support.

Wireless 3rd party apps are the only way but just feel clunky after being so used to link, the extra overheard is nuts.

Same been going back and forth for a bit however it gets weird.

It went from "This is a known wide spread issue which a fix is being worked on"

to "This is working as intended just use wireless as u shouldn't be using wired as wireless is more stable" 

then its "You're the first to report this but we can forward it on if you want, but sounds like u want to leave feedback for future updates instead"

The team isn't aware as theres no direct communication, and others validating the developers/engineers aren't aware of anything, while some state they are.

Simply put its a simple face of the FT runtimes for facetracking not being exposed (Under the extension name section column(center)) for the following:

• XR_FB_face_tracking
• XR_FB_face_tracking2
• XR_FB_eye_tracking_social

You can easily see this by running OpenXR Explorer with Link active and u'll see that it no longer advertises them. (See attached photo for ref) It will show 

• SupportsEyetracking:False
• SupportsFacetracking:False

etc

The issue lies with the desktop app not the headset, and restores do prompt to bring it back temp (for a few minutes) before it gets overwritten by meta since its constatnly checking online and disables them again.

There's no report option for PC desktop software (for the meta app) and they don't really read the forums per their rep's as its meant for "consumers to communicate with eachother and have the freedom too"

Mind you its been 3 weeks now, and no update, just one of the following

• Its known and a fix is in the works
• Not an issue working as intended just try wireless instead enjoy
• Submit feedback if you're unhappy with it

This is not a fix for link sadly, and given OpenVR space calibrator doesn't see the quest when connected to steam link, using it with basestations/trackers is a no go atm.

Your mention is for wireless though, which works on any software with the device, steamlink included, You don't even have to change the OSC output port. Problem with steamlink is that it registers the qpro differently so u can't use it with openspace calibrator like u can with VD or ALVR which I find odd.

This thread is about LINK (cable) not wireless issues, Meta already made their stance that they're not going to look into this sadly, as since it works for "some" users (they mean wirelessly) that its not an issue and people should file feedback if they'd like to see it returned sometime next year when they roll out their March update.

It's a simple fix from their side, we've validated the rootcause but for w/e reason they feel its not a big enough issue to consider a bug.

I left instructions on how to make a text file, u can also just paste it in notepad, then click save as -> when saving change the dropdown from .txt to all files and rename it whateveryou want and add .reg at the end vs .txt that performs the same.

Per support they have no rush or push to change this (per their words) as it still works for "some" people, and only hint at leaving feedback if u feel its an issue.

Thanks for the update Pindle!

You have the Developer tab and you need to enable developer runtime features.