cancel
Showing results for 
Search instead for 
Did you mean: 

Stuck on splash screen when upgrading to SDK v57 and Quest 3

SanCity
Protege

Tried upgrading my project from

com.unity.xr.oculus - 4.0.0

to:

com.unity.xr.oculus - 4.2.0-exp-env-depth.1


and

com.oculus.integration.interaction - 0.46.0

to

com.oculus.integration.interaction - 0.57.0


I also switched from GLES to Vulkan as was needed for Depth API to work. When deploying and launching the game on my Quest 3, it just get's stuck in the loading screen. Tried to read the logs, but there is nothing related to the id of my game. Anyone has any ideas what it can be?

Attaching some screenshots of my settings and Android Manifest.json-file:

SanCity_7-1698085076378.png

 

SanCity_0-1698084875032.png

SanCity_2-1698084979915.png

SanCity_3-1698085006949.pngSanCity_4-1698085013816.pngSanCity_5-1698085025392.pngSanCity_6-1698085033985.png

 




2 REPLIES 2

SanCity
Protege

After trying Metas XR repo Discover: https://github.com/oculus-samples/Unity-Discover, I noticed that they didn't use OpenXR. So tried disable it in XR-plugin management and switch to Oculus instead. And then it worked. Anyone has any idea why that might be?

Probably because there are some features in MR that are only available for Oculus. I have the same issue as you, after moving from Quest 2 to Quest 3 and can't find a solution. Tried to do as you did, but it doesn't resolve the issue. The weird thing is that it doesn't even show the Unity splash screen. If I disabled Oculus splash screen then I only see the three dots, indicating the app is loading.