Timing does not work in Flow Update.
#1
Happy New Year. I wish tyFlow continued growth in 2026 and good fortune to the production staff.

Now, regarding the Flow Update, even after changing the Timing (On Event Entry, continue) , I still can't control the operator's behavior. Is this by design?
Specifically, even if you change the Timing, the operator will always continue to function. You cannot use Timing to turn it off.

While I can simulate turning it On/Off by keyframing the Channels percentage, it would still be more convenient if I could control it directly via Timing.
  Reply
#2
You need to be much more specific about what the issue is, as I don't see any issues with the timing controls in that operator.
  Reply
#3
Even If Changing FlowUpdate's [Timing] from [Continue] to another setting, It will always cause FlowUpdate to function.
In other words, you cannot make it follow the cache or stop it from doing so.

This is simply a flow where I added gravity using Force to the PhysX preset flow.

https://i.gyazo.com/b089f9c17153ea0e3ce4...34b566.mp4

I cached it. After turning gravity off, I used FlowUpdate to make the cache follow the movement.
Even if you change the FlowUpdate Timing in the child state from Continue to On Event Entry or Frame-based, FlowUpdate always functions.
You cannot stop it for a specified period.
  Reply
#4
You're using Flow Update but also have PhysX enabled, which will ultimately override what Flow Update does. This explains the behavior you're seeing. The timing settings of Flow Update work fine, but since your particles are still PhysX enabled (even with Flow Update on), they will still fall/collide the same way (making it seem as though Flow Update is doing it, even though it's not). Also you disabled your Force operator, but PhysX has its own gravity (PhysX rollout of a tyFlow object) - so you haven't necessarily disabled gravity fully with just the Force operator off.

Flow Update should be used in combination with Birth Flow, if you want to import a tyCache into a flow. Put them in their own even to avoid confusion.
  Reply
#5
Sorry, in this tyFlow, Default gravity was turned off.
Besides Force, even if you turn off PhysX, FlowUpdate will still function regardless of Timing.
https://i.gyazo.com/508b16e90f36dbdc7fb5...42d738.mp4
I think this is strange, and I thought it would be convenient if it could be controlled by Timing.
But if this is the specification, I'll accept it.

I do know how to combine Birth Flow and Flow Update.
But what about flows that include things like PhysX Bind or Object Bind (like ropes)?
It's quite a hassle to recreate similar bind states on particles created with Birth Flow.
So it's simpler to just transplant the position and rotation of particles from a specific frame in the cache.
That's why I wanted to use Flow Update alone for just one frame to recreate the state.
But Timing doesn't behave as I expected; it keeps running continuously.
  Reply
#6
Can you post the file, please.
  Reply
#7
This simply adds force and flow update to the PhysX preset flow.


Attached Files
.zip   simplePhysx.zip (Size: 40.17 KB / Downloads: 129)
  Reply
#8
Ok great, thank you for the file - that explains why I could not reproduce the issue, as it's a bug that only occurs when using Flow Update on a tyCache, rather than another tyFlow object.

It will be fixed in the next build. Meanwhile, you can simulate timing on the operator by having it in its own event and moving particles in/out of the event during the interval when you want them to be controlled by the operator.
  Reply
#9
(01-13-2026, 03:21 AM)tyFlow Wrote: Ok great, thank you for the file - that explains why I could not reproduce the issue, as it's a bug that only occurs when using Flow Update on a tyCache, rather than another tyFlow object.

It will be fixed in the next build. Meanwhile, you can simulate timing on the operator by having it in its own event and moving particles in/out of the event during the interval when you want them to be controlled by the operator.

Thank you. I see, it seems there was a difference in how we envisioned using it.

Next time, I'll attach the max file no matter how simple the scene is. I'm sorry for spending your time.
  Reply


Forum Jump: