You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Examples of when environment can cause plane detection failure (or slow) would be low light, or bright walls, highly textured walls or moving surfaces etc.
The text was updated successfully, but these errors were encountered:
Is it possible to figure out the failure reason for plane detection (via WebXRPlaneDetector and/or light estimation) in Babylon?
Why? We want to show in app remediation prompt to user in the lines of the latest ARCore best practices which suggests to inform the user what went wrong (or why it is taking so long) https://developers.google.com/ar/design/environment/definition#environmental_limitations
Examples of when environment can cause plane detection failure (or slow) would be low light, or bright walls, highly textured walls or moving surfaces etc.
The text was updated successfully, but these errors were encountered: