Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won


cwhite last won the day on February 17 2016

cwhite had the most liked content!

Community Reputation

45 Excellent

About cwhite

  • Rank

Personal Information

  • Name
  • Location
  1. Rendering Crowds over the farm

    Do you get any errors from mantra, or messages with verbose output enabled?
  2. You need to locate the cone twist constraint's data in the details view. In your case, it would be underneath the constraint network
  3. It's only the motor target parameter that is converted from euler angles to a quaternion.
  4. If you look in the details view, the parameter values are actually converted into a quaternion. So, you'll need a quaternion primitive attribute named 'motor_target'.
  5. It sounds like you should set up the packed primitives as *animated* static objects - then the solver will handle fetching the updated packed primitive's transform from SOPs until it becomes active.
  6. I think the object would also need to be marked as animated for the solver to fetch the updated value from SOPs
  7. For animated static objects you shouldn't need to do any extra work to transfer velocity: https://www.sidefx.com/changelog/?journal=&categories=&body=inherit+velocity&version=16.0.491&build_0=&build_1=&show_versions=on&items_per_page=1
  8. Cycling animation cycles

    The collision geometry / configure joints tools are never mandatory - they are only needed for ragdolls. Agent primitives support either static shapes (attached to an animated transform) or bone deformation.
  9. glue + RBD solver

    The RBD solver only supports the old style of glue, which is the "Glue to Object" parameter on several of the RBD Object DOPs. There is a deprecated (ophidden) RBD Glue Object DOP that is a wrapper around the RBD Fractured Object DOP for setting that up.
  10. I think right-clicking on the checkbox -> Edit Expression -> $F == 42 should work. Otherwise, it's fairly straightforward to do in a SOP solver. It's just an Attribute Copy SOP where Attribute to Match is "name" - no VEX needed.
  11. Affector matrix with packed

    If both objects are being solved, collisions should be disabled in both directions (otherwise, if A thinks it should collide against B, but B thinks it shouldn't collide against A, what should happen?)
  12. Affector matrix with packed

    I think the solver has Make Objects Mutual Affectors enabled by default, but for packed objects the 'collisionignore' point attribute is generally much easier to work with
  13. If you only need this for convex hulls, just do a shrinkwrap SOP in a foreach loop and transfer any attributes that you need
  14. That attribute only applies when the Bullet solver itself breaks constraints, so that a switchover to the new constraint type can happen instantly. Currently, the only constraint type that the Bullet solver can break for you is glue. If you're manually breaking constraints in a SOP solver, you're also responsible for deciding whether to switch it to a new constraint type or leave it as broken
  15. The tuple size is required to be 2, but the second path is only used if the first one fails to load. This allows you to have a fallback in case your preferred path uses variables that may not necessarily be defined in every situation (or example, you might have a relative path like $HIP/agents/mocapbiped3/shapelib.bgeo so that your setup is portable if you upload it somewhere for rendering). Some applications like geodiff don't have $HIP defined when loading geometry, so the second path could specify the absolute path as a fallback. Shape libraries aren't required to be generated through the agent ROP. But, they are expected to have the same format (collection of packed primitives with a name attribute)