Participant

Solved

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

442 replies
293119 views

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-some-Router/td-p/1090698

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

TheAntiSocializerAnswer

Honored Contributor

Hey everyone! Thank you so much for the information you've all provided.

If you have not already done so already, I would suggest reaching out to the support team via email so that they can gather a copy of your logs.

If you have already reached out to support and provided your logs, please PM MetaStoreHelp with your case number.

EDIT 8/5: Hey everyone! Just wanted to reach out and thank you all for your continued patience. If you're still having some issues, the best thing I can recommend at the time would be to submit a bug report. That way it can go straight to our engineers for them to further review everything provided. Thanks again!

Sometimes it's okay to be a little Bing Chilling

Show previous replies

Z

zetto75

Participant

I tried everything. The only thing that works for me is to use Wi-Fi analyzer on Pc to find the best channel and change in router settings. It s not confortable and i hope they will find a upgrade to solve this issue.

V

VirtualOmnipresence

Up and Coming

I've also noticed something interesting lately. For me if I disable positional tracking under "settings / headset tracking", wifi becomes rock solid (as it was prior to OS version 57). Here is a video comparing packet loss with positional tracking enabled and with positional tracking disabled (please watch the video on desktop, the graph has a rather thin line):

For me this shows that this whole issue is just a low level software issue. As soon as the tracking task get's too busy (due to the movement), the wifi driver doesn't get enough CPU resources and delays and/or looses wifi network packets.

R

revanmj

Participant

Couldn't find any "positional tracking" on Headset Tracking settings panel, the only tracking I could disable there was hands and body tracking. And it didn't help at all, with it disabled there are still the same stutters when streaming PCVR via Wi-Fi 6 network.

Quest 3 PTC | AMD Ryzen 5700X, 32 GB RAM, GeForce 4070 Super, Windows 11 x64

V

VirtualOmnipresence

Up and Coming

revanmj this is what I mean:
https://www.meta.com/help/quest/articles/headsets-and-accessories/using-your-headset/turn-off-tracking/

Here is a screenshot from the internet showing the setting:

You need to disable the first toggle on the quest device at "settings / headset settings". It switches the device into 3 DoF mode. The headset then only tracks your head and controller rotation but not the position. Not useable for playing of course, but it was useful to test/illustrate the cause of the issue.

Z

zetto75

Participant

I don t know if auto a previous firmware the disgustino was better but the solution can t be change everytime the router channel. Is very uncinfortable. I’ve a high end pc a Wi-Fi 6 router on the 5 ghz only the quest 3. But in pcvr sometimes i see some lag.

Z

zetto75

Participant

Sorry the iPhone correct my with strange words.

Z

zetto75

Participant

Correct me.

Z

zetto75

Participant

I don t know if with previous firmwares the situation was better but the solution can t be change everytime the router channel.

LunchAndJosh

Inspiring

This has surprisingly gotten worse for me since v62 over the last few weeks, the spikes are becoming worse 😞

B

Babinok

Participant

Today, in a local community of 12 thousand people, we managed to find out that all owners of Quest 3 have these microfreezes. Even those who previously wrote that everything was fine with them, after carrying out the right tests, noticed the problem and now can no longer ignore it . ) A lot of people wrote that the problem exists. So I can safely assume that it is global and available in all headsets with the latest updates.

D

D3ft0ne

Participant

It's getting pretty rediculous tbh, in terms of no comm from Dev at all on this... It's not like it's a few users. This is pretty much a global issue.

K

krillme

Up and Coming

My brand new Quest 3 is also having this problem. I temporarily switched back to my Quest 2 and can confirm it DOES NOT HAPPEN on Quest 2.

Show more replies

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO