Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detecting user's physical environment impact on plane detection #33

Open
jp833 opened this issue Aug 25, 2021 · 0 comments
Open

Detecting user's physical environment impact on plane detection #33

jp833 opened this issue Aug 25, 2021 · 0 comments

Comments

@jp833
Copy link

jp833 commented Aug 25, 2021

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.

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

No branches or pull requests

1 participant