Forum Discussion

GamerReality's avatar
GamerReality
Start Partner
6 months ago
Solved

My project runs on Quest 2 at 18 FPS (GPU-bound), no matter the scene or XR Rig

Our game's Quest performance has always hovered around 36 fps while in development, which I've come to find out was due to high batch counts and complex lit material shaders on every object. But now...
Android
graphics
performance
support needed
Unity
  • GamerReality's avatar
    GamerReality
    6 months ago

    Thanks for the quick reply. I was able to get my empty scene to run at 60 fps on my Quest again after these changes (I did them one by one and they each had a positive impact):

    • Turned off 4X MSAA and disabled the anti-aliasing feature in the camera. I read on the Stylized Water 3 Discord that this was causing glitches with their asset on Quest for some people.
    • Turned off Stylized Water 3 features on the URP-Performant-Renderer asset I'm running on Quest.
    • Deleted the Screen-Based Ambient Occlusion setting from my other PCVR Universal Renderer Data profile.

     

    In the default Unity XR toolkit scene, it hits 72 fps, but sometimes dips to 55 in a CPU-bound way. That might be from building the APK as a development build with script debugging enabled both in the build settings, though.

Cesar_Ortega_Art's avatar
Cesar_Ortega_Art
Start Member
6 months ago

That sounds really rough, sorry that is happening. A few quick sanity checks you might try:

- Check that Quest store apps run normally first, just to rule out a headset or thermal issue.

- Was the project originally a URP project? If it was converted, that can sometimes cause odd rendering issues. In Project Settings > Quality, make sure your Mobile URP Asset is selected for Android and you’re using the lowest quality level.

- Turn off allpost-processing or extra renderer features (SSAO, bloom, custom passes). Quest can’t handle full-screen effects very well.

If all else fails, create a brand new empty URP/OpenXR project and do a quick APK test to standalone, if that runs smoothly, something in your main project, like a package or render setting is dragging performance down.

I’m also using Quest 2 with Unity 6, and standalone runs fine here. If you want, I can share my project/quality settings so you can compare. Just let me know what you need to see.

GamerReality's avatar
GamerReality
Start Partner
6 months ago

Thanks for the quick reply. I was able to get my empty scene to run at 60 fps on my Quest again after these changes (I did them one by one and they each had a positive impact):

  • Turned off 4X MSAA and disabled the anti-aliasing feature in the camera. I read on the Stylized Water 3 Discord that this was causing glitches with their asset on Quest for some people.
  • Turned off Stylized Water 3 features on the URP-Performant-Renderer asset I'm running on Quest.
  • Deleted the Screen-Based Ambient Occlusion setting from my other PCVR Universal Renderer Data profile.

 

In the default Unity XR toolkit scene, it hits 72 fps, but sometimes dips to 55 in a CPU-bound way. That might be from building the APK as a development build with script debugging enabled both in the build settings, though.

→ Find helpful resources to begin your development journey in Getting Started

→ Get the latest information about HorizonOS development in News & Announcements.

→ Access Start program mentor videos and share knowledge, tutorials, and videos in Community Resources.

→ Get support or provide help in Questions & Discussions.

→ Show off your work in What I’m Building to get feedback and find playtesters.

→ Looking for documentation?  Developer Docs

→ Looking for account support?  Support Center

→ Looking for the previous forum?  Forum Archive

→ Looking to join the Start program? Apply here.

 

Recent Discussions