Occlusion not initialized on app launch

Bug Reports
1
  • Platform category: Unity
  • Unity version: 6000.0.69f1
  • Issue category: Real-time Mapping-Depth / Occlusion
  • Device Model & OS version: Nothing Phone 2a (Android 16)
  • NSDK version: 4.0.0-b2-26022000

This topic follows a previous one that was closed before I had time to reply ( Occlusion not working on latest ardk versions ).
Sorry for the delay, I haven’t been working on this project recently.

It seems that the bug is still occurring.

I recorded my phone while testing with Unity version 6000.0.69f1 and ARDK version 4.0.0-b2-26022000:

  1. Launching the application → occlusion appears to be disabled
  2. Minimizing / reopening the app → occlusion is working
  3. Minimizing / reopening the app again → the depth seems to get stuck on the last frame from before minimizing the application.

I also checked the logcat logs and noticed that “InfiniTAM - [INFO] Created ThreadPool with 1 thread” is only called during step 2 (when occlusion is working). If I’m not mistaken, this should be called when the application starts.

I’m also curious: am I the only one experiencing this issue?

2

Hi there,

Thank you for reporting this to us. I have passed it along to our engineering team, and will update you when more information becomes available.

Kind regards,

Maverick L.

3

Hi Flavian,

Thank you for your patience. I’m still working with our engineering team to narrow down the cause and appreciate your understanding. In the meantime, do you have access to a Samsung Galaxy or Google Pixel you can try to reproduce this issue on?

Kind regards,
Maverick L.

4

Are you able to reproduce this in our sample project showcasing occlusion? If not, can you provide your exact project setup?

5

Hi Flavian,

I wanted to follow up. Have you had the chance to test occlusion on another device or with the sample?

Best,
Maverick L.

6

Hi Maverick,

I have tried out the sample project on my Nothing Phone 2a (Android 16) with Unity 6000.0.69f1.
I have been able to reproduce the bug in this project as well.

Unfortunately, I don’t have access to a Samsung Galaxy or Google Pixel to try to reproduce the issue on.

7

Thank you for checking that. I will reach back out when I have more information to provide to you.

8

After further consultation with our engineering team, we believe the issue is most likely related to limited Google ARCore support on the device currently being used.

We sincerely apologize for the inconvenience and appreciate your understanding.