Julien Duroure

I just pushed a fix on blender side. You should be able to test with next build (from April 18th): https://builder.blender.org/download/

Hello, Blender does manage hierarchy during glTF export (or please open a bug report with your test case). I am talking here about parent/child hierarchy. Collection is not part of...

Not that simple. Seems > bpy.data.objects['Cube'].vertex_groups == bpy.data.objects['Cube.001'].vertex_groups returns False, even if you instanciate Cube.001 from Cube (Alt+D)

> But the exporter only cares about the list of names, and those do appear to be shared. Current master is not using name for vertex group, as this is...

* Materials can be retrieved from mesh, but vertex group can't, so we can pass only a tuple of vertex group names * Using name leads to errors (even for...

> Materials cannot be retrieved from the mesh because they can be overridden at the object level. That is why they are passed down to begin with. What I mean...

After merge of #1378, VertexGroups are no more part of the cache key. Setting vertex_groups to None before calling gather_mesh should now be removed, not more relevant

Confirmed that currently, we don't manage multiple action on same track Not sure how this should work if we want to implement it : * Merging/baking in a single one...

@mattrossman What you describes is not implemented for now

Yes, I confirm that baking for bones are already in place. I think the enhancement can be easily be done by exporting actions as usual, and then concatenate actions (keeping...