bones are renamed about daeblend HOT 2 CLOSED

I was looking at wrong field

from daeblend.

It puts the node names in the "skin" controller as a "Name_array" which are just as they are found in blender. But that's just the rest position (inverted matrices), the pose positions is then defined as a node tree and referenced with "skeleton". If there's a name collision in the node tree then it will generate a unique id with a number on the end. It's all very complicated. I found that DAE loaders interpret the format in wildly different ways so DAE is extremely hard to work with. And I found that it most cases the intended use is a JS library to read it. Like Three.JS. Which means it makes more sense just to export from Blender in JSON format directly. Maybe there's a good JS Blender exporter out there.

from daeblend.