Bizarrely specific Quest 3 PC Link problems from newest update.
I just updated to the newest Meta Quest Link software. Now on online multiplayer games, specifically Onward (on Quest Link) and Forefront (on SteamVR) have an issue where the right eye display is completely thrown/scaled/sized/warped incorrectly, its actually pretty nauseating. Weirdly it didn't do this with Into the Radius (on Quest Link) or CONVRGENCE (on SteamVR). When I switched the OpenXR runtime to SteamVR instead of Quest Link, the issue stopped on Forefront. I tried disabling asynchronous spacewarp and sliced encoding and that didn't fix the problem. Onward still displays fine on stand-alone. I tried running the repair function on the Quest Link setup exe but that did not fix the issue. Additionally, I ran Forefront on my PSVR2 with the PC adapter and it displayed fine.
Idk if it's important, but for reference, I have a Radeon GPU (RX 7800 XT), which to my knowledge sometimes struggles with VR related software support. Although, because the direct-to-DP PSVR2 worked fine, I don't think it's a problem with my GPU.
It seems very likely that its an issue with the Meta Quest Link OpenXR runtime.
I have no idea how to fix this.
Onward is my favorite game and I much prefer it on PC, and I don't wanna have to buy it again on SteamVR just to play the game I already bought.
Update:
I did some more testing, and when playing Forefront with my Quest the microphone no longer works.
The first thing I did was try to uninstall + reinstall Onward, and it wont let me redownload it. It will download everything then just say "failed to install, contact Meta for help." I tried removing all the files manually a reinstalling, got the same response. I tried uninstalling and reinstalling Into the Radius and it worked just fine.
It's a specific issue with AMD GPU's and Unity games. The solution from some Reddit posts appears to be to downgrade the AMD graphics driver. Disabling sliced encoding and switching OpenXR runtimes seems to fix some games, but some problems persist. The issue has been noted on the Meta developer Feedback Center and a fix is in progress.