local pose used for EstimateFeatureMapQualityForHosting #81
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updated documentation and sample to use the local camera pose instead of the global camera pose.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated documentation and sample usage for
EstimateFeatureMapQualityForHosting.The issue is that the documentation doesnt specify and the sample uses the global pose of the camera. But actually the local pose is expected. This hasn't been an issue in the sample, because the AR Session Origin is at (0,0,0). This is very common, but there are use-cases where the Session Origin has to be moved, which would break the sample when using
EstimateFeatureMapQualityForHosting.