GLTFExporter: Remove truncateDrawRange
option.
#24625
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.
Related issue: -
Description
This PR removes the
truncateDrawRange
option fromGLTFExporter
.The feature was originally implemented for A-Painter so only geometry data are exported which were defined via
BufferGeometry.drawRange
. However, indexed geometries were never supported.It seems to me that something application specific has been moved into
GLTFExporter
which I don't think is appropriate.BufferGeometry.drawRange
should be evaluate by the renderer, not exporters. SinceGLTFExporter
is the only exporter that honorsdrawRange
, I suggest to removetruncateDrawRange
and state that exporters always process the entire geometry.Closes #15104.