(Not Resolved) Known Issue - Quest PCVR streaming micro lags and stutter esp. when moving head

I get the same issue, thought it was my apple time capsule router, so "upgraded" to the tp link axe75 because its got wifi 6e, so figured that would fix it, since there are no other wifi 6e networks within range. (tower block living so 5ghz band is absolutely saturated). Now to my surprise, 5ghz is almost unusable in the evening on the tplink, where as my apple router is king. Anyway back to the problem, I get this frame lag which happens 2 to 3 times per minute, on quest 3 and quest pro, but it is less noticeable on quest pro which I don't know how. But that is why I got the TP link. I was going to replace the apple router, but now using both and the TP link is only for the airlink. well it still performs the same. sometimes when I increase the bitrate to 200mbs, it becomes very laggy. other times it doesn't. tried reinstalling software to no success. this is annoying as hell, because have you tried cutting up traffic at 200+ mph on no hesi when random frame pauses happen? come on fix this meta.

Hey guys. I know it's been a little while now so I wanted to jump in and reach out again to let you all know I'm still trying to push for information. To be completely transparent, the most I've been able to get the whole time was/is that they're still working on/looking into this but that there are 'no updates'.

Any and all bits of information you have provided have been appreciated and are being relayed to our internal team so they're up to date on everything in here. 

I'm still going to continue trying to poke at them for information so hopefully I'll have something to provide soon.

This forum is great, it just deleted my post randomly 🙂 

To write the whole thing again:

Q3, ASUS GT-BE98, PC <-> WIFi Router Fiber/Copper 10G/2.5G.

Throughput iPerf3 to my Pixel 6 300Mbit/s+ 0% loss via UDP:

[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 5] 0.00-1.00 sec 42.4 MBytes 356 Mbits/sec 0.020 ms 0/30709 (0%)
[ 5] 1.00-2.00 sec 45.7 MBytes 383 Mbits/sec 0.011 ms 98/33200 (0.3%)
[ 5] 2.00-3.00 sec 41.7 MBytes 350 Mbits/sec 0.016 ms 0/30230 (0%)
[ 5] 3.00-4.00 sec 43.2 MBytes 362 Mbits/sec 0.040 ms 0/31255 (0%)
[ 5] 4.00-5.00 sec 41.5 MBytes 348 Mbits/sec 0.013 ms 0/30042 (0%)
[ 5] 5.00-6.00 sec 41.5 MBytes 348 Mbits/sec 0.021 ms 0/30037 (0%)
[ 5] 6.00-7.00 sec 43.8 MBytes 367 Mbits/sec 0.021 ms 0/31712 (0%)
[ 5] 7.00-8.00 sec 43.1 MBytes 362 Mbits/sec 0.014 ms 0/31220 (0%)
[ 5] 8.00-9.00 sec 43.7 MBytes 367 Mbits/sec 0.021 ms 0/31645 (0%)
[ 5] 9.00-10.00 sec 44.4 MBytes 372 Mbits/sec 0.042 ms 3/32149 (0.0093%)
[ 5] 10.00-11.00 sec 42.6 MBytes 357 Mbits/sec 0.031 ms 0/30837 (0%)
[ 5] 11.00-12.00 sec 40.6 MBytes 340 Mbits/sec 0.016 ms 0/29378 (0%)
[ 5] 12.00-13.00 sec 44.8 MBytes 376 Mbits/sec 0.222 ms 0/32471 (0%)
[ 5] 13.00-14.00 sec 39.9 MBytes 335 Mbits/sec 0.067 ms 0/28898 (0%)
[ 5] 14.00-15.00 sec 37.5 MBytes 314 Mbits/sec 0.082 ms 0/27161 (0%)
[ 5] 15.00-16.00 sec 38.6 MBytes 325 Mbits/sec 0.021 ms 0/27972 (0%)
[ 5] 16.00-17.00 sec 43.5 MBytes 365 Mbits/sec 0.024 ms 9/31508 (0.029%)
[ 5] 17.00-18.00 sec 44.2 MBytes 371 Mbits/sec 0.016 ms 0/32028 (0%)
[ 5] 18.00-19.00 sec 43.5 MBytes 365 Mbits/sec 0.017 ms 0/31528 (0%)
[ 5] 19.00-20.00 sec 46.6 MBytes 391 Mbits/sec 0.030 ms 0/33727 (0%)
[ 5] 20.00-21.00 sec 45.0 MBytes 378 Mbits/sec 0.016 ms 0/32603 (0%)
[ 5] 21.00-22.00 sec 43.7 MBytes 366 Mbits/sec 0.011 ms 0/31618 (0%)
[ 5] 22.00-23.00 sec 44.5 MBytes 373 Mbits/sec 0.022 ms 0/32221 (0%)
[ 5] 23.00-24.00 sec 43.3 MBytes 364 Mbits/sec 0.019 ms 0/31381 (0%)
[ 5] 24.00-25.00 sec 41.5 MBytes 349 Mbits/sec 0.027 ms 0/30088 (0%)
[ 5] 25.00-26.00 sec 45.0 MBytes 377 Mbits/sec 0.017 ms 0/32574 (0%)
[ 5] 26.00-27.00 sec 45.4 MBytes 381 Mbits/sec 0.019 ms 0/32874 (0%)
[ 5] 27.00-28.00 sec 43.1 MBytes 361 Mbits/sec 0.017 ms 0/31202 (0%)
[ 5] 28.00-29.00 sec 44.8 MBytes 376 Mbits/sec 0.022 ms 0/32420 (0%)
[ 5] 29.00-30.00 sec 44.5 MBytes 373 Mbits/sec 0.019 ms 0/32216 (0%)
[ 5] 30.00-30.05 sec 2.30 MBytes 389 Mbits/sec 0.017 ms 0/1667 (0%)

Quest 3 was tested on Dedicated 6GHz and 5GHz networks, is running v67 and is constantly getting worse. I tried a myriad of options and configurations.

I can confirm using VD and fpsVR that the problem is on the networking side and between my Smartphone and my PC I can exclude anything on that route. Therefore I conclude, that the Meta Quest 3 has massive Issues on both 5Ghz and 6Ghz Networks, dedicated or not. I have very little interference where I live as well.

Without ADB sideloading (which I'd prefer to avoid for now) I cannot verify my "real" bandwidth between my PC and the headset, only the useless theoretical number that the WiFi connection shows (2400 Mbit/s is just not realistic).

I have been able to somewhat confirm a direct connection between head movement and Speed Drops in the wifi performance.

What I did was Hosting an Openspeedtest instance on my Homelab and running a continous Stress Test from my Meta Quest 3.

ASUS GT-BE98, 5GHz Network Dedicated

The results were as follows:

• No Movement: Stable 900Mbit/s+
• Hand movement: Minimal variance in Connection stability
• Head movement (like in Beat Saber): Drops down below 100Mbit/s in the most extreme cases. Since this is TCP, I suppose for UDP this scenario would mean many many dropped frames. The Speed decrease is in fact so extreme, you can see it very clearly in the connection graph.

I am on the same boat here ... my Q pro works perfectly fine and my Quest 3 has issues. Same network , same pc through Air Link with a Asus AXE7800 ... only difference the headset itself. Even bought the Q Pro controllers for my Q3 as well. So really only difference is the headset itself. Did anyone try changing the headstrap? I am on a bobovr s3 pro. Its not like by any chance the wifi antenna is in the side where we click on the headstraps??? And this might give problems? I contacted meta support but did not get very far ... they wanted me to upload a log but the chat only allows 5mb and the log was nearly 100Mb ... uploaded it to wetransfer but they can't use that or something like that .. I have to wait for an email now. Getting really tired of this issue. Hoping with every update (now on V67) that it should be fixed but so far nothing.

Hi lads I recently got the quest 3 and my brother has the quest 2, I can't connect properly connect on quest link (lagging and low res, but when I use the quest link cable it's fine) I just recently tried to play the forest on steam vr and it was horrible. It was all pixelated and lagging even in steam vr, I'm very close to my wifi but I don't have Ethernet, although I am pritty much underneath my wifi(I live on the 2 story and the wifi is below me) it still saids average range any recommendations for wireless vr, I was thinking on running a Ethernet to my room as I have experience in electrical

Guys, this problem has been there from the beginning and Meta is unable to do anything about it. Someone suggested it might be a design (hardware) error. In this case, the chances of fix are 0%

https://communityforums.atmeta.com/t5/Get-Help/Known-Isssue-Unstable-wifi-coverage-with-Quest-3-on-some-Router/td-p/1090698

with this set up using VD, on game like contractor showdown, i still get 15 ms of networking, lagging fps drop.. no one near me is using 6ghz and still i put the best channe to be really fu***** isolate and still laggin and fps drop.. i dont know what else i can do.. im running the game 90hz 1.0x on medium in vd and all low in game.. anyone got any idea?

It's shocking to me no one has mentioned this issue is on stand-alone as well. I have tested this bug considerably and it occurs in stand-alone even in the standard menu on both passthrough and non-pass through. It it much more subtle and difficult to notice than it is on Link but it is there. I have done everything including factory resetting my headset and turning off WiFi completely to the headset and the slight jitter every 3-5 seconds remains. I am guessing it is either one of two things, a hardware problem with the video processing, or a bug introduced from an update. If it's a hardware issue I don't think Meta will admit it because that's going to be a considerable problem.

After 1 week of troubleshooting and running arround in circles I found this thread, so I guess i can give up now and buy a longer cable, right? 😞 played a total of 5 minutes but spent 5hrs in menus, heck of a first time PCVR experience, what can I say? For context, in Alyx, with high fdelity setting, 90fps target:

• In Virtual Desktop, on 2400mbps connection through GL.iNet Beryl AX router I get 35-60fps and stuttering like crazy while moving (can't throw objects, they just fall from hand)
• On usb3 cable I get stable 90fps, no stuttering and can throw objects just fine.

I also get heavy stutters while watching a movie ONLY when I move (pan) my head, rotating is not that bad. So is there anything that I could try? (I have an early EU quest3)