My Quest pro has just had an update and now I'm getting a strange wobbling effect when using PCVR via the link cable and Meta Link. This doesn't occur with virtual desktop and wasn't happening before the quest headset updated
Hello Hitmanhepp :
I'm sorry to hear that you have been seeing wobbling effects during cable link sessions. Does this also occur when you use airlink? To help us with troubleshooting this issue, please provide a detailed description of the issue you're experiencing.
Steps To Reproduce:
Be as specific as possible. The more detailed your steps, the easier it is for us to replicate the issue.
[Example Step] Select the Link button in the Settings.
[Additional Steps]
Observed Results:
Describe what you saw or what went wrong.
Expected Results:
Explain what you expected to happen instead.
Test Environment:
Include relevant information such as:
GPU used
PC specifications
Connection type (Wi-Fi or Ethernet)
Headset in use
Headset version (can be found using this link)
PC Link App version (found in desktop app, under Settings > General > Bottom of page)
Additionally, please provide any relevant pictures and logs using our Horizon app, and log-gatherer tool under the diagnostics folders.
For more information on checking your software version, visit this link, and for collecting logs from your PC, refer to this guide.
Thank you for taking the time to help us improve Link. Your feedback is invaluable, and we look forward to hearing from you!
Yes it still happens when using airlink.
When I move my head in PCVR there's an occasional stutter with a wobble or artefacting in part of the view.
I'm using an RTX 5090
AMD9800x3D
64GB ram
My headset is V2.1
Link App 85.0.0.239.552. I've also used to PTC version on the link app and the effect is still there.
The problem started when my headset updated this morning
Thanks for following up with the info Hitmanhepp . If I understand correctly, so you started with v85.0.0.239.552 and the problem didn't occur with that version, correct? It's when your headset updated this morning and I presume it updated to v2.1, and that's when you started seeing this problem?
Yes, this is correct. I can reduce the frequency of the wobbles/artefacts by turning off eye tracking and natural facial expressions
I have similar issue, using cable link (with official cable). Airlink seems to work fine. Tested on two different laptops (4090 and 5090), here the issue happens every time link is established. on 3 different stationary PC's it doesn't happen. All using same windows version / updates, latest Nvidia drivers. Latest version of Meta Horizon PC app and latest update inside VR headset. All intel CPU's (i9 13th and 14th gen, intel core ultra 9). All PC's and laptops have 64GB RAM. Started on 4th March, after updating. Before this everything worked perfect! Hope this helps in debugging. Tested with 3 different Meta Quest 3's and one Quest Pro
Both my QPro and Q3 headset got the non-PTC v201 update earlier today. My meta-link PC app got a non-PTC v85 update a couple of days ago. I don't see any significant ui changes, nor do I see the navigator feature. At least both headsets now startup properly. Prior to this update I needed to press my power button twice in order for it to startup the Quest home. Otherwise, all seems to be working fine with my QPro using Link and Q3 using Air Link.
I did notice that if I use Link (official link cable, 9800x3d/rtx5090) with Fixed Bitrates there seems to be an upper limit of ~650-700mbps (still looks very good, to me anyway).
I normally use dynamic bitrates and in this case there isn't any limitation, and worked fine with up to 960mbps, but it does start to add latency much above ~800mbps. TBH I can't see any significant differences above 700-750mbps, and this doesn't add any appreciable latency. So, I'm sticking with dynamic bitrates enabled and 750mbps Max. I checked all this out using the ODT hud/performance/link details btw.
If you haven't tried dynamic bitrates for a while, I suggest you try them out. With ODT link settings I enable dynamic bitrate and use 750mbps Max dynamic bitrate. The beauty of this is that I can use the same ODT for both Link and Air Link.
With Link I'm seeing a pretty constant 730-750mbps and with Air Link I'm seeing a pretty constant 200-230mbps. Obviously, there is some graphical noise, but these usually settle down after 5-10 seconds. The main thing is that overall, I'm getting very good, stutter-free performance. I currently set meta-link graphics to 80Hz refresh rate with res slider full right. Depending on the app, I often add 1.2-1.4x pixel density and also mod ASW modes (eg. Forced 45fps, actually = 1/2 your refresh rate, asw off with msfs2020/2024). I still use the good old Oculus Tray Tool game profiles to do this. Although, it's pretty easy to just edit ODT directly and most of these can be done on the fly.
Thanks, I have Encode bitrate at 600. Should I set that to 0 and set dynamic bit rate to 600 instead? What difference would this make?
Hitmanhepp Ya, give that a go for starters and see what you think. Give dynamics 2-5 minutes to stabilize before drawing any conclusions. Then try 750mbps max dynamic as shown in my previous post ODT. Depending on you pc specs you may find 650-750mbps max dynamic works best.
With Link it’s best to disconnect any unnecessary usb and Bluetooth devices to avoid interference and/or running out of usb bandwidth.
Also, if you are using the fairly new experimental feature, System Positional TimeWarp (PTW), try turning this off (of course try it both ways). Many users (mainly VD users?) have found that this can cause stuttering in PCVR. I currently leave it disabled.
Since v74 I’ve found that dynamic bitrates have provided smoother performance with both Link and Air Link.
I have same wobbles/artefacts. Don't bother looking for help. Meta has broken the fixed encoding rate. You can even enter 2000 or 10 and nothing will happen (for H264) - the quality will remain the same. For H264 will imact perfomance, but still no visual difference 5 or 500 MBps.
V2.1 introduces new bug with the floor. When boundary detection is disabled, the floor is detected at a distance of 2.3 meters.
007x007 I don't know about floor height with boundaries disable (think you still need developer mode for this?), but most everything else seems to be working fine, except for the Fixed bitrate limit. See my previous post for details and my ODT settings. Maybe try these and see how you go. Cheers.
I disable this feature using Quest Games Optimizer because I sometimes saw borderlines when playing Beat Saber, even when the game was much larger than my room.
Thanks. Will try dynamic bitrates.
BTW. PTW option in headset have no impact to Oculus Debug Tool "Async-SpaceWarp Mode". It always show "Enabled" (in headset menu). Can you check if this works for you? (enabled/disabled)?
EDIT: Dynamic rate do not help. I still have wobbling. I tried recording it, but it's not visible on the video. Only in the headset.
I have the same issue on my Quest Pro. I started noticing it right after the latest update (the one with the new UI).
The only good thing is that this glitch only appears within the headset's own interface and Meta's native software; everything works fine when connected via Steam Link. However, using Remote Display is a nightmare—the image literally tears apart.
Are there any solutions that don't involve radical measures?
MetaMetalMonke
Hi, i have the exact same issue. Happend after updating to 2.1. ,( from 85)
no difference between airlink and link. Tried the usual. Factory reset, new install of link app, tried 3 different cables, ports. Even bought a new headset. Same issue there . (4090 Rtx, new highend gaming pc)
reinstalled an older NVIDIA driver; no effect
I‘ll try the dynamic Bitrate tomorrow.
Still having this problem, it's worse when eye tracking is enabled
