Hi fellow tyflow magicians
Perhaps any of you could help shed some light on this subject.
In our current scene we are birthing particles using the 'birth objects' operator. The naming of the objects in the scene is relevant, so for instance 'object_1, object_2'...etc. We need to use the alembic exporter to export the particle for use in another software package, however the naming should carry over. So instead of churning out objects named 'tyflow_node_###' or 'mesh_###' we need the naming to remain consistent with the original 'object_1, object_2' naming convention.
Does any of you know if this can be done without scripting?
Thanks in advance!
Tim
Perhaps any of you could help shed some light on this subject.
In our current scene we are birthing particles using the 'birth objects' operator. The naming of the objects in the scene is relevant, so for instance 'object_1, object_2'...etc. We need to use the alembic exporter to export the particle for use in another software package, however the naming should carry over. So instead of churning out objects named 'tyflow_node_###' or 'mesh_###' we need the naming to remain consistent with the original 'object_1, object_2' naming convention.
Does any of you know if this can be done without scripting?
Thanks in advance!
Tim