Skip to content
This repository has been archived by the owner on Sep 14, 2021. It is now read-only.

Occlusion bug using Depth API in Unity 2018.4 ('HelloAR' demo scene) #763

Open
Lord-Min opened this issue Oct 29, 2020 · 1 comment
Open
Labels

Comments

@Lord-Min
Copy link

Lord-Min commented Oct 29, 2020

VERSIONS USED

  • Unity: 2018.4.28f1
  • ARCore SDK for Unity: 1.2.0
  • Gradle: 5.6.4
  • Device manufacturer, model, and O/S: Galaxy Note 8(Andorid OS 9), Galaxy s10(Andorid OS 10)
  • Unity Editor PC: Windows10 Pro

STEPS TO REPRODUCE THE ISSUE

Currently, there is a bug where an afterimage appears in the camera background when using the Depth API. (See attached image)
https://www.dropbox.com/s/0404grnjr9ctd13/Screenshot_20201029-210437_SpectatorV.jpg?dl=0
https://www.dropbox.com/s/sbm8ctyn3123j83/Screenshot_20201029-210458_SpectatorV.jpg?dl=0

Testing took place in the'HelloAR' demo scene

The afterimage is continuously updated every 5 to 10 seconds, and the occluded object is not properly occluded because it is covered by the afterimage texture.

What I further discovered is that when I disable the'DepthEffect' script the bug goes away. It seems to have something to do with the DepthEffect script.

Is there any way to fix this issue?

WORKAROUNDS (IF ANY)

In Unity 2017.4.40f1, we have confirmed that the Depth API is working properly and functions neatly without afterimages.

It seems unclear whether it is a problem with the Unity version or the Gradle version.

@Lord-Min Lord-Min added the bug label Oct 29, 2020
@Lord-Min
Copy link
Author

#745
It is the same issue as this one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant