Forum Discussion
Solved
suggestedCpuPerfLevel and suggestedGpuPerfLevel appear to do nothing
Setting OVRManager.suggestedCpuPerfLevel and OVRManager.suggestedGpuPerfLevel to OVRManager.ProcessorPerformanceLevel.Boost has no effect on CPU and GPU levels when observed through the OVRMetrics to...
They are "suggested" levels because the power management system can override them to conserve battery or manage overheating.
"Gets or sets the current suggested CPU performance level, which can be overriden by the Power Management system."
Is your app maxing out the CPU or GPU utilization? If not, the system may just be deeming the higher levels unnecessary.
Looks like the UK release notes are behind. Check the US version:
https://store.facebook.com/help/quest/articles/whats-new/release-notes/
Thanks for the quick response pro_zac
I actually have them set to ProcessorPerformanceLevel.PowerSavings and the CPU sits at 0 and GPU 1 most of the time. It's only when loading level blocks (they animate on) does it need the extra grunt. CPU up to 1-2 GPU up to 2-3 for a few seconds. to keep the 72FPS.
And we can only see this dynamic changing if we set the levels to -1 via ADB.
If don't do this then the CPU and GPU stay at 1, but the frame rate drops to 56-60
You can hardly notice it but it violates Oculus submission.
Why would the Power Management system keep them at 1 1 if the device is not throttling, overheating?
So now today I can't repeat this situation. My app is updating the GPU and CPU when it needs a bit more grunt and dropping them back when it doesn't.
I've notice the OS is now at 40.0 so maybe there is a fix in there for what I was experiencing
Release notes only go up to 38.0 so will have to wait
https://store.facebook.com/en-gb/help/quest/articles/whats-new/release-notes/
Looks like the UK release notes are behind. Check the US version:
https://store.facebook.com/help/quest/articles/whats-new/release-notes/