Locked at 35fps in UE-5.3.2 VR Preview after having 72fps consistently

[Swazzler]

I use UE-5.3.2, the MetaXR Plugin, Meta Quest Pro and MetaHumans for a VR project. My PC setup includes 32gb RAM and a Nvidia 3080ti. 

Typically, when I use the VR Preview, I consistently get 72fps which is the Hz the Quest Pro uses. However, when I work on the project, e.g. move actors around the scene or change some scripts, for a few minutes (5-15min), I only get 35fps/36fps and it seems to be locked on this fps value. After restarting Unreal, I have 72fps again.

What could be the problem?

[kutlaytunc]

Seems like ASW(Async Space Warp) lock; it is quest's frame generation thing. I disabled on regedit because it was reactivating after restart. You can check for the solution here.

[Swazzler]

@kutlaytunc I looked into the Oculus Debug Tool and it says that "(PC) Asynchronous Spacewarp" is disabled. I would like to test whether ASW is the problem before I change regedit stuff like in your suggested solution.

Do you have any idea how this can be (see the attached picture)?

[natebev3600]

Hello @Swazzler,

Make sure in your oculus settings you have “power saving mode” turned off, this reduces your frame-rate. This does come at the cost of having less battery life. 

Have a good day!
-Nate

[kutlaytunc]

When ASW is enabled, it locks itself to 36FPS and generates every other frame to reach 72FPS. However, after restarting your PC, this setting resets, and ASW activates again. Instead of manually disabling it each time, you can use a Regedit entry to automate the process.

First, set your desired FPS limit in the Meta Quest Link desktop app. Then, use Regedit to disable ASW permanently. This way, it will remain disabled even after restarting your computer.

If this doesn't fix your issue, it solved your future problem trust me ‌‌🖖