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
{{ message }}
This repository has been archived by the owner on Sep 14, 2021. It is now read-only.
I'm working on a project in which i'm trying to place an object "underground" by mapping a street and then spawning an object under the generated plane.
To generate the plane I'm using the DetectedPlaneGenerator script from the examples, the only problem is that the street i'm mapping is inclined by about 10 degrees, and the planes generated don't follow the slope, but instead are half floating over the street and the other half goes inside.
Is there a way to get the plane inclination from the feature points, or by allowing the planes to be inclined would impact too much the plane detection, generating planes where it shouldn't?
To replicate the "issue" you can build the HelloAR project and try to map an inclined street, then move to the side and lower your phone so that you see the plane edge. Thank you!
The text was updated successfully, but these errors were encountered:
I'm working on a project in which i'm trying to place an object "underground" by mapping a street and then spawning an object under the generated plane.
To generate the plane I'm using the DetectedPlaneGenerator script from the examples, the only problem is that the street i'm mapping is inclined by about 10 degrees, and the planes generated don't follow the slope, but instead are half floating over the street and the other half goes inside.
Is there a way to get the plane inclination from the feature points, or by allowing the planes to be inclined would impact too much the plane detection, generating planes where it shouldn't?
To replicate the "issue" you can build the HelloAR project and try to map an inclined street, then move to the side and lower your phone so that you see the plane edge. Thank you!
The text was updated successfully, but these errors were encountered: