Skip to content
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

"Animation channel cannot target TRS properties of node with defined matrix." Question #62

Closed
MilosBulat opened this issue Jan 26, 2018 · 4 comments
Labels

Comments

@MilosBulat
Copy link

Hi Khronos team,

If glTF file with an animated node is used in glTF previewers that don't support animation that node will be rendered in the default scene position.
Assuming this limitation was added to optimize glTF file size, is there a design strategy in glTF development for file size and corner cases kinds of tradeoffs?

Thanks,
Miloš

@lexaknyazev
Copy link
Member

If glTF file with an animated node is used in glTF previewers that don't support animation that node will be rendered in the default scene position.

Animated node can still have TRS properties defined. The limitation refers only to node.matrix property.

@MilosBulat
Copy link
Author

Hm, that sounds strange. Why is TRS property allowed and matrix property not?

@lexaknyazev
Copy link
Member

Please see KhronosGroup/glTF#892 and KhronosGroup/glTF#845 for some background on this.

@MilosBulat
Copy link
Author

Thanks @lexaknyazev that answers my question. :)

Best,
Miloš

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants