Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The "RealFlowFileUpdate" operator updates position, speed and other information about custom channels for all particles generated by the "RealFlowFileBirth" operator. It is an optional operator, meaning that if you are routing particles to another container (event) and you do not need to keep the particle information (position, speed etc) synchronized with RealFlow files, you do not have to use a RealFlow File Update operator in that container. Simply Display or Delete them as shown below.

 


Workflow when routed particles are deleted.


When routing RealFlow particle information to another PFlow container (event), if you want to keep particle information synchronized with the RealFlow files, you need to place another "RealFlowFileUpdate" operator in that container:

 

Workflow when routed particles are updated.


The "RealFlowFileUpdate" operator also acts like a garbage collector for every PFlow event container it is placed in. Its role is to check for dead particles by comparing its current particle IDs with the particle IDs stored in the current RealFlow BIN frame file. If it finds any dead particles, it will mark and send them to a "RealFlowDeathTest" operator in order to be routed to another container event. From there they can be deleted from PFlow if necessary.

  • "RealFlow Channels": MAXScript PFlow operators can access particle attributes which are computed by RealFlow like viscosity, density etc.

 

RealFlow File Update operator settings.


These attributes are shown in the custom data channels available in PFlow particle containers. The custom data channels can store less data than RealFlow produces, so users must select which particle attributes they want to use. Each attribute will use up a certain number of value slots of the available space, as follows:

...


The names "ticksPerFrame" and "frameRate" are built-in MAXScript "variables.plugin"

 

"RealFlowFileUpdate" Operator and MAXScript

The following attributes are exported to MAXScript:

...

The Ids for the “Channels” parameter can be combined with bitwise "OR" from MAXScript.

 

RealFlowFileBirth and RealFlowFileUpdate operator have animatable parameters.