Add Draco quantization workaround for point clouds #9908
Merged
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.
This fixes a regression from 1.86 after updating Draco, where
SkipAttributeTransform
broke future attribute lookups withGetAttributeByUniqueId
. To reproduce, see this Sandcastle and select the "PointCloudDraco" tileset.This change is analogous to #9904, but since
decodePointCloud
always tries to callSkipAttributeTransform
on"POSITION"
and"NORMAL"
, those are the two attributes that useGetAttributeId
andGetAttribute
instead ofGetAttributeByUniqueId
.