USDZExporter: Add support for interleaved data. #22633
Merged
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
|
Thanks! |
|
@Mugen87 do you think each exporter should implement this separately, or would there be a good place to move common exporter functionality (like deinterleaving data, denormalizing, making textures readable, ...)? Thanks! |
|
Supporting interleaved buffer data definitions happens automatically when the dedicated interface of The other features you have mentioned should ideally not implemented per exporter. As a first step, there is #22874 which tries to integrate (de)normalization in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Related issue: #22609 (comment)
Description
The exporter now supports interleaved data by using the dedicated
BufferAttributeinterface.