Repository navigation
Quest 3 at native panel resolution and 200 Hz over USB: the decoder is not the limit, the low-latency decode mode is #3410
Replies: 2 comments
|
Thanks for the heads up. This is such a good quality of life, not having to worry about everything breaking down at higher bitrates or refreshrates. We are still far from having a system that configures various settings dependent on each other. It makes things awkward because we want to provide the maximum flexibility and control to the user, which is a double-edged sword. Since this is such a big issue, i think we should extrapolate the Do you think you can open a PR on this? Make sure to follow our AI guidelines. Tweaking dynamically the encoder setting is difficult, so I would leave that out for now. |
|
Closing as AI generated discussion |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Sharing measurements because the usual explanation for the 120–144 Hz ceiling on Quest 3 ("the decoder can't go faster") turned out to be a configuration limit in how the decoder is driven, not the silicon.
Disclosure up front: I did this with an AI assistant (Claude Fable 5.1) running the measurements, reading the ALVR source and the headset's codec files, and iterating settings over adb while I tested in the headset. I know a lot of people are tired of AI-assisted mods and bug reports, and I understand why. With my day job I would not have had the time to debug this by hand, so I'd rather share it with that caveat than sit on it. Every number below was measured on my setup, and I'm happy to re-run anything.
Result
SteamVR → ALVR v20.14.1 → Quest 3 over USB 3, 2048×2144 per eye (4096×2144 encoded), foveated encoding off, 200 Hz.
ALVR statistics: 199.6–199.9 fps delivered, decoder 9.4–10 ms, encoder 4.3–4.5 ms, ~42–50 ms total pipeline, 0 stale frames, 0 queue overflows. fpsVR in-headset: 200 FPS, 0 dropped, 0.0 % reprojection. H264, HEVC and AV1 all hold it at ~200 Mbps CBR.
What was limiting it
vendor.qti-ext-dec-low-latency.enable = 1(the default inmediacodec_extra_options). In this mode the Qualcomm decoder returns each frame before starting the next, so throughput ≈ 1 ÷ latency. At native resolution that is ~17 ms per frame ≈ 60–70 fps, whatever the codec or bitrate. Setting it to 0 and raisingmax_buffering_framesto 4 lets the decoder pipeline: the same frame now costs ~9.4 ms of latency but the pipeline sustains 200 fps. The headset's own/vendor/etc/media_codecs.xmlratesc2.qti.{avc,hevc,av1}.decoderat 7,776,000 blocks/s (≈2 Gpix/s, performance point 3840×2160 @ 240), well above the 1.76 Gpix/s this stream needs.Cost: about two extra frames of latency (≈10 ms at 200 Hz) compared with the low-latency mode. The Quest home overlay is noticeably laggy while this runs; the SoC is close to its ceiling.
Note:
max_buffering_framesabove 5 overflows the client's 10-slot ImageReader on focus loss and freezes the stream (MaxImagesAcquired); filed separately as a bug. 4 is the working value.Outside ALVR's scope, but needed to reproduce
Horizon OS v2.7 only enumerates the extended refresh rates (>120 Hz, up to 207) to some apps; ALVR's client gets ≤120, so
preferred_fpsabove 120 is rounded down ("Chosen refresh rate not supported. Using 120Hz"). On this headsetadb shell setprop debug.oculus.allRefreshRates 1(resets on reboot) makes the runtime enumerate every panel mode (72…207 at 4128×2208). Manifest changes (uses-horizonos-sdk, targetSdk 34,supportedDevices) did not. 207 Hz works too, but this unit shows ghosting at the top of the view at 207; 200 is clean.Suggestion
A "throughput" decoder preset (low-latency flag off + buffering 4) next to the current low-latency default, and a
preferred_fpsslider range above 120 now that Quest 3 exposes up to 207 Hz. Happy to test patches.Settings used (session.json)
PC: Windows 11, i5-12400F, RTX 4070 (driver 617.14), SteamVR 250820. Headset: Meta Quest 3, Horizon OS v2.7 (build 2026-09-24).
All reactions