-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal pull transforms and bones from accessor (partially possible through extensions) #462
Comments
Thanks for the input, @ParticlePeter. Can you please provide a minimal JSON example? |
Yes, will do, need some time for this. Would be a cube mesh transformed by three matrices enough? |
Sure, thanks! |
@lexaknyazev any thoughts on this? |
Sorry that the example never reached this place, it actually did in proposal/issue #889 which is an evolution of this one here. The flat_nodes_proposal.zip demonstrates the same concept but via spec changes. Only addition would be that a node can have either transformation data or reference the data via accessor. In the case of global transforms meshes could directly source their data from accessors. |
This is something we can consider for the next major glTF revision, but we are not currently actively discussing this. |
Motivation: Looking at glTf from the OpneGL standpoint, in respect to instanced drawing and MultiDrawInderect, its nice to have (a huge amount of) transforms available as a binary chunk, directly upload-able to a TBO/UBO/SSBO.
Changes possible via extension:
When local transformation is required (possible via extension):
To evaluate the hierarchy:
Required (minimal) changes to the Spec, supply alternatives via extensions (accessor and index):
Interested in such an extension? Draft and example files can follow.
The text was updated successfully, but these errors were encountered: