Just wondering if anyone else experienced this. Happens to coincide with the announcement of Framesync, so wondered if they might be related.
<meta-data android:name="com.oculus.enable_frame_sync" android:value="false" />Have added the above to my AndroidManifest for next update just in case.
Yes! you’re on the right track.
https://developers.meta.com/horizon/blog/framesync-meta-horizon-os/
Recent updates introduced FrameSync, and it can cause unexpected FPS drops depending on timing/CPU load.
Disabling it via your code is a valid test and has helped others stabilize performance.
You can also check that the app isn’t becoming CPU-bound (FrameSync can expose this), your fixed timestep / vsync settings and the GPU/CPU levels (OVRManager or equivalent)
If disabling FrameSync improves things, then it’s likely the new scheduling interacting poorly with your workload.
