cancel
Showing results for 
Search instead for 
Did you mean: 

v46 frame drops/stutters/headroom dips

NumbrOneDad
Protege

Edit: For anyone stopping by looking for a solution, there isn't going to be one. This issue is falling on deaf ears by meta staff. The issues described exist both in standalone and pcvr link/airlink. It seems to be widespread, possibly most or all quest 2 devices, yet it's been relayed that it's only a small subset of users experiencing the issue... sure. That's definitely why we can totally troubleshoot and fix it /s

The only remedy is going to be through an update issued by meta. I/You/We have done all the troubleshooting and bug hunting possible, all signs point to them. Good luck everyone!

...

Frame drops, reprojection (even with ASW set to Off), stuttering, performance degradation, and gpu headroom dipping to 0 or even negative has been since v44, and now v46 as well. I have come across this issue in many different posts here in the meta forums, elsewhere as well, and no one has come to any conclusions other than this HAS to be an issue with oculus software itself. Witnessing OVR errors and socket errors amongst others in the console logs and no previous fix is capable of providing any remedy to the current issue. I have tried all previous working drivers from nvidia, uninstalling with DDU and reinstalling old to new. No change. HAGS set to off, clean installed oculus based off of official support techniques (safe mode and manual folder deletion), toggled and focused console window, set high priority on ovrserverx64 and game running, disabled link sharpening, disabled mobile ASW, reset all graphic settings to default, set vsync to off in nvidia control panel, reset nvidia control panel, nothing. These issues stem directly from the oculus software and there's no chance of user error. For those hoping to chime in about windows update breaking the software, that is also untrue. I have now tried windows 10 on updates 20h1, 20h2, 21h1, 21h2, and 22h2 and this issue is present across all of them. I also tried on windows 11 builds 21h2 and 22h2 and the same issue persists. We desperately need a community update from @Ryanality as i know im not the first to raise this issue. I wish i could say it was just user error, machine setup etc. There are multiple internal errors displayed in the console window and i've submitted these logs with the support team as have the others experiencing this issue. It would be great if we could PLEASE get a public update regarding this issue. I have been troubleshooting this for several weeks straight.. i'm going absolutely mad. PLEASE HELP US!!!!!!!!!!!!!!!!!!!!!!! Basic troubleshooting, clean installs, NONE OF IT WORKS! 2 years of using this headset and software...and this is the worst its been by far! 😧

268 REPLIES 268

Confirming I'm having the same issues.

In my case, it all started with v47 updates, my system was working just fine with previous version.

v47 was the one that broke the rendering engine and raised the encoder issues.

If I look at the logs, i'm seeing stuff like this:

 

[Service_2022-12-16_16.49.59.txt] 16/12 17:32:44.095 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2022-12-16_16.49.59.txt] 16/12 17:32:44.791 {!ERROR!} [xrstreaming] Frame 5027 dropped due to encoder backup
[Service_2022-12-16_16.49.59.txt] 16/12 17:32:44.791 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2022-12-16_16.49.59.txt] 16/12 17:32:45.495 {!ERROR!} [xrstreaming] Frame 5077 dropped due to encoder backup
[Service_2022-12-16_16.49.59.txt] 16/12 17:32:45.495 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2022-12-16_16.49.59.txt] 16/12 17:32:45.559 {!ERROR!} [xrstreaming] Frame 5080 dropped due to encoder backup
[Service_2022-12-16_16.49.59.txt] 16/12 17:32:45.559 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2022-12-16_16.49.59.txt] 16/12 17:33:07.251 {!ERROR!} [xrstreaming] Frame 6612 dropped due to encoder backup
[Service_2022-12-16_16.49.59.txt] 16/12 17:33:07.251 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2022-12-16_16.49.59.txt] 16/12 17:33:12.681 {!ERROR!} [xrstreaming] Frame 7001 dropped due to encoder backup
[Service_2022-12-16_16.49.59.txt] 16/12 17:33:12.681 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2022-12-16_16.49.59.txt] 16/12 17:33:29.525 {!ERROR!} [xrstreaming] Frame 8208 dropped due to encoder backup
[Service_2022-12-16_16.49.59.txt] 16/12 17:33:29.525 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2022-12-16_16.49.59.txt] 16/12 17:33:29.605 {!ERROR!} [xrstreaming] Frame 8213 dropped due to encoder backup
[Service_2022-12-16_16.49.59.txt] 16/12 17:33:29.605 {!ERROR!} [Kernel:Error] OVR Error:
[Service_2022-12-16_16.49.59.txt] 16/12 17:33:34.136 {!ERROR!} [xrstreaming] Frame 8535 dropped due to encoder backup
[Service_2022-12-16_16.49.59.txt] 16/12 17:33:34.136 {!ERROR!} [Kernel:Error] OVR Error:
 
 
I did not have these errors before the update, so looks like the v47 update screwed something on the encoder side on my machine.
 
My machine is a quite low-spec machine (AMD Ryzen 5 2600, MSI B450 TOMAHAWK MAX II, 16GB Ram, Nvidia 970, Windows 10.0.19044 Build 19044) but it was working just fine before the last update.
Tried to factory-reset the Meta Quest 2 a couple of times. Sometimes it solves the issue for some time (usually in my first gaming session), but from the second gaming session going on the issue always come back. 

I know we don't need root, but this non downgradable firmware is meant to protect quest from being rooted, or tweaked.  Basically meta feeling insecure about their software, that if people would have any option they would switch.

 

Hey guys, I went ahead and asked about this issue. I wasn't able to really get any information, but I do want it to be known that they are aware and working on this currently. For now, please continue to post any information you may have on said issue that could be of use.

Sometimes it's okay to be a little Bing Chilling

New findings, might be related, if you'll set dynamic bitrate offset in ODT any except for 0, bitrate become much more stable and tends to stick to whatever you have set as dynamic, this increases lags and frame drops, but it takes much more serious lag/sequence of droped frames to drop bitrate to 10 mbit to slowly grow back up in few seconds. On default any frame drop usually lead to bitrate being dropped to 10mb.

Suggest everyone to test V47.1, something defenetly changed, encoder errors not as frequent in logs and it feels different. 

My post from v47 release thread:

Well, can't say it got fixed, feels better maybe placebo, i'll test update, do clean reinstall of everything. First run i had was defenetly improved, i finaly was hitting 180-190 mbit bitrate most of time, but it was stil dropping frames, it just wasn't acompanied by bitrate being droped. On second connect it just went back to exactly how it was before, feels better btw, like they changed something about vsync or something. Also Frame dropped due to encoder backup is not seen as frequently in logs.

So nope, isn't fixed yet

Checked again, clean install and all. Exactly same in the end, in beginning it feels better, and it actually drops less fps, but after some time it get back to same drops, with same frequency

@fatal88 Did you checked update out, how is it on your side? For me there is no more enoder errors in logs, but frame drops same as before. What about you?

 

Not every frame drop I notice in the headset, or that is represented as a dip on the Oculus Link HUD's encoder frame rate graph, corresponds to an error in the log - though some definitely do correspond.

I got the 47.1 update on desktop (though version still shows as 47.0 in the desktop app's settings?) and I'm still seeing the encoder dropping frames.

The 47.1 update fixed the micro-stuttering and frame drops for me.
Assetto Corsa Competizione was the most affected. Just confirmed that there are no random frame drops on the performance monitor right after the Oculus PC software update.

MSI Z690 A DDR4 - i7 12700KF - Gainward RTX 3080 Phantom GS - 32GB DDR4 3600MHz