fbx export: path to body different than in fusion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hello,
This is one for the devs maybe.
Id like to map some data in fusion to an fbx export from the file.
But there is a mismatch in the naming of how the fbx stores the body vs what it looks like in fusion.
i wrote a bit of python to give me the hierarchy/namespace that is similar to that of the fbx.
fusion path to body:
LEG v1/KNEE v1:1/Big Drum Assembly:1/Crank:1/Body4
fbx path to body:
LEG v1/KNEE v1:1/KNEE v1/Big Drum Assembly:1/Big Drum Assembly/Crank:1/Crank/Body4
Can someone confirm what the rule is for these fbx paths?
Am i safe to assume that the root & body names are the only parts of the fbx path that do not get name.split(':') extra item in the path?
Cheers
Kym