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

Can orphaned nodes affect the transforms of shared meshes? #1649

Closed
prideout opened this issue Aug 2, 2019 · 3 comments
Closed

Can orphaned nodes affect the transforms of shared meshes? #1649

prideout opened this issue Aug 2, 2019 · 3 comments

Comments

@prideout
Copy link

prideout commented Aug 2, 2019

We've seen glTF assets that define two parallel node hierarchies: one that is rooted into a scene, and one that does not belong to a scene. They both contain references to a single set of meshes. It appears that Cinema4D is exporting assets in this way to separate an "animation hierarchy" from a "modeling hierarchy".

More generally, if a given mesh is referenced by more than one node, does it take on the transform of all those nodes? In what order do the transforms compose together?

Somewhat related to #1358 and #1547.

@scurest
Copy link

scurest commented Aug 3, 2019

Every node with a mesh property creates a new instance of the mesh with the transform of that node. A mesh itself doesn't have a transform.

@prideout
Copy link
Author

prideout commented Aug 3, 2019

Is it an error for a node to exist that is never referenced by any scene hierarchies?

@scurest
Copy link

scurest commented Aug 3, 2019

No, there do not even have to be any scenes in a file.

@prideout prideout closed this as completed Sep 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants