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

[acreed11]

Hi team,

I'm getting micro lags and stutter in Airlink on my Quest 3 (EU/UK), esp. when moving my head. In the Oculus debug overlay this causes brief spikes in transmit/decode, fps drops and visible stuttering. The issue is not present on my Quest Pro with otherwise identical settings - see below screenshots to illustrate.

Few more details:
- Issue is not present on Quest Pro with same settings on HMD, router and PC (using same res)
- Issue is worse at higher bitrates, esp. >200mbps, but still present <200mbps
- Issue is unrelated to PC/game latencies (CPU, GPU, Queue each <5ms)
- Stutters/lags are intermittent (every 10-20 seconds) when not moving but happen immediately and reproducibly when moving the head to either side or especially looking downwards (i.e. on any bigger headset movements)
- Wifi 6E router (TP Link AXE75 EU/UK)
- EDIT: exact same issue with Asus RT-AXE7800 (EU/UK) wifi 6e router
- Connection shows as 2,400mbps
- Airlink codec H264 (but same on other codecs)
- I've attempted factory resetting, installing latest drivers
- Updated to v62 and latest Quest Link desktop version (I can see the 120hz option for my Q3)
- EDIT: Ordered a separate Quest 3 for testing: presents the exact same issue

-EDIT: Same issue on 5ghz 802.11ax 160mhz BUT switching to 802.11ac (!) completely fixed the issue. I cant test this on 6ghz but looks like 802.11ax or something related to how q3 implements it is the culprit

As the issue is worse the higher the bitrate and not present on Q Pro with otherwise same settings, I suspect it's related to the below known Wifi issues - but opening a new thread as instructed. 
https://communityforums.atmeta.com/t5/Get-Help/Known-Isssue-Unstable-wifi-coverage-with-Quest-3-on-s...

Best,
JensQ3QPro

Updates:
- Tried separate router: exact same issue with Asus RT-AXE7800 wifi 6e router
- Ordered a separate Quest 3: exact same issue on both routers

-Same issue on 5ghz 802.11ax 160mhz BUT switching to 802.11ac (!) completely fixed the issue. I cant test this on 6ghz but looks like 802.11ax or something related to how q3 implements it is the culprit

[Babinok]

You are wrong - I have already written about this.

[RockG.o.d]

I will have to turn the headset on again and see if it happens in mine. I know the jitter happens in airlink on both quest pro and quest 3. Never noticed it in the menus or in the very few quest games I have played. Might be an idea to play a high fps video test on the screens. I know the quest pro had a problem with the screens in the quest menu which did get resolved in the latest update, but I also remember playing airlink without issues until I think v59 or might have been later. Really can’t remember. 

[alex_rasa]

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) 

[Panromir]

You could try the Openspeedtest tool I mentioned about 3 pages ago. What most people here experience is not some kind of crazy stutter and downright unsuable streaming, but constant little reprojections and hiccups, which are extremely annoying.

What you describe, seems like generally bad networking somewhere between your PC and your Headset, which you should be able to see in Openspeedtest most likely.

[Phenicia10]

I have the same problem... but I don't use airlink... I'm tired.. I have the feeling, It's 700$ for nothing..

[Phenicia10]

I have the same problem here.... (lol..)

[Thywolf]

Okay I was having this issue, and found the solution to it on my end it seems. Swapping off my ethernet cable to sharing the dedicated access point with the quest 3 fixed this for me

[Babinok]

Can you give more details?

[Charging_Robot]

I need help with something, for some reason my Quest 3 while using the link cable will freeze for a moment before unfreezing but everything feels weird and it is motion sickness inducing, the screen is all shakey but I ain't moving my head and it like the motion sensor becomes super sensitive. It goes away after putting my head out of guardian or double tapping the headset (passthrough mode) and also control+shift+windows+B which is the driver reset but it ruins the VR experience. I've had it for a long time, but after I upgraded my GPU, I hoped that would help. I was wrong, and I see this is an issue with many AMD cards, I have an Nvidia 4060 ti and an I7-10700k. (the card I had previously was a 1660TI) it happens randomly when playing. before anyone says to upgrade the CPU that's the plan but I don't have a job. Being an HS student is a struggle fr  😔, but If anyone knows a fix for this, it would be greatly appreciated. in AutoAnalysis it's showing as an OAFError. forgot to write it in and don't know where to write it in now but I used to have a quest 2, it also had the same issue with link. 

[Kaltern]

I've had this issue since day 1. I have tried pretty much everything you can imagine, and the issue remains. I have a list of symptoms and possible causes but I believe all this proves the issue lies with the hardware. If I had the option I'd refund this as a defective product as it doesn't do what it advertises. It seems this is more prevalent outside of the US - is this correct? 

A wired connection works as well as can be expected. My PC's are unlikely to be at fault. I'm using a 6E capable wifi router with a 2400mbps connection to the Q3, and I have the same problem on 2 different PC's (one with a different 1200mbps router - which should still be sufficient).

It sounds very much like to me, Meta know what the problem is, and they won't admit it due to liability.