VSync behaving strangely

Dear VR
Brotherhood,

we’re finishing developing of gear VR game
based on Unity. So far everything was pretty much ok. Unfortunately recently we’re
suffering from decreased performance. Trying to resolve these we’ve been
removing unnecessary things from scenes and optimizing game with OVR plugin
options. In doing so we’ve found some troubling issues:

- Cpu and
gpu levels set via “OVRPlugin.cpuLevel” and “OVRPlugin.gpuLevel” accessors had
none impact on performance nor framerate.

- VSync
embedded into Oculus SDK is snapping very rapidly from 60 to 30 frame per
second. (Unity vSync is disabled.)

- Changing
cpu or gpu levels was disabling (we’re guessing here) said vsync for a brief
moment resulting in peak of framerate.

Above
mentions and some testing breed questions:

- Have
anyone ever experienced something similar?

- Is it a bug
or intended behaviour?

- Are cpu
and gpu levels some kind of obsolete or disabled code? (We’re been checking reference
for such but found none information on it).

- What are
real available levels for CPU and GPU? Reference mentions 0-2, but there are
forum posts suggesting 0-3. Plugin itself accepts anything (even negative numbers)
without error, warning nor clamp of values.

Some
reference to previous posts on related subject:

https://forums.oculus.com/developer/discussion/23675/default-cpu-gpu-throttling-level-for-unity-applications

https://forums.oculus.com/developer/discussion/42111/automatically-set-cpu-gpu-levels