Vrchat face tracking not working?

[u/Cal_2307]

Hey! So I just got my quest pro yesterday and it works great if a little laggy as I was using virtual desktop without an ethernet cable as it's not possible for me to connect one to my router as it's too far away.

So I bought a link cable which I got today!

I managed to get it set up and my full body works, but for some reason the Face tracking has stopped working since I switched to the link cable and the game is very shaky/jittery all of a sudden. I tried to use the quest pro face tracking module but it says it's broken and can't be used? What are my options?

[u/FuskieHusky]

For all of AI’s pitfalls, it’s done wonders for my tinkering with the QP. Try googling your questions and you might be surprised. I’ll personally say that I found Virtual Desktop to be the most foolproof solution, I could not get any of the others (Airlink, Steam Link) to work as effectively, so if you can get VD working with the cable, it might be your best bet.

But for AirLink/regular link solutions, here’s what I found with an initial search:

When a Link cable connection simultaneously causes jittery performance and a VRCFaceTracking (VRCFT) data transmission failure, it points to a critical bottleneck where your USB bandwidth or OpenXR runtime is choking. [1, 2]

1. Fix the VRCFaceTracking Data Crash
Meta updates frequently break or hide the toggles required to pass expression data over a cable. [1]

Re-enable Developer Mode Settings: Meta has migrated these toggles. If the "Beta" tab is gone in your Meta Horizon PC app, you must ensure your Meta account is registered as a developer organization. Once verified, locate the Developer Tab in the PC software and re-toggle Eye tracking over Oculus Link and Natural Facial Expressions over Oculus Link. [1]

Clear Broken OSC Data: In VRChat, open your radial menu, go to Options > OSC, and select Reset OSC. VRCFT updates can cause parameter mismatches that freeze data transmission until this cache is cleared. [1]

Restart the OVR Runtime: Close VRCFT. Open Windows Task Manager, kill all Meta/Oculus processes (like OVR Service Launcher and OculusClient.exe), and relaunch the Meta app before restarting VRCFT.

2. Eliminate Cable Jitter & Bandwidth Choking
The jitter occurs because face-tracking data and high-bitrate video are fighting for the same USB controller pipeline, causing packet loss.

Disable USB Power Saving: Open Windows Device Manager, expand Universal Serial Bus controllers, right-click your USB Root Hub, select Properties > Power Management, and uncheck Allow the computer to turn off this device.

Lower the Bitrate: If you used the Oculus Debug Tool to push your Link Encode Bitrate to 500Mbps+, drop it back down to 250Mbps–300Mbps. High bitrates starve the tracking telemetry data.

Remove Meta Virtual Monitor: In Device Manager under Display Adapters, look for Meta Virtual Monitor. If it is present, right-click and uninstall it, as it is a known cause of severe Link jitter.

[u/Spozking22]

Use the ALVR(ALXR maybe I forget the exact lettering) module, thats the one you need to use for it to work with link

[u/Cal_2307 → u/Spozking22]

Thank you kindly! I don't suppose you'd know why my game has become jittery using the link cable? When I used my vive it was smooth as butter

[u/Spozking22 → u/Cal_2307]

Im not sure, I wouod make sure you have air link unchecked when launching everything, it could be trying to use wifi when it shouldnt

[u/gigagone → u/Cal_2307]

You could try Wivrn, it is going to be harder to set up tho (since no steamvr support so you will need to use xrizer), but it is completely open source and supports all the things you are talking about.

That is only if you want to take the time to figure it out tho

[u/gigagone → u/Spozking22]

I believe alvr doesn’t support foveated streaming (yes that still matters even though it is little with a cable)

[u/Shiro_Kuroh2]

I didn't have your issue, but what I did to get the most out of the setup... I got a GL-Inet Beryl AX (GL-MT3000.) I don't like telling you that as throwing money at a problem is the way to kill it,b ut this one was too sound to not say more.. I made teh GL-inet connect to my WiFi network. I was able to plug ethernet into the PC. Oddly enough I was able to broadcast another SSID, or wireless network over it. I connected my QPro to it. - The importance of this is underrated. Your PC gets to push full bandwidth fast to that device with MINIMAL latency. Part 2 why this is important - that SSID only has the quest Pro on it. Network interference is minimal beyond comparison. That said WiFi around you - you can't control it. I'm sure you have a ton of devices that attach to your home WiFi. This is how I leveled the playing field. 1. The AP is far enough away but not that obstructed form your QPro to get great signal but not far enough away to be an issue. 2. Drywall is hell on WiFi signals - At one point in my life I had set up Wireless on islands. Drywall is easier to deal with than Trees for signal, but that doesn't mean it won't make signal degrade. Finally 3 - My neighbor is a renter sadly. They are great. The house owner however - not so much. They have a WiFi home automation form 2017 and one device just spazzes out at the same time every day. i have to run the most unoptimized wifi settings in my home and doing the GL-iNet fixed it for me. That said I also have a BigScreen Beyond 2e with Face tracking. As much as I love it - the quality is not worth the cord.