The fifth input provides the guiding geometry. Some pieces could be animated, some pieces set to deform, while others may be set to use spheres as geometry representation. Packed geometry is recognized and can be configured with the RBD Configure SOP to drive their behavior individually. The fourth input provides the collision geometry. It will be used as the simulation geometry when provided. The third input is the proxy geometry, a simplified representation of the render geometry, better suited for fast simulations. You can also use the RBD Constraint Properties SOP to set these up. They need a name point attribute connecting them to their respective pieces and a constraint_name primitive attribute matching the constraint relationship DOP’s data name, and can have primitive attributes to define their behaviorĭuring the course of the simulation. These can be created when fracturing the geometry using an RBD Material Fracture SOP or created explicitly using the RBD Constraints From Lines, RBD Constraints From Curves, or RBD Constraints From Rules among other methods. The second input is the constraint geometry, used to instantiate dynamic constraint It will be used as simulation geometry if none is provided in the third input. ![]() ![]() Like most RBD SOPs, it is based on a three input SOP, with 2 additional inputs. The RBD Bullet Solver is a wrapper around a DOP network to simplify the running ofīullet simulations.
0 Comments
Leave a Reply. |