Difference between revisions of "BallJoint"
From Web3D.org
Line 1: | Line 1: | ||
*[[Node Reference]] | *[[Node Reference]] | ||
− | == | + | ==BallJoint== |
Specification Link: [http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#BallJoint BallJoint] | Specification Link: [http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rigid_physics.html#BallJoint BallJoint] |
Revision as of 09:05, 24 April 2015
Contents
BallJoint
Specification Link: BallJoint
BallJoint : X3DRigidJointNode { SFVec3f [in,out] anchorPoint 0 0 0 (-∞,∞) SFNode [in,out] body1 [] [RigidBody] SFNode [in,out] body2 [] [RigidBody] MFString [in,out] forceOutput "NONE" ["ALL", "NONE", ...] SFNode [in,out] metadata NULL [X3DMetadataObject] SFVec3f [out] body1AnchorPoint [] SFVec3f [out] body2AnchorPoint [] }
DTD Validation
Children
Children must appear as follows:
- A single, optional IS.
- A single, optional node derived from X3DMetadataObject for the metadata field.
- Any number of RigidBody or Prototype nodes in any order.
Attributes
- There is no check that the values in the forceOutput field are acceptable.
Schema Validation
Children
Children must appear as follows:
- A single, optional IS.
- A single, optional node derived from X3DMetadataObject for the metadata field.
- A maximum of two additional children, which may be either RigidBody or Prototype nodes in any order.
Attributes
- There is no check that the values in the forceOutput field are acceptable.
Schematron validation
TBD