App frame rate drop when increasing devices refresh rate
Hello So I'm noticing some frame and GPU utilisation increases when I change the refresh rate of the Quest 2 I'm using the latest OVRMetrics to view the numbers App build with Unity 2019.4.34 Changing refresh rate using SideQuest The app is a steady 72 when at 72hz GPU hovering around 85 If I change the refresh rate to 90hz the app hovers around 74-76fps but GPU goes up to 96 Going to 120hz pushes the GPU up to 99 and drops the app frame rate to 69-70fps Is this to be expected? Or maybe its a bug with the OS (version 39.0.0.86.336) I don't need the app running more than 72fps but even if I set the OVRManager.display.displayFrequency in Unity, the OS appears to override it when I change the refresh rate
Oculus Quest App framerate way slower than same app on Oculus Go
Hello everyone, I recently developped an app for Oculus Go on Unity using the OVR Plugin, and now I'm trying to port it to the Oculus Quest. The Oculus Go App was a bit laggy because there was a lot of world space UI, so I found ways to make it run smoothly at 60 fps. When developping it for the Quest, I had to recreate a matching InputManager so it could work well with the controllers, and I changed OVRManager's target device from Go to Quest. But when I build the app, it runs at maximum 40 fps on the Quest, even though it was really smooth on the Go. Comparing both Profilers on my PC, I can't manage to find any difference : it looks like a lot of CPU usage is taken by EventSystem ( because of World space UI), Camera Rendering and OVRManager.Update() (which obviously can't be too altered by me (the raycasting part takes the most time)). Of course this is because my PC isn't using all the resources of the scene since VR isn't activated, but to my knowledge there is still no way to connect the Unity profiler to an Android Oculus device. Here is the Go App Profiler : And here is the Quest's : Behaviour script Update takes even less time on the Quest because I managed to optimize some things. So basically I want to know why the application takes way more resources on the Quest than on the Go. It can't only be the 6 DOF component. Any suggestion is welcome, Thank you !
