tyFlow Forum
Naming rules for export objects - Printable Version

+- tyFlow Forum (https://forum.tyflow.com)
+-- Forum: tyFlow Discussion (https://forum.tyflow.com/forum-1.html)
+--- Forum: General Discussion (https://forum.tyflow.com/forum-2.html)
+--- Thread: Naming rules for export objects (/thread-3364.html)



Naming rules for export objects - walterlee - 10-15-2022

I face fractured a simple plane in tyflow and export them as objects,the names of objects are not arranged according to their positions. How to name exported particles in order of position?

What I get:
[Image: gpQkTAXL_o.jpg]
What I want:
[Image: UFjmUkZL_o.jpg]


RE: Naming rules for export objects - tyFlow - 10-17-2022

Is variation set to 0 in your Face Fracture operator?

Faces won't be extracted in order unless faces is set to 1 and variation is set to 0.


RE: Naming rules for export objects - walterlee - 10-17-2022

(10-17-2022, 05:36 PM)tyFlow Wrote: Is variation set to 0 in your Face Fracture operator?

Faces won't be extracted in order unless faces is set to 1 and variation is set to 0.

variation has been set to 0,and I succeeded to extract all the faces,
I want the name of the first  extracted face on the left of the first row is "xxx_ 001", the second extracted face on the left of the first row is "xxx_ 002"……
Is there a way to naming the extracted faces according to their position.


RE: Naming rules for export objects - tyFlow - 10-19-2022

Oh I see the issue...you're on an older BETA build.

The option to disable random ordering was added to a more recent build (v1.009).


RE: Naming rules for export objects - walterlee - 10-19-2022

(10-19-2022, 12:56 AM)tyFlow Wrote: Oh I see the issue...you're on an older BETA build.

The option to disable random ordering was added to a more recent build (v1.009).

I tested the v1.011 vesrsion,still not get what I want,Is there anything wrong with my  process:





RE: Naming rules for export objects - tyFlow - 10-19-2022

I see...hmm....seems like an Export Particles operator limitation now that I think about it.

The Face Fracture operator itself is fracturing things in order, correctly, when randomization is disabled in the latest builds...but the Export Particles operator is not keeping the particles sorted.

Luckily there is a workaround...the Export Particles operator has a MAXScript option that runs on particles after they are exported. You can use that to rename each object based on a custom float value - in this case you can assign their ID as a custom float and using the MAXScript option allows you to rename the corresponding object with that ID.

I've attached a file showing how it's done....just click the export button in the Export Particles operator and you'll see the objects are exported in order: "particle_1", "particle_2", etc, from topleft to bottom right.

You can see the script used in the "Objects MAXScript" rollout of the Export Particles operator. The id values are assigned in the Custom Properties operator.


RE: Naming rules for export objects - walterlee - 10-19-2022

(10-19-2022, 03:15 PM)tyFlow Wrote: I see...hmm....seems like an Export Particles operator limitation now that I think about it.

The Face Fracture operator itself is fracturing things in order, correctly, when randomization is disabled in the latest builds...but the Export Particles operator is not keeping the particles sorted.

Luckily there is a workaround...the Export Particles operator has a MAXScript option that runs on particles after they are exported. You can use that to rename each object based on a custom float value - in this case you can assign their ID as a custom float and using the MAXScript option allows you to rename the corresponding object with that ID.

I've attached a file showing how it's done....just click the export button in the Export Particles operator and you'll see the objects are exported in order: "particle_1", "particle_2", etc, from topleft to bottom right.

You can see the script used in the "Objects MAXScript" rollout of the Export Particles operator. The id values are assigned in the Custom Properties operator.
This method works. Thank you very much!