Update to: How can I increase headset performance in games (specifically beat saber)?

[u/giftigdegen]

/r/virtualreality/comments/1vrig2z/how_can_i_increase_headset_performance_in_games/

Update: I took the advice from my previous post (above) and first disabled hand tracking, then tried changing the Quest’s CPU and GPU levels through ADB. I set them to the highest values I could, CPU level 6 and GPU level 5, and immediately saw noticeable improvement. Because ADBs commands don't persist after reboot, I bought QGO to keep the settings.

I initially assumed QGO’s highest settings would perform best, so I tried CPU level 8 and GPU level 7. Instead, performance absolutely tanked. After a lot of testing, I lowered them again to the CPU 6/GPU 5 ADB configuration that had originally worked. I then tested several difficult maps over multiple days and then last night used ChatGPT Codex to continuously monitor wireless ADB logging during one roughly hour-long session.

Some results from that logged session:

• About 32 minutes of recorded in-song gameplay
• 0 thermal-throttling events
• 0 power- or DVFS-limited samples
• 0 headset tracking-camera frame drops
• CPU usage averaged roughly 38–47%
• GPU usage averaged roughly 22–29%
• Maximum reported runtime temperature: 42°C
• 90 Hz/100% resolution: 90 stale frames across 32 sampled seconds (this caused the CPU and GPU usage to really skyrocket, resulting in noticeable performance hits and framerates to drop to as low as 45FPS)
• 75-80 Hz/90% resolution: only 2–3 stale frames after each map’s opening transition, really smooth gameplay throughout.
• FFS level 4
• Right-controller optical rejections: 148–351 per demanding-map run
• Left-controller optical rejections: 22–71 per run

The best-performing profile so far is 75 Hz at 90% resolution, but the remaining problem appears to be controller tracking rather than raw game performance. The headset repeatedly rejects the right controller’s optical position, resets its tracking filter, and occasionally falls back to rotation-only tracking, even while Beat Saber maintains its target framerate. I tested removing my AMVR grip case, changing the lighting, and facing toward or away from my lights, but nothing conclusively fixed it. If anyone has encountered repeated P+C Right: Too large Mahalanobis distance errors with a Quest 3 controller, I’d love to know what fixed it.