4u2ges (6/2/2024)
I meant to ask this for a long time...
We have a button "Export Accessory" in CC Pipeline, but it exports materials "traditional" fbx way without pipeline with a lot of missing textures.
It would have been a great help to add "Convert to Accessory" function.
The way I see it, you select multiple objects and click that button. At this point a CC_Base_Hip bone is getting extruded and named after respective object.
Then object is getting bound to character Armature, vertex group is created (named after extruded bone) and mesh vertices acquire 100% influence from that bone.
Once the character exported from Blender and imported to CC with pipeline, those objects are recognized as "Accessories".
The advantage of this method (as oppose to "Export Accessory") is, that if you import objects fully textured (like from DAZ, USDZ, ..etc) or texture them in Blender,
they import to CC 1:1 with all maps properly applied.
This is how I currently do it:
https://forum.reallusion.com/FindPost546499.aspx I was a bit lazy and only attached as a cloth without making bone for the accessory, but the idea is the same.
I saw today in another thread the Utopia scene exported to Blender from DAZ with Diffeo by AutoDidact.
I did the same thing but went further and exported the scene to CC > iCLone with pipeline with the method above.
(There were too may objects to manually attach them to a character so I merged them all first).
Came out with about 99% accuracy, I did minor tweaks, added a few iClone trees and lights.
...
I guess, you understand where I am going with this
;)
We eventually need a full scene pipeline from Blender to iClone/CC without the need to use a character as a transport.
It should not be difficult I think as most routines for materials/textures binding are already in place.
Uh oh, props. Time to run and hide... Props are a nightmare to deal with. They're a mixture of armature and pose, sometimes directly parented to bones, other times skinned and thoroughly confusing.
But it's interesting timing, as this is exactly where I am at now with the Datalink.
I've figured out (I think) what CC/iClone sends to Blender as props and how to connect the two and that was confusing enough with all the endless bone name duplication. But sending props back to CC/iClone and maintaining the connection is a whole new level of confusing which I have yet to figure out as CC/iClone change the internal structure when they import props, and they change it again when they export it back to Blender...
However, just sending props back is relatively simple for simple structures: i.e. single armatures or a collection of meshes and empties, which I've streamlined into the datalink:
More complicated structures with nested armatures will take more figuring out and will be dependent on correctly ID'ing the bones/transforms on
both sides to accurately reconstruct the parenting and sub prop layout.
Worst case scenario is merging the whole scene (or partial scene) into one large armature based structure and sending it back as a single prop. That should work and is the next step for me.