+- 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: Questions about tyCache and Cloth (/thread-4839.html)
Questions about tyCache and Cloth - Findus - 06-21-2025
Hi,
exporting a tyCache can preserve some properties, but it can't preserve Operators like Object Bind, correct? Basically, it just saves the movement of the particles, not what makes them move.
And the Playback Cache can't be saved, so I'll have to recalculate that each time I open the file, no way around it?
Is there any way how I could save the initial state of a cloth animation (after it has settled) without having to recalculate it each time I open the file, but still have all the operators, local stiffness settings etc.?
The only way I can think of right now is to copy the event(s), just load in the cashed state at the beginning (in a worst case scenario a mesh) and maybe do something with Flow Update.
When I use a Birth-Flow and set my 1-frame cache as a source (clamped to the frame in question), I somehow get double particles when I add a Cloth Bind (or rather Cloth Bind adds its own, bound particles, probably). That also happens when I untick "Particles" in the "Enable Cache Elements"section of the tyCache object. Unchecking "deforming meshes" makes the mesh go away, on the other hand.
RE: Questions about tyCache and Cloth - d4rk3lf - 06-21-2025
I usually do this by just doing snapshoot of the TyFlow once the cloth settles.
Then I import that new object in new TyFlow via birth object... and then I just copy paste my cloth bind operator, and other operators I need from the first flow, and I disable first flow.
But maybe there is a better way.
RE: Questions about tyCache and Cloth - Findus - 06-21-2025
Thanks a lot for your reply!
Using a cache (even for just one frame or "state") would have the advantage of not having to reassign a new snapshot mesh after changes (still would have to export, though). But I'll definitely consider snapshot as an option.
Would you consider the Birth Flow bringing in particles even when particles are deactivated in the tyCache object (Enable Cache Elements section) a bug? Or is this something to be expected?
RE: Questions about tyCache and Cloth - Findus - 06-21-2025
Looks like I can get rid of the particles by ticking "Cull if no shape assigned" in the tyCache object. I still feel like unticking particles in "Enable cache elements" should do the same.
RE: Questions about tyCache and Cloth - d4rk3lf - 06-21-2025
Well, the most straight-forward option for me would be, if birth flow could just inherit cloth mesh from refenced TyFlow.
It can inherit particles, but it won't inherit skinned cloth bind mesh.... and I don't know if there's a way to "rebuild it".
So, I would avoid Tycashe for this (as I said instead, it's much simpler to just snapshoot when cloth settles... then to create tycache... save it on disk... import it... etc.. etc)
I am using birth flow all the time when dealing with RGB Sims, and it saves me a lot of time on not having to calculate fractures all the time, or if I want to start from certain frame (or even if I just want to "post simulation" delete some fragments).
It's perfect for this.. only if it could inherit cloth mesh from referenced TyFlow.
But I am not sure how hard for Tyson would be to implement that.