Compatibility with Google Cardboard: render order issue on iPhone

[ocularbioengarhku]

Can I change the render order in Unity Sentis?

I am making a AR app that using Unity Sentis + Google Cardboard. The example I am using is "Depth Estimation Sample". The two plugins work fine in the editor, but there comes the issue when building to mobile phone: the camera feed and depth map is not displaying in VR mode, it's only happen in iPhone currently.

Program Structure

1. Initialize Google Cardboard in Awake()
2. After the Google Cardboard finished setup, wait for the camera permission
3. If it is granted, setup the Sentis and just call the code that originally inside Start() in the script of InferenceWebcam

iPhone

It can't display the camera feed and depth map in VR mode. But the Google Cardboard default close and gear button is still clickable but didn't display on screen. So I wonder if there is a display order issue that the Sentis output result is draw under the Google Cardboard UI? And can I change the render order in Sentis?

Tested devices:

• iPhone 13 mini
• iPhone 6s
• iPhone 7 plus

Android

Except the first open after installing the app, the camera feed and depth map works fine in VR mode (Google Cardboard)

Tested devices:

• UleFone Armor 8 Pro
• Nokia 7.2
• Samsung Galaxy J7 Prime

//----

Actually the both camera playback and depth map is quite lag when testing in all my android phones and old iPhone 6s and 7 plus. But that another issue and will open another post for it. Thank you

[ocularbioengarhku]

Please see this thread on Google Cardboard for more information, thank you!

[ocularbioengarhku]

Kind of find out the problem of this issue is cased by the different versions in Google Cardboard and Unity Sentis. I decide to close this thread and open other new threads to discuss the versioning issue in more basic and easy example.

If you are interested, please see the following links:
Can’t display VR mode on iPhone in Unity 2023.2+
Abnormal darken color in VR mode on iPhone, Unity 2021.3+
Depth estimation example on v1.3.0 vs v1.2