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 importing any .dae or .gltf file exported using Blender's (2.90) built-in exporters, the animations don't work for -col/-colonly objects,
The reason appears to be quite simple: the importer drops the -col and -colonly suffix from the node names, but the animation tracks are referring to (non-existing) nodes with -col and -colonly suffix.
(Side note: when exporting gltf with Blender 2.90, "Group by NLA track" needs to be checked off, otherwise, only one of the existing tracks appear in theAnimationPlayer node, possibly a separate issue for gltf importer)
The text was updated successfully, but these errors were encountered:
I think the node names can be fixed in this loop. At first glance, it seems one can use _fixstr() on the path, but it actually only works for a single node name. It also requires a specific suffix.
I current don't have time to work on this, but a few possible ways I see this can be fixed:
A generalization of _fixstr() that works for a full path, and scans for all possible suffixes could be made & used?
It is possible to avoid renames that drop suffixes, that would fix the problem
Keep track of all _fixstr() changes in a hashmap, and do the animation renaming using that hashmap after all renames are completed
When importing any .dae or .gltf file exported using Blender's (2.90) built-in exporters, the animations don't work for -col/-colonly objects,
The reason appears to be quite simple: the importer drops the -col and -colonly suffix from the node names, but the animation tracks are referring to (non-existing) nodes with -col and -colonly suffix.
(Side note: when exporting gltf with Blender 2.90, "Group by NLA track" needs to be checked off, otherwise, only one of the existing tracks appear in theAnimationPlayer node, possibly a separate issue for gltf importer)
The text was updated successfully, but these errors were encountered: