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.