Can't meet FPS requirement in build - EDIT: partial fix
Hi, After running the automated VRC tests in the oculus debug tool, i'm growing concerned about the ability to accurately test my framerate for oculus rift s. The vrc testframerate fails, giving me an average of 67.5 fps (I should be hitting 80 for this oculus rift s). if I enable the performance hud and run the app again, i see conflicting statistics. Application GPU/CPU render times are about 3ms each, but the "app queue ahead" time is around 30ms? App framerate is shown perfectly locked at 60fps. If my total frame time is somewhere around 6-7ms, why am i getting a framerate at half that? The first scene in my unity build is a nearly empty menu scene, just a skybox and a simple menu. This runs perfectly fine in the unity editor, and usually a non-editor build will always run a little faster. I've tried changing vsync settings, running the app with nothing else open, restarting my computer even, nothing helps me hit the required 80fps in a near empty scene! Edit: I've upgraded from oculus integration 1.41 to 1.42, no change there. I also tried toggling the queue ahead option in the OVRManager component, didn't seem to change anything. Here's me rendering an almost empty scene in unity editor, easily getting 100+fps Unity 2019.2.1, windows 10 running a GTX 970, oculus integration from ap store version 1.41, will try upgrading to 1.42
Hello VR Project Failing VRC.Quest.Performance.1 on startup
I recently submitted a game to the Meta Quest App Lab, and it was rejected for failing VRC.Quest.Performance.1, which means the frame rate dipped below allowable levels. When watching the app using the MQDH Performance Analyzer, it showed that a drastic frame drop occurred at the instant the app was launched- before/as the Unity splash screen is shown. In an effort to understand this issue, I built the "Hello VR" introductory project described here: https://developer.oculus.com/documentation/unity/unity-tutorial-hello-vr/. When profiling this incredibly lightweight application using the Performance Analyzer, I still had performance-check-failing lag at application startup. I feel like I am missing something- what is the standard way to launch Unity games that does not result in frame drops? In my game I am using oculus splash screen and a lightweight initial loading scene, but it has not resolved the initial lag. This is a screenshot of the Performance Analyzer running the "Hello VR" app.
Performance issue with OVRPlugin using OpenXR backend
Hello, our game is using Unity 2020.3.32f1 and Oculus Integration v39.0.0. We found in profiler that with OpenXR backend, OVRManager takes about 2ms CPU every frame on a Quest 1 device, while it only takes about 0.32ms if we switch back to the legacy OVRPlugin with LibOVR and VRAPI backends. (The profiler data were taken using a new project with only Oculus Integration 39.0 added, and with the sample scene MRC in Oculus/VR/Scenes) With deep profiling on, we found that it is from OVRP_1_16_0.ovrp_GetControllerState4(). We also found that if we remove the battery in 1 or both Oculus Touch controllers, the time drops (with 1 battery removed, it drops to around half and with both removed, it drops to near 0ms, but of course we can no longer play without controllers). As a result of this, we can hardly switch to the OpenXR backend due to the FPS requirement in Quest 1. Anyone knows if I am missing something or is it a problem with the plugin itself? Thank you.
