As a small incentive, let me add after some additional research:
This approach is similar to how Houdini handles particle simulations, by using attributes and groups, allowing for multiple conditions and effects to be applied within a single network at the same time, without need to branching.
And one more example came to my mind:
The strengths of node based workflows are their actually flexibilty, as long as you can connect things freely with each other:
If we look at Nuke, also node-based:
Any "Alpha" image can be plugged everywhere you want.
You can even do even mask operations (considering time, movement, intersection/subtraction/addition) in a separate network. This is non-destructive, flexible and modular.
The smartest and clearest approach for Tyflow would be to have a "surface test birth operator" for Surface Tests geometries in a separated event.
And the output can be connected as a "volume mask" into any operator in any event when you enable the surface test condition for this operator.
So you can sort all your "surface test" volumes nicely at one spot in the node graph, easy to check and adjust there, and connect them to to any operator you need to limit.
Sending particles to a new event makes only sense, if everything changes for them, if a completely new situation should happen.
But not for "art-directed" adjustments in the same setup.
This approach is similar to how Houdini handles particle simulations, by using attributes and groups, allowing for multiple conditions and effects to be applied within a single network at the same time, without need to branching.
And one more example came to my mind:
The strengths of node based workflows are their actually flexibilty, as long as you can connect things freely with each other:
If we look at Nuke, also node-based:
Any "Alpha" image can be plugged everywhere you want.
You can even do even mask operations (considering time, movement, intersection/subtraction/addition) in a separate network. This is non-destructive, flexible and modular.
The smartest and clearest approach for Tyflow would be to have a "surface test birth operator" for Surface Tests geometries in a separated event.
And the output can be connected as a "volume mask" into any operator in any event when you enable the surface test condition for this operator.
So you can sort all your "surface test" volumes nicely at one spot in the node graph, easy to check and adjust there, and connect them to to any operator you need to limit.
Sending particles to a new event makes only sense, if everything changes for them, if a completely new situation should happen.
But not for "art-directed" adjustments in the same setup.