You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When loading a GLTF/GLB file containing nodes with matrix transforms, the matrix data appears to be converted into simple translations, losing rotation and scale information
.
Steps to reproduce:
Create a GLTF file with a node containing a 4x4 transformation matrix
Load the file using tinygltf
Examine the node data after loading
Node matrix should be preserved as-is in node.matrix
No automatic conversion to translation/rotation/scale components
This conversion breaks complex transformations that can't be accurately decomposed into TRS components. Is there a way to preserve the original matrix data? If not, could this be added as an option?
Environment:
tinygltf
Platform: Windows
Compiler: MSVC
Let me know if you'd like me to modify or add any details to the issue.
The text was updated successfully, but these errors were encountered:
When loading a GLTF/GLB file containing nodes with matrix transforms, the matrix data appears to be converted into simple translations, losing rotation and scale information
.
Steps to reproduce:
Create a GLTF file with a node containing a 4x4 transformation matrix
Load the file using tinygltf
Examine the node data after loading
Example GLTF node:
After loading, the node.matrix array is empty (size 0), and instead the transform has been converted to a simple translation:
Expected behavior:
Node matrix should be preserved as-is in node.matrix
No automatic conversion to translation/rotation/scale components
This conversion breaks complex transformations that can't be accurately decomposed into TRS components. Is there a way to preserve the original matrix data? If not, could this be added as an option?
Environment:
tinygltf
Platform: Windows
Compiler: MSVC
Let me know if you'd like me to modify or add any details to the issue.
The text was updated successfully, but these errors were encountered: