| On this page | |
| Since | 14.0 |
The SOP Solver DOP lets the DOP simulation use a SOP Network or chain
of SOPs to evolve an object’s geometry over time. At each timestep, the
SOP specified in the SOP Path parameter is set up with a number of
global parameters accessible with the stamp or stamps expression
function. Since these global parameters are modified at each timestep,
any SOPs that feed into the output SOP are forced to recook.
The available global parameters are:
|
|
Current simulation time being solved for. |
|
|
Length of timestep. |
|
|
The object identifier for the object being solved. |
|
|
The name of the object being solved. |
|
|
This is the full path to the DOP Network that is being solved. |
|
|
This is the name of the data on the object that is to be solved by the SOP Solver. |
|
|
This is the full path to the piece of data within the DOP Network
that is being solved by the SOP Solver. It is equivalent to |
By using an expression like stamps("../OUT", "DATAPATH", "../.:objname/Geometry") in an 
Object Merge SOP, the output of the previous timestep can be used as the starting point for the next timestep within the SOP Network.
The SOP Solver is itself a SOP network. This means that the SOP Path can point to itself, using '.', to cook its contents as the SOP solving network. The default SOP Solver will contain an DOP import already set up with the appropriate stamp expression, and a Impacts network setup with the usual need to grab the impact data for an RBD object.
When a SOP Solver is applied to multiple objects, each object is solved individually in a separate pass. Likewise, when you dive in and view the SOP network you are not seeing the DOP solve, but instead the network as a normal SOP network. This usually results in the same thing as the default stamps are setup to behave the same in DOP and SOP modes.
Use External SOP
Since this node is itself a SOP network, if this toggle is not set the SOP network used for solving is the contained network.
SOP Path
Points to the SOP that is accessed on each timestep.
The global parameter listed above are set on this SOP node, so this is the
node that should be used as the first parameter in stamp or stamps expressions to access this information.
Data Name
The name of the Geometry data on the simulation object that should be processed by this solver.
Usually this will be the
main geometry for an object, named Geometry, but this is not
required.
The type of the data should be Geometry, Scalar Field, Vector
Field, or Matrix Field. If it is Geometry, the output of the
SOP network is made the new data value. If it is a field
type, the first volumes (regardless of name) in the output
will be sampled to become the new field values. The fields
will not change size or resolution.
Invoke Compiled Block
To run a SOP solver, a copy of the geometry has to be made to ensure the SOPs can still read the original, unmodified, geometry during the solve. This adds a considerable overhead to a SOP solver, however.
If the SOP Path refers to a compiled block, or an Output SOP connected directly to a compiled block, the block can be directly invoked. Doing so allows the copy to be avoided and instead the geometry manipulated in-place.
The compile block’s output becomes the new version of the solved data. An input named “data” will be given the original version solved data.
Note
This only works with processing Geometry, not with fields.
Primary Input
Controls which input gets the original version of the solved data. By default this is “data”.
Note
If you try to load this data using an Object Merge or 
DOP Import, you will get an empty geometry as it has been removed from
the DOP simulation so it can be solved in place.
Num Extra Inputs
It is possible to bind additional inputs to the invoked compile block. If the compile block has a named input matching one of these, it will gain the corresponding geometry when invoked. The normal rules to transform DOP Data into Geometry are performed, so Scalar Fields will be imported as Volumes, etc.
Input Name
The name of the input to bind to. The compile block begin with the matching name will be wired to this data.
Source
Where to gain the geometry from.
This Object’s Data
Data attached to the currently solved object will be used.
Note
You cannot refer to the data being currently solved as it is being solved in-place. Specifically, the data specified by the Data Name parameter and any extra output is not available.
Object’s Data
Data attached to another object in the simulation.
Relationship’s Data (Packed)
A relationship defines a link between this object and many other objects. This brings in all the other objects that match that relationship. The resulting geometry consists of many packed primitives, one per object, that contain the respective data.
Additional primitive attributes are present on each packed primitive to describe the object
objid
Unique integer id of the object.
objname
The name of the object, note DOPs allows duplicate names.
bounce
The Bounce Physical Parameter.
bounceforward
The Bounce Forward Physical Parameter.
friction
The Friction Physical Parameter.
dynamicfriction
The Dynamic Friction Physical Parameter.
temperature
The Temperature Physical Parameter.
pscale
The Thickness of the Surface Collision Parameter.
Solve Metadata
An empty geometry with detail attributes that provide the current status of the solver. This geometry will also contain the variables defined in Stamps.
simtime
Current simulation time.
startsimtime
Simulation time of the start of the current solve step.
endsimtime
Simulation time of the end of the current solve step.
time
Current Houdini time.
timestep
Duration of current solve step.
objid
Unique object id of object currently being solved by this sop solver. This doesn’t exist when solving relationships.
objname
Current name of the solving object. May be duplicate in DOPs. Will be present for relationships.
dopnet
Path of the DOP network currently solving.
datapath
Full path to geometry this sop solver is being asked to process.
dataname
Name of the data this sop solver is being asked to process.
Object Name
Which object to fetch data from.
Relationship
The relationship to use to determine which objects to fetch.
Collider Labels
Objects can have a collider label to provide a hint of how the user wants them to be used by various solvers. The Use Solver Default, Use Volume Collisions and Use Surface Collisions options of the Static Object are such an example. This lets you filter the objects found in a relationship collision by a label in addition to by the relationship type.
Data Name
What data on the object to acquire and convert to geometry.
Fetch Time
When to fetch the data. A SOP Solver solves a window of time, so it may be necessary to get the data either at the start or end of that window.
Num Extra Outputs
It is possible to define a compiled sop network with more than one output node. This is done with the Primary Path. In order to process multiple geometry in-place, these extra outputs can be specified here.
Input Name
The name of the Block Begin Compile SOP that will receive the original version of this geometry.
Data Name
The data on this object to solve with this output.
SOP Path
The path to the compile end node whose results will replace the data. Note this is relative to this node, so often can simply be the name of the node.
SOP Output is in Simulation Space
When extracting the geometry from the SOP at each timestep, turning on this parameter will cause the SOP Solver to transform the geometry from world space to local object space.
NOTE:
When data is pulled into SOP using the Object Merge
SOP, it is extracted into world space, so
this option will often need to be turned on. Alternatively a DOP
Transform SOP can be used at the SOP level to change the geometry
from one space to another, rather than using this option.
Solve Objects on Creation Frame
Causes the SOP Solver to operate on an object even on the frame in which the object enters the simulation.
If you want to bring an object into a simulation and not modify it on the initial frame, turn this option off.
Stamps
Extra variables can be stamped here and accessed from within the SOP network
with stamp expressions. For example, if you stamp a variable called FOO,
its value can be queried with stamp("..", "FOO", -1) for a Float
variable or stamps("..", "FOO", "") if the variable is of type String.
Note
When used with compiled blocks, these variables are added to the extra Solve Metadata input as detail attributes.
Variable Name
Name of the variable to stamp; this is the identifier that would be used as
the second argument in a stamp or stamps expression.
Variable Type
Type of the variable to stamp. Float refers to a numeric value, and can
be accessed using the stamp expression function. String variables can
hold an arbitrary string of characters, and can be accessed using the
stamps expression function.
Float Value
The value to assign to the numeric variable. This value will be returned by
a relevant stamp expression from within the SOP network.
String Value
The value to assign to a string variable. This value will be returned by a
relevant stamps expression from within the SOP network.
Parameter Operations
Each data option parameter has an associated menu which specifies how that parameter operates.
Use Default
Use the value from the Default Operation menu.
Set Initial
Set the value of this parameter only when this data is created. On all subsequent timesteps, the value of this parameter is not altered. This is useful for setting up initial conditions like position and velocity.
Set Always
Always set the value of this parameter. This is useful when specific keyframed values are required over time. This could be used to keyframe the position of an object over time, or to cause the geometry from a SOP to be refetched at each timestep if the geometry is deforming.
You can also use this setting in
conjunction with the local variables for a parameter value to
modify a value over time. For example, in the X Position, an
expression like $tx + 0.1 would cause the object to
move 0.1 units to the right on each timestep.
Set Never
Do not ever set the value of this parameter. This option is most useful when using this node to modify an existing piece of data connected through the first input.
For example, an 
RBD State
DOP may want to animate just the mass of an
object, and nothing else. The Set Never option could be used
on all parameters except for Mass, which would use Set
Always.
Default Operation
For any parameters with their Operation menu set to Use Default, this parameter controls what operation is used.
This parameter has the same menu options and meanings as the Parameter Operations menus, but without the Use Default choice.
Make Objects Mutual Affectors
All objects connected to the first input of this node become mutual affectors.
This is equivalent to using an 
Affector
DOP to create an affector relationship between
* and * before connecting it to this node. This option makes it
convenient to have all objects feeding into a solver node affect
each other.
Group
When an object connector is attached to the first input of this node, this parameter can be used to choose a subset of those objects to be affected by this node.
Data Name
Indicates the name that should be used to attach the data to an object or other piece of data. If the Data Name contains a “/” (or several), that indicates traversing inside subdata.
For example, if the 
Fan Force DOP has the default Data Name
“Forces/Fan”. This attaches the data with the name “Fan” to an
existing piece of data named “Forces”. If no data named “Forces”
exists, a simple piece of container data is created to hold the
“Fan” subdata.
Different pieces of data have different requirements on what names should be used for them. Except in very rare situations, the default value should be used. Some exceptions are described with particular pieces of data or with solvers that make use of some particular type of data.
Unique Data Name
Turning on this parameter modifies the Data Name parameter value to ensure that the data created by this node is attached with a unique name so it will not overwrite any existing data.
With this parameter turned off, attaching two pieces of data with the same name will cause the second one to replace the first. There are situations where each type of behavior is desirable.
If an object
needs to have several Fan Forces blowing on it, it is
much easier to use the Unique Data Name feature to ensure that
each fan does not overwrite a previous fan rather than trying to
change the Data Name of each fan individually to avoid
conflicts.
On the other hand, if an object is known to have RBD
State data already attached to it, leaving this
option turned off will allow some new RBD State
data to overwrite the existing data.
Solver Per Object
The default behavior for solvers is to attach the exact same solver to all of the objects specified in the group. This allows the objects to be processed in a single pass by the solver, since the parameters are identical for each object.
However, some objects operate more logically on a single object at
a time. In these cases, one may want to use $OBJID expressions
to vary the solver parameters across the objects. Setting this
toggle will create a separate solver per object, allowing $OBJID
to vary as expected.
Setting this is also required if stamping the parameters with a Copy Data DOP.
All Inputs
Any microsolvers wired into these inputs will be executed prior to this node executing. The chain of nodes will thus be processed in a top-down manner.
First Output
The operation of this output depends on what inputs are connected to this node. If an object stream is input to this node, the output is also an object stream containing the same objects as the input (but with the data from this node attached).
If no object stream is
connected to this node, the output is a data output. This data
output can be connected to an 
Apply Data DOP,
or connected directly to a data input of another data node, to
attach the data from this node to an object or another piece of
data.
channelname
This DOP node defines a local variable for each channel and parameter on the Data Options page, with the same name as the channel. So for example, the node may have channels for Position (positionx, positiony, positionz) and a parameter for an object name (objectname).
Then there will also be local variables with the names positionx, positiony, positionz, and objectname. These variables will evaluate to the previous value for that parameter.
This previous value is always stored as part of the data attached to the object being processed. This is essentially a shortcut for a dopfield expression like:
dopfield($DOPNET, $OBJID, dataName, "Options", 0, channelname)
If the data does not already exist, then a value of zero or an empty string will be returned.
DATACT
This value is the simulation time (see variable ST) at which the current data was created. This value may not be the same as the current simulation time if this node is modifying existing data, rather than creating new data.
DATACF
This value is the simulation frame (see variable SF) at which the current data was created. This value may not be the same as the current simulation frame if this node is modifying existing data, rather than creating new data.
RELNAME
This value will be set only when data is being attached to a relationship (such as when Constraint Anchor DOP is connected to the second, third, of fourth inputs of a Constraint DOP).
In this case, this value is set to the name of the relationship to which the data is being attached.
RELOBJIDS
This value will be set only when data is being attached to a relationship (such as when Constraint Anchor DOP is connected to the second, third, of fourth inputs of a Constraint DOP).
In this case, this value is set to a string that is a space separated list of the object identifiers for all the Affected Objects of the relationship to which the data is being attached.
RELOBJNAMES
This value will be set only when data is being attached to a relationship (such as when Constraint Anchor DOP is connected to the second, third, of fourth inputs of a Constraint DOP).
In this case, this value is set to a string that is a space separated list of the names of all the Affected Objects of the relationship to which the data is being attached.
RELAFFOBJIDS
This value will be set only when data is being attached to a relationship (such as when Constraint Anchor DOP is connected to the second, third, of fourth inputs of a Constraint DOP).
In this case, this value is set to a string that is a space separated list of the object identifiers for all the Affector Objects of the relationship to which the data is being attached.
RELAFFOBJNAMES
This value will be set only when data is being attached to a relationship (such as when Constraint Anchor DOP is connected to the second, third, of fourth inputs of a Constraint DOP).
In this case, this value is set to a string that is a space separated list of the names of all the Affector Objects of the relationship to which the data is being attached.
ST
The simulation time for which the node is being evaluated.
Depending on the settings of the 
DOP Network
Offset Time and Scale Time parameters,
this value may not be equal to the current Houdini time
represented by the variable T.
ST is guaranteed to have a value of zero at the
start of a simulation, so when testing for the first timestep of a
simulation, it is best to use a test like $ST == 0, rather than
$T == 0 or $FF == 1.
SF
The simulation frame (or more accurately, the simulation time step number) for which the node is being evaluated.
Depending on the settings of the DOP Network parameters,
this value may not be equal to the current Houdini frame number
represented by the variable F. Instead, it is equal to
the simulation time (ST) divided by the simulation timestep size
(TIMESTEP).
TIMESTEP
The size of a simulation timestep. This value is useful for scaling values that are expressed in units per second, but are applied on each timestep.
SFPS
The inverse of the TIMESTEP value. It is the number of timesteps per second of simulation time.
SNOBJ
The number of objects in the simulation. For nodes that
create objects such as the 
Empty Object DOP,
SNOBJ increases for each object that is evaluated.
A good way to guarantee unique object names is to use an expression
like object_$SNOBJ.
NOBJ
The number of objects that are evaluated by the current node during this timestep. This value is often different from SNOBJ, as many nodes do not process all the objects in a simulation.
NOBJ may return 0 if the node does not
process each object sequentially (such as the 
Group
DOP).
OBJ
The index of the specific object being processed by the node. This value always runs from zero to NOBJ-1 in a given timestep. It does not identify the current object within the simulation like OBJID or OBJNAME; it only identifies the object’s position in the current order of processing.
This value is useful for generating a
random number for each object, or simply splitting the objects into
two or more groups to be processed in different ways. This value
is -1 if the node does not process objects sequentially (such
as the Group DOP).
OBJID
The unique identifier for the object being processed. Every object is assigned an integer value that is unique among all objects in the simulation for all time. Even if an object is deleted, its identifier is never reused. This is very useful in situations where each object needs to be treated differently, for example, to produce a unique random number for each object.
This value is also the best way to look up information on an object using the dopfield expression function.
OBJID is -1 if the node does not process objects
sequentially (such as the Group DOP).
ALLOBJIDS
This string contains a space-separated list of the unique object identifiers for every object being processed by the current node.
ALLOBJNAMES
This string contains a space-separated list of the names of every object being processed by the current node.
OBJCT
The simulation time (see variable ST) at which the current object was created.
To check if an object was created
on the current timestep, the expression $ST == $OBJCT should
always be used.
This value is zero if the node does not process
objects sequentially (such as the Group DOP).
OBJCF
The simulation frame (see variable SF) at which the current object was created. It is equivalent to using the dopsttoframe expression on the OBJCT variable.
This value is zero if the node does not process objects
sequentially (such as the Group DOP).
OBJNAME
A string value containing the name of the object being processed.
Object names are not guaranteed to be unique within a simulation. However, if you name your objects carefully so that they are unique, the object name can be a much easier way to identify an object than the unique object identifier, OBJID.
The object name can
also be used to treat a number of similar objects (with the same
name) as a virtual group. If there are 20 objects named “myobject”,
specifying strcmp($OBJNAME, "myobject") == 0 in the activation field
of a DOP will cause that DOP to operate on only those 20 objects.
This value is the empty string if the node does not process objects
sequentially (such as the Group DOP).
DOPNET
A string value containing the full path of the current DOP network. This value is most useful in DOP subnet digital assets where you want to know the path to the DOP network that contains the node.
Note
Most dynamics nodes have local variables with the same names as the
node’s parameters. For example, in a 
Position DOP,
you could write the expression:
$tx + 0.1
…to make the object move 0.1 units along the X axis at each timestep.
DentingWithPops Example for SOP Solver dynamics node
This example combines a number of important DOPs concepts.
First, it uses both POP Solver and RBD Solver objects interacting with each other in a bidiretional manner. The RBD object affects the particles, and the particles affect the RBD object.
Second, the RBD object atually uses a multi-solver to combine an RBD Solver with a SOP Solver. The RBD Solver controls the motion of the overall object, while the SOP Solver performs the denting of the geometry.
Third, the SOP Solver extracts impact information from the RBD Solver to perform the denting. It extracts this information using DOP expression functions.
The end result is a simulation of a torus that is bombarded by a stream of particles. The particles bounce off the torus, and also cause the torus to move. In addition, each particle collision causes a slight denting of the torus.
VisualizeImpacts Example for SOP Solver dynamics node
An example that shows how you can visualize impact data in an RBD simulation by using a SOP Solver to add custom guide geometry to the RBD Objects.
This example has three toruses falling on a grid with green lines showing the position and magnitude of impacts. The force visualization is added as ancillary geometry data to the actual toruses, so the RBD Solver is entirely unaware of the effect. The SOP Solver could also be used as an independent SOP network to extract impact visualization from an RBD Object.
Marks a simulation object as active or passive.
Creates affector relationships between groups of objects.
Blends between a set of animation clips based on the agent’s turn rate.
Layers additional animation clips onto an agent.
Defines a target that an agent can turn its head to look at.
Adjusts the agent’s skeleton to look at a target.
Adapts the legs of an agent to conform to terrain and prevent the feet from sliding.
Project the agent/particle points onto the terrain
Defines an orientation that aligns an axis in object space with a second axis defined by the relative locations of two positional anchors.
Anchor: Object Point Group Position
Defines multiple points, specified by their number or group, on the given geometry of a simulation object.
Anchor: Object Point Group Rotation
Defines orientations based on multiple points on the given geometry of a simulation object.
Anchor: Object Point Id Position
Defines a position by looking at the position of a point on the geometry of a simulation object.
Anchor: Object Point Id Rotation
Defines an orientation by looking at a point on the geometry of a simulation object.
Anchor: Object Point Number Position
Defines a position by looking at the position of a point on the geometry of a simulation object.
Anchor: Object Point Number Rotation
Defines an orientation by looking at a point on the geometry of a simulation object.
Anchor: Object Primitive Position
Defines a position by looking at the position of a particular UV coordinate location on a primitive.
Defines a position by specifying a position in the space of some simulation object.
Defines an orientation by specifying a rotation in the space of some simulation object.
Anchor: Object Surface Position
Defines multiple attachment points on a polygonal surface of an object.
Defines a position by specifying a position in world space.
Defines an orientation by specifying a rotation in world space.
Attaches data to simulation objects or other data.
Creates relationships between simulation objects.
Attaches the appropriate data for Bullet Objects to an object.
Sets and configures a Bullet Dynamics solver.
Applies a uniform force to objects submerged in a fluid.
Attaches the appropriate data for Cloth Objects to an object.
Defines the mass properties.
Defines the physical material for a deformable surface.
Defines the internal cloth forces.
Creates a Cloth Object from SOP Geometry.
Defines the plasticity properties.
Constrains part of the boundary of a cloth object to the boundary of another cloth object.
Defines how cloth uses target.
Defines a way of resolving collisions involving a cloth object and DOPs objects with volumetric representations (RBD Objects, ground planes, etc.)
Constrains an object to remain a certain distance from the constraint, and limits the object’s rotation.
Constrains pairs of RBD objects together according to a polygon network.
Constraint Network Relationship
Defines a set of constraints based on geometry.
Constraint Network Visualization
Visualizes the constraints defined by constraint network geometry.
Creates multiple copies of the input data.
Sets and configures a Copy Data Solver.
Mimics the information set by the Copy Object DOP.
Defines a Crowd Fuzzy Logic
Creates a crowd object with required agent attributes to be used in the crowd simulation.
Updates agents according to their steer forces and animation clips.
Defines a Crowd State
Defines a transition between crowd states.
Defines a Crowd Trigger
Combines multiple crowd triggers to build a more complex trigger.
Adds a data only once to an object, regardless of number of wires.
Deletes both objects and data according to patterns.
Applies force and torque to objects that resists their current direction of motion.
Defines how the surrounding medium affects a soft body object.
Controls Embedded Geometry that can be deformed along with the simulated geometry in a finite element simulation.
Creates an Empty Data for holding custom information.
Creates an Empty Object.
Constrains a set of points on the surface of one FEM object to a set of points on the surface on another FEM object or a static object.
Constrains points of a solid object or a hybrid object to points of another DOP object.
Creates an FEM Hybrid Object from SOP Geometry.
Constrains regions of a solid object or a hybrid object to another solid or hybrid object.
Make a set of points on the surface of an FEM Object slide against the surface of another FEM Object or a Static Object.
Creates a simulated FEM solid from geometry.
Sets and configures a Finite Element solver.
Constrains an FEM object to a target trajectory using a hard constraint or soft constraint.
Attaches the appropriate data for Particle Fluid Objects to become a FLIP based fluid.
Evolves an object as a FLIP fluid object.
Applies forces on the objects as if a cone-shaped fan were acting on them.
Fetches a piece of data from a simulation object.
Applies forces to an object using some piece of geometry as a vector field.
Creates a vortex filament object from SOP Geometry.
Evolves vortex filament geometry over time.
Imports vortex filaments from a SOP network.
Saves and loads simulation objects to external files.
Finite Element Output Attributes
Allows a finite-element object to generate optional output attributes.
Attaches the appropriate data for Fluid Objects to an object.
Applies forces to resist the current motion of soft body objects relative to a fluid.
Attaches the appropriate data for Fluid Objects to an object.
A solver for Sign Distance Field (SDF) liquid simulations.
A microsolver that applies viscosity to a velocity field using an adaptive grid.
A microsolver that advects fields and geometry by a velocity field.
A microsolver that advects fields by a velocity field using OpenCL acceleration.
A microsolver that advects fields by a velocity field.
A microsolver that computes analytic property of fields.
A microsolver that swaps geometry attributes.
A microsolver that applies a force around an axis to a velocity field.
A microsolver that blends the density of two fields.
A microsolver that blurs fields.
A microsolver that determines the collision field between the fluid field and any affector objects.
Gas Build Collision Mask From Pieces
A microsolver that builds a collision field for fluid simulations from instanced pieces.
A microsolver that builds a mask out of positive areas of the source fields.
A microsolver that builds a mask for each voxel to show the presence or absence of relationships between objects.
A microsolver that calculates an adhoc buoyancy force and updates a velocity field.
A microsolver that performs general calculations on a pair of fields.
A microsolver that detects collisions between particles and geometry.
A microsolver that applies a combustion model to the simulation.
A microsolver that clips an SDF field with a convex hull.
A microsolver that adjusts an SDF according to surface markers.
A microsolver that computes the cross product of two vector fields.
A DOP node that creates forces generated from a curve.
A microsolver that scales down velocity, damping motion.
A microsolver that diffuses a field or point attribute.
A microsolver that dissipates a field.
Adds fine detail to a smoke simulation by applying disturbance forces to a velocity field.
A microsolver that runs once for each matching data.
A microsolver that embeds one fluid inside another.
A microsolver that enforces boundary conditions on a field.
A microsolver that equalizes the density of two fields.
A microsolver that equalizes the volume of two fields.
A microsolver that emits a DOP error.
A microsolver that evaluates the external DOPs forces for each point in a velocity field and updates the velocity field accordingly.
A microsolver that extrapolates a field’s value along an SDF.
A microsolver that creates a feathered mask out of a field.
A microsolver that calculates and applies feedback forces to collision geometry.
A data node that fetches the fields needed to embed one fluid in another.
Runs CVEX on a set of fields.
Runs CVEX on a set of fields.
A microsolver that copies the values of a field into a point attribute on geometry.
Filters spurious divergent modes that may survive pressure projection on a center-sampled velocity field.
A microsolver that defragments geometry.
A microsolver that creates a signed distance field out of geometry.
A micro solver that transfers meta data on simulation objects to and from geometry attributes.
Blends a set of SOP volumes into a set of new collision fields for the creation of a guided simulation.
A microsolver that copies Impact data onto point attributes.
Gas Integrate Shallow Water Equations
Integrates the shallow water equations.
A microsolver that applies forces to a particle fluid system.
A microsolver that repeatedly solves its inputs at different rates.
A microsolver that solves its subsolvers at a regular interval.
A microsolver that clamps a field within certain values.
A microsolver that keeps particles within a box.
A microsolver that combines multiple fields or attributes together.
A microsolver that adaptively sharpens a field.
A microsolver that looksup field values according to a position field.
A microsolver that rebuilds fields to match in size and resolution to a reference field.
A microsolver that arbitrary simulation data between multiple machines.
A microsolver that exchanges boundary data between multiple machines.
A microsolver that exchanges boundary data between multiple machines.
A microsolver that balances slices data between multiple machines.
A microsolver that exchanges boundary data between multiple machines.
Executes the provided kernel with the given parameters.
Uses OpenCL to perform boundary enforcement for fluid fields.
Uses OpenCL to import VDB data from source geometry into simulation fields.
A microsolver that counts the number of particles in each voxel of a field.
A microsolver that moves particles to lie along a certain isosurface of an SDF.
A microsolver that separates adjacent particles by adjusting their point positions..
A microsolver that copies a particle system’s point attribute into a field.
A microsolver that converts a particle system into a signed distance field.
A microsolver that removes the divergent components of a velocity field.
Gas Project Non Divergent Adaptive
A microsolver that removes the divergent components of a velocity field using an adaptive background grid to increase performance.
Gas Project Non Divergent Multigrid
A microsolver that removes the divergent components of a velocity field using a multi-grid method.
Gas Project Non Divergent Variational
A microsolver that removes the divergent components of a velocity field.
A microsolver that reduces a field to a single constant field .
A microsolver that reduces surrounding voxels to a single value.
A microsolver that reinitializes a signed distance field while preserving the zero isocontour.
A microsolver that repeatedly solves its input.
A microsolver that resets fields outside of the stenciled region.
A microsolver that changes the size of fields.
A microsolver that resizes a fluid to match simulating fluid bounds
A microsolver that initializes a rest field.
A microsolver that converts an SDF field to a Fog field.
A microsolver that computes the forces to treat the fluid simulation as sand rather than fluid.
A microsolver that creates, deletes and reseeds particles. Tailored to be used in a fluid solver.
A microsolver that seeds marker particles around the boundary of a surface.
A microsolver that seeds particles uniformly inside a surface.
Applies a Shredding Force to the velocity field specified.
A microsolver that computes slice numbers into an index field.
Adjusts a fluid velocity field to match collision velocities.
A microsolver that calculates the forces imparted by a strain field.
A microsolver that updates the strain field according to the current velocity field.
A microsolver that substeps input microsolvers.
A microsolver that snaps a surface onto a collision surface.
A microsolver that calculates a surface tension force proportional to the curvature of the surface field.
A microsolver that synchronizes transforms of simulation fields.
A microsolver that applies a force towards a target object.
Modifies the temperature of a FLIP over time.
Applies Turbulence to the specified velocity field.
Up-scales and/or modifies a smoke, fire, or liquid simulations.
Scales fluid velocity based on the fluid’s current speed or a control field.
A microsolver that reorients geometry according to motion of a velocity field.
A microsolver that applies viscosity to a velocity field.
A microsolver that seeds flip particles into a new volume region.
Remaps a field according to a ramp.
Applies a confinement force on specific bands of sampled energy.
Applies a vortex confinement force to a velocity field.
Applies a confinement force on specific bands of sampled energy.
A microsolver that applies forces to a velocity field or geometry according to vorticle geometry.
A DOP node that adds the appropriately formatted data to represent vorticles.
A DOP node that recycles vorticles by moving them to the opposite side of the fluid box when they leave.
A microsolver that performs a wavelet decomposition of a field.
A microsolver that applies a wind force.
Runs CVEX on geometry attributes.
Runs a VEX snippet to modify attribute values.
Applies a gravity-like force to objects.
Creates a ground plane suitable for RBD or cloth simulations.
Creates simulation object groups.
Defines a constraint relationship that must always be satisfied.
Attaches the appropriate data for Hybrid Objects to an object.
Stores filtered information about impacts on an RBD object. The shelf tool has no effect in the viewport, it just sets up nodes in the network to record the impact data.
Applies an impulse to an object.
Creates an index field.
Visualizes an index field.
Creates DOP Objects according to instance attributes
Marks a simulation object as intangible or tangible.
Stores the name of the scene level object source for this DOP object.
Apply forces on objects using a force field defined by metaballs.
Creates a matrix field.
Visualizes a matrix field.
Merges multiple streams of objects or data into a single stream.
Modifies or creates options on arbitrary data.
Defines an object’s position, orientation, linear velocity, and angular velocity.
Unified visualization of multiple fields.
A DOP that transfers arbitrary simulation data between multiple machines.
Does nothing.
Creates position information from an object’s transform.
Uses vortex filaments to move particles.
A POP node that uses velocity volumes to move particles.
A POP node that attracts particles to positions and geometry.
The POP equivalent of the Attribute Blur SOP.
A POP node that copies volume values into a particle attribute.
A POP node that resets the stopped attribute on particles, waking them up.
A POP node that applies a force around an axis.
A POP node that reacts to collisions.
A POP node that detects and reacts to collisions.
A POP node marks particles to ignore implicit collisions.
A POP node that colors particles.
A POP node that creates forces generated from a curve.
A POP node that creates incompressible velocity field generated from a curve.
A POP node that applies drag to particles.
A POP node that applies drag to the spin of particles.
A POP node that applies a conical fan wind to particles.
A POP node that creates a simple fireworks system.
A POP node that floats particles on the surface of a liquid simulation.
A POP node that applies a flocking algorithm to particles.
Controls local density by applying forces between nearby particles.
A POP node that applies forces to particles.
A POP node that applies sand grain interaction to particles.
A POP node that groups particles.
Compute hair separation force using a VDB volume approach.
A POP node that sets up the instancepath for particles.
A POP node that applies forces between particles.
A POP node that kills particles.
A POP node that limits particles.
A POP node that applies forces within the particle’s frame.
A POP solver that generates particles at a point.
A POP node makes a particle look at a point.
A POP node that creates a mask based on whether particles are occluded by geometry.
A POP node that applies forces according to metaballs.
Converts a regular particle system into a dynamic object capable of interacting correctly with other objects in the DOP environment.
A POP node that sets various common attributes on particles.
A POP node that sets attributes based on nearby particles.
A POP Node that generates particles from incoming particles.
A POP node that creates a spongy boundary.
A POP solver updates particles according to their velocities and forces.
A POP node that generates particles from geometry.
A POP node that sets the speed limits for particles.
A POP node that sets the spin of particles..
A POP node that uses the vorticity of velocity volumes to spin particles.
A POP node that sets the sprite display for particles.
Applies force to agents/particles to align them with neighbors.
Applies anticipatory avoidance force to agents/particles to avoid potential future collisions with other agents/particles.
Applies forces to agents/particles to bring them closer to their neighbors.
Applies forces to agents/particles calulated using a VOP network.
Applies force to agents/particles to avoid potential collisions with static objects.
Applies force to agents/particles according to directions from a path curve.
Applies force to agents/particles to move them toward a target position.
Apply force to agents/particles to move them apart from each other.
Used internally in the crowd solver to integrate steering forces.
Constrains agent velocity to only go in a direction within a certain angle range of its current heading, to prevent agents from floating backward.
Apply forces to agents/particles to create a random motion.
A POP node that creates a new stream of particles.
A POP node that applies torque to particles, causing them to spin.
Runs CVEX on a particle system.
A POP node that directly changes the velocity of particles.
A POP node that applies wind to particles.
Applies a wind shadow to particles
Runs a VEX snippet to modify particles.
Solves a Smoothed Particle Hydrodynamics (SPH) density constraint for fluid particles using OpenCL.
A microsolver for particle fluid forces
Visualizes particles.
Creates simulation object groups based on an expression.
Defines the base physical parameters of DOP objects.
Applies a force to an object from a particular location in space.
Creates position information from a point on some SOP geometry.
Associates a position and orientation to an object.
Sets and configures a Pyro solver. This solver can be used to create both fire and smoke.
Performs a sparse pyro simulation on the given object. This solver can be used to create both fire and smoke.
Constrains an RBD object to a certain orientation.
Constrains an RBD object to have a certain orientation, but with a set amount of springiness.
Automatically freezes RBD Objects that have come to rest
Constrain a RBD Car Rig along a path.
Attaches the appropriate data for RBD Objects to an object.
Creates a number of RBD Objects from SOP Geometry. These individual RBD Objects are created from the geometry name attributes.
Guide Bullet Packed Primitives.
Constrains an object to two constraints, creating a rotation similar to a hinge or a trapeze bar.
Creates an RBD Object from SOP Geometry.
Creates a single DOP object from SOP Geometry that represents a number of RBD Objects.
Constrains an RBD object a certain distance from the constraint.
Creates a simulation object at each point of some source geometry, similarly to how the Copy surface node copies geometry onto points.
Sets and configures a Rigid Body Dynamics solver.
Constrains an object to remain a certain distance from the constraint, with a set amount of springiness.
Alters the state information for an RBD Object.
Serves as the end-point of the simulation network. Has controls for writing out sim files.
Saves the state of a DOP network simulation into files.
Saves the state of a DOP network simulation into files.
Applies forces to an object according to the difference between two reference frames.
Sets and configures a Rigid Body Dynamics solver.
Attaches the appropriate data for Ripple Objects to an object.
Creates an object from existing geometry that will be deformed with the ripple solver.
Animates wave propagation across Ripple Objects.
Creates a signed distance field representation of a piece of geometry that can be used for collision detection.
A microsolver that performs general calculations on a pair consisting of a DOP field and a SOP volume/VDB.
Creates a scalar field from a SOP Volume.
Creates a vector field from a SOP Volume Primitive.
Creates a scalar field.
Visualizes a scalar field.
Defines the internal seam angle.
Defines the mass density of a Cloth Object.
Divides a particle system uniformly into multiple slices along a line.
Specifies a cutting plane to divide a particle system into two slices for distributed simulations.
Constrains an object to rotate and translate on a single axis, and limits the rotation and translation on that axis.
Attaches the appropriate data for Smoke Objects to an object.
Creates an Smoke Object from SOP Geometry.
Creates an empty smoke object for a pyro simulation.
Sets and configures a Smoke solver. This is a slightly lower-level solver that is the basis for the Pyro solver.
Performs a sparse smoke simulation on the given object. This is a slightly lower-level solver that is the basis for the sparse pyro solver.
Constrains a set of points on a soft body object to a certain position using a hard constraint or soft constraint.
Soft Body (SBD) Pin Constraint
Constrains a point on a soft body object to a certain position.
Soft Body (SBD) Spring Constraint
Constrains a point on a soft body to a certain position, with a set amount of springiness.
Soft Body Collision Properties
Defines how a soft body object responds to collisions.
Defines how a Soft Body Object responds to collisions.
Defines how a Soft Body Object responds to collisions.
Defines how a Soft Body Object responds to collisions.
Allows the user to import the rest state from a SOP node.
Sets and configures a Soft Body solver.
Defines the strengths of the soft constraint on a soft body object.
Controls the anisotropic behavior of a Solid Object.
Attaches the appropriate data for Solid Objects to an object.
Defines the mass density of a Solid Object.
Defines how a Solid Object reacts to strain and change of volume.
This builds a tree of spheres producing bounding information for an edge cloud.
This builds a tree of spheres producing bounding information for a point cloud.
Splits an incoming object stream into as many as four output streams.
Creates a Static Object from SOP Geometry.
Allows you to inspect the behavior of a static object in the viewport.
Control the thickness of the object that collides with cloth.
Passes one of the input object or data streams to the output.
Creates a Terrain Object from SOP Geometry.
Thin Plate/Thin Plate Collider
Defines a way of resolving collisions between two rigid bodies.
Applies a uniform force and torque to objects.
Applies forces on the objects according to a VOP network.
Creates a vector field.
Visualizes a vector field.
Modifies common Vellum constraint properties during a Vellum solve.
Microsolver to create Vellum constraints during a simulation.
Creates a DOP Object for use with the Vellum Solver.
Blends the current rest values of constraints with a rest state calculated from the current simulation or external geometry.
Sets and configures a Vellum solver.
A Vellum node that creates Vellum patches.
Applies an impulse to an object.
A microsolver to create soft references to visualizers on itself.
Uses instance points to source packed source sets into DOP fields.
Imports SOP source geometry into smoke, pyro, and FLIP simulations.
Defines a way of resolving collisions involving two rigid bodies with volume.
Voronoi Fracture Configure Object
Attaches the appropriate data to make an object fractureable by the Voronoi Fracture Solver
Defines the parameters for dynamic fracturing using the Voronoi Fracture Solver
Dynamically fractures objects based on data from the Voronoi Fracture Configure Object DOP
Applies a vortex-like force on objects, causing them to orbit about an axis along a circular path.
Creates a Whitewater Object that holds data for a whitewater simulation.
Sets and configures a Whitewater Solver.
Applies forces to resist the current motion of objects relative to a turbulent wind.
Constrains a wire point’s orientation to a certain direction.
Wire Angular Spring Constraint
Constrains a wire point’s orientation to a certain direction, with a set amount of springiness.
Attaches the appropriate data for Wire Objects to an object.
Defines the elasticity of a wire object.
Constraints a wire point to a certain position and direction.
Creates a Wire Object from SOP Geometry.
Defines the physical parameters of a wire object.
Defines the plasticity of a wire object.
Sets and configures a Wire solver.
Defines a way of resolving collisions involving a wire object and DOPs objects with volumetric representations.
Defines a way of resolving collisions between two wires.