04-17-2019, 06:14 PM
Custom properties are local to each particle, yes.
Eventually I actually plan on adding a vehicle actor helper to tyFlow, to achieve exactly what you're trying to do.
As for visual data flows...I personally found the opposite to be true. I always thought PFlow's data op was incredibly clunky...so many nodes required to achieve simple things like modifying a matrix row or swapping vector coordinates, etc....massive trees of nodes impossible to parse at a glance that could be translated into a couple lines of code. The only reason I used data ops is because pflow's script operator was slow and limited. Hence my focus on tyFlow's script operator instead.
Eventually I actually plan on adding a vehicle actor helper to tyFlow, to achieve exactly what you're trying to do.
As for visual data flows...I personally found the opposite to be true. I always thought PFlow's data op was incredibly clunky...so many nodes required to achieve simple things like modifying a matrix row or swapping vector coordinates, etc....massive trees of nodes impossible to parse at a glance that could be translated into a couple lines of code. The only reason I used data ops is because pflow's script operator was slow and limited. Hence my focus on tyFlow's script operator instead.