Seeing identical behaviour using Air Link which uses HEVC. I guess I'll be keeping an eye on this since it's the only thing not working for me so far on 11.
What version of Oculus are you using? And what build of Windows 11? The latest PTC for Oculus is 32.0.0.41.423. I'm not certain what the latest W11 is, but the last build I tried with was 22000.100.
31.1.0.67.507, on 22000.100 and 22000.120. Haven't tried the latest build (132). This was on a Q2 and 2080S. Tried 120 Hz and a couple of others but it seems like it always drops just a bit below refresh rate after said 25 seconds.
If you (or anyone else) get free time to do so, I'd like to hear how the latest W11 build and PTC Oculus work. There's been 2 V32 PTC Oculus builds released that were seemingly a bit small, but have no changelogs mentioned, and I'm wondering if either of those happened to address W11, or if W11 .132 maybe fixed something. I'm back on W10 currently because of this and can't test it myself.
Just tried it on Win11 .132, sadly no changes on either release or PTC 32.0.0.41.423. Same symptoms. I'm guessing Oculus likely won't be looking at this until Win11 reaches general availability.
No real change with Windows 11 22000.160 and Oculus 32.0.0.47.423 (PTC) with both wired Link and Air Link (still drops frames). Although instead of only dropping frames after 25 seconds, it starts dropping frames immediately as soon as the Link session is initiated, but this only happened a few times that I've seen. Other times, the frame drops start after 25 seconds. I wonder if there's some way to figure out why this inconsistency happens.
Someone on Reddit: I haven't checked that option on W11, but it seemingly defaults to the Quest 2 for the audio input/output on W10. Edit: Didn't help.
Oculus client V33 (33.0.0.22.194, PTC) is available now. I haven't tested it on W11 yet. There appears to be a new Link option in the Debug Tool, so presumably this build brings some changes to Link in-general.
Oculus client V33 (33.0.0.28.194, PTC) seemingly works on W11 22449.1000. Although I'm skeptical as to why it's working or how consistent it'll continue to be. The first two times I tried it with wired and Air Link, it was a laggy mess and still dropping frames. I went to Oculus Debug Tool, did Service -> Toggle console window visibility, allowed the UAC prompt, and went back into wired Link, and performance was fantastic even after 25 seconds (Beat Saber in Oculus mode). This will need more investigation, but I wonder if Oculus isn't starting with admin rights or something.
Well that has to be the oddest bug I've seen in quite a while with any software. Link is a laggy mess by-default, but if you go to the Debug Tool and Toggle the console window visibility, Link works fine. I did this 5 times in a row back and forth and results were consistent (with console window hidden, Link is laggy; with console window visible, Link is fine). So for whatever reason, you need the console window to be visible in order for Link to work on W11 currently it seems.
Just had a go on 22000.194 as well on Oculus 33.0.0.28.194. Really nothing interesting of note, it's been the same since the very first leaked Win11 build. The console workaround however works perfectly and isn't too annoying so I'll probably be sticking on Win11 for now.