x_ite 8.8.6 → 8.9.0

package/docs/_posts/components/RigidBodyPhysics/BallJoint.md

@@ -1,6 +1,6 @@
 ---
 title: BallJoint
-date: 2022-01-07
+date: 2023-01-07
 nav: components-RigidBodyPhysics
 categories: [components, RigidBodyPhysics]
 tags: [BallJoint, RigidBodyPhysics]
@@ -15,7 +15,7 @@ tags: [BallJoint, RigidBodyPhysics]
 
 BallJoint represents an unconstrained joint between two bodies that pivot about a common anchor point. Contains two RigidBody nodes (containerField values body1, body2).
 
-The BallJoint node belongs to the **RigidBodyPhysics** component and its default container field is *joints.* It is available since X3D version 3.2 or later.
+The BallJoint node belongs to the **RigidBodyPhysics** component and its default container field is *joints.* It is available from X3D version 3.2 or higher.
 
 ## Hierarchy
 
@@ -29,13 +29,17 @@ The BallJoint node belongs to the **RigidBodyPhysics** component and its default
 
 ### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
 
-### MFString [in, out] **forceOutput** "NONE" <small>["ALL","NONE",...]</small>
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
+
+### MFString [in, out] **forceOutput** "NONE" <small>["ALL", "NONE", ...]</small>
 
 *forceOutput* controls which output fields are generated for the next frame. Values are ALL, NONE, or exact names of output fields updated at start of next frame.
 
-### SFVec3f [in, out] **anchorPoint** 0 0 0
+### SFVec3f [in, out] **anchorPoint** 0 0 0 <small>(-∞,∞)</small>
 
 *anchorPoint* is joint center, specified in world coordinates.
 
@@ -45,7 +49,11 @@ Metadata are not part of the X3D world and not interpreted by the X3D browser, b
 
 #### Hint
 
-- Can detect separation if body1AnchorPoint!=body2AnchorPoint.
+- Can detect separation if *body1AnchorPoint*!=body2AnchorPoint.
+
+#### Warning
+
+- It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.
 
 ### SFVec3f [out] **body2AnchorPoint**
 
@@ -53,17 +61,21 @@ Metadata are not part of the X3D world and not interpreted by the X3D browser, b
 
 #### Hint
 
-- Can detect separation if body1AnchorPoint!=body2AnchorPoint.
+- Can detect separation if body1AnchorPoint!=*body2AnchorPoint*.
+
+#### Warning
+
+- It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.
 
 ### SFNode [in, out] **body1** NULL <small>[RigidBody]</small>
 
-Input/Output field body1.
+The *body1* and body2 fields indicate the two RigidBody nodes connected by this joint.
 
 ### SFNode [in, out] **body2** NULL <small>[RigidBody]</small>
 
-Input/Output field body2.
+The body1 and *body2* fields indicate the two RigidBody nodes connected by this joint.
 
-## Description
+## Advisories
 
 ### Hint
 
@@ -73,6 +85,6 @@ Input/Output field body2.
 
 <x3d-canvas src="https://create3000.github.io/media/examples/RigidBodyPhysics/BallJoint/BallJoint.x3d" update="auto"></x3d-canvas>
 
-## External Links
+## See Also
 
-- [X3D Specification of BallJoint](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rigidBodyPhysics.html#BallJoint){:target="_blank"}
+- [X3D Specification of BallJoint node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rigidBodyPhysics.html#BallJoint){:target="_blank"}

package/docs/_posts/components/RigidBodyPhysics/CollidableOffset.md

@@ -1,6 +1,6 @@
 ---
 title: CollidableOffset
-date: 2022-01-07
+date: 2023-01-07
 nav: components-RigidBodyPhysics
 categories: [components, RigidBodyPhysics]
 tags: [CollidableOffset, RigidBodyPhysics]
@@ -13,9 +13,9 @@ tags: [CollidableOffset, RigidBodyPhysics]
 
 ## Overview
 
-CollidableOffset repositions geometry relative to center of owning body. Contains a single CollidableShape or CollidableOffset node (containerField='collidable').
+CollidableOffset repositions geometry relative to center of owning body. Contains a single CollidableShape or CollidableOffset node (`containerField='collidable').`
 
-The CollidableOffset node belongs to the **RigidBodyPhysics** component and its default container field is *children.* It is available since X3D version 3.2 or later.
+The CollidableOffset node belongs to the **RigidBodyPhysics** component and its default container field is *children.* It is available from X3D version 3.2 or higher.
 
 ## Hierarchy
 
@@ -32,7 +32,11 @@ The CollidableOffset node belongs to the **RigidBodyPhysics** component and its
 
 ### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### SFBool [in, out] **enabled** TRUE
 
@@ -44,7 +48,7 @@ Position (x, y, z in meters) of children relative to local coordinate system.
 
 #### Hint
 
-- The order of operation is first apply the center offset, then scaleOrientation and scale, then rotation, then restore the center offset, then translation.
+- The order of operation is first apply the center offset, then scaleOrientation and scale, then rotation, then restore the center offset, then *translation*.
 
 ### SFRotation [in, out] **rotation** 0 0 1 0 <small>[0,1]</small>
 
@@ -52,18 +56,18 @@ Orientation (axis, angle in radians) of children relative to local coordinate sy
 
 #### Hint
 
-- The order of operation is first apply the center offset, then scaleOrientation and scale, then rotation, then restore the center offset, then translation.
+- The order of operation is first apply the center offset, then scaleOrientation and scale, then *rotation*, then restore the center offset, then translation.
 
-### SFBool [ ] **visible** TRUE
+### SFBool [in, out] **visible** TRUE
 
 Whether or not renderable content within this node is visually displayed.
 
-#### Hint
+#### Hints
 
-- The visible field has no effect on animation behaviors, event passing or other non-visual characteristics.
-- Content must be visible to be collidable and to be pickable.
+- The *visible* field has no effect on animation behaviors, event passing or other non-visual characteristics.
+- Content must be *visible* to be collidable and to be pickable.
 
-### SFBool [ ] **bboxDisplay** FALSE
+### SFBool [in, out] **bboxDisplay** FALSE
 
 Whether to display bounding box for associated geometry, aligned with world coordinates.
 
@@ -71,22 +75,41 @@ Whether to display bounding box for associated geometry, aligned with world coor
 
 - The bounding box is displayed regardless of whether contained content is visible.
 
-### SFVec3f [ ] **bboxSize** -1 -1 -1 <small>[0,∞) or -1 -1 -1</small>
+### SFVec3f [ ] **bboxSize** -1 -1 -1 <small>[0,∞) or −1 −1 −1</small>
 
 Bounding box size is usually omitted, and can easily be calculated automatically by an X3D player at scene-loading time with minimal computational cost. Bounding box size can also be defined as an optional authoring hint that suggests an optimization or constraint.
 
-#### Hint
+#### Hints
 
 - Can be useful for collision computations or inverse-kinematics (IK) engines.
+- Precomputation and inclusion of bounding box information can speed up the initialization of large detailed models, with a corresponding cost of increased file size.
+- [X3D Architecture, 10.2.2 Bounding boxes](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#BoundingBoxes){:target="_blank"}
+- [X3D Architecture, 10.3.1 X3DBoundedObject](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#X3DBoundedObject){:target="_blank"}
 
 ### SFVec3f [ ] **bboxCenter** 0 0 0 <small>(-∞,∞)</small>
 
-Bounding box center: optional hint for position offset from origin of local coordinate system.
+Bounding box center accompanies bboxSize and provides an optional hint for bounding box position offset from origin of local coordinate system.
+
+#### Hints
+
+- Precomputation and inclusion of bounding box information can speed up the initialization of large detailed models, with a corresponding cost of increased file size.
+- [X3D Architecture, 10.2.2 Bounding boxes](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#BoundingBoxes){:target="_blank"}
+- [X3D Architecture, 10.3.1 X3DBoundedObject](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#X3DBoundedObject){:target="_blank"}
 
 ### SFNode [ ] **collidable** NULL <small>[X3DNBodyCollidableNode]</small>
 
-Field collidable.
+The *collidable* field holds a reference to a single nested item of a *collidable* scene graph.
+
+#### Warning
+
+- If there are multiple transformation paths to this reference, the results are undefined.
+
+## Advisories
+
+### Hint
+
+- Content must be visible to be collidable and to be pickable.
 
-## External Links
+## See Also
 
-- [X3D Specification of CollidableOffset](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rigidBodyPhysics.html#CollidableOffset){:target="_blank"}
+- [X3D Specification of CollidableOffset node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rigidBodyPhysics.html#CollidableOffset){:target="_blank"}

package/docs/_posts/components/RigidBodyPhysics/CollidableShape.md

@@ -1,6 +1,6 @@
 ---
 title: CollidableShape
-date: 2022-01-07
+date: 2023-01-07
 nav: components-RigidBodyPhysics
 categories: [components, RigidBodyPhysics]
 tags: [CollidableShape, RigidBodyPhysics]
@@ -13,9 +13,9 @@ tags: [CollidableShape, RigidBodyPhysics]
 
 ## Overview
 
-CollidableShape connects the collision detection system, the rigid body model, and the renderable scene graph. Contains a single Shape node (containerField='shape') for animating collidable geometry.
+CollidableShape connects the collision detection system, the rigid body model, and the renderable scene graph. Contains a single Shape node (`containerField='shape')` for animating collidable geometry.
 
-The CollidableShape node belongs to the **RigidBodyPhysics** component and its default container field is *children.* It is available since X3D version 3.2 or later.
+The CollidableShape node belongs to the **RigidBodyPhysics** component and its default container field is *children.* It is available from X3D version 3.2 or higher.
 
 ## Hierarchy
 
@@ -30,7 +30,11 @@ The CollidableShape node belongs to the **RigidBodyPhysics** component and its d
 
 ### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### SFBool [in, out] **enabled** TRUE
 
@@ -42,7 +46,7 @@ Position (x, y, z in meters) of children relative to local coordinate system.
 
 #### Hint
 
-- The order of operation is first apply the center offset, then scaleOrientation and scale, then rotation, then restore the center offset, then translation.
+- The order of operation is first apply the center offset, then scaleOrientation and scale, then rotation, then restore the center offset, then *translation*.
 
 ### SFRotation [in, out] **rotation** 0 0 1 0 <small>[0,1]</small>
 
@@ -50,18 +54,18 @@ Orientation (axis, angle in radians) of children relative to local coordinate sy
 
 #### Hint
 
-- The order of operation is first apply the center offset, then scaleOrientation and scale, then rotation, then restore the center offset, then translation.
+- The order of operation is first apply the center offset, then scaleOrientation and scale, then *rotation*, then restore the center offset, then translation.
 
-### SFBool [ ] **visible** TRUE
+### SFBool [in, out] **visible** TRUE
 
 Whether or not renderable content within this node is visually displayed.
 
-#### Hint
+#### Hints
 
-- The visible field has no effect on animation behaviors, event passing or other non-visual characteristics.
-- Content must be visible to be collidable and to be pickable.
+- The *visible* field has no effect on animation behaviors, event passing or other non-visual characteristics.
+- Content must be *visible* to be collidable and to be pickable.
 
-### SFBool [ ] **bboxDisplay** FALSE
+### SFBool [in, out] **bboxDisplay** FALSE
 
 Whether to display bounding box for associated geometry, aligned with world coordinates.
 
@@ -69,32 +73,46 @@ Whether to display bounding box for associated geometry, aligned with world coor
 
 - The bounding box is displayed regardless of whether contained content is visible.
 
-### SFVec3f [ ] **bboxSize** -1 -1 -1 <small>[0,∞) or -1 -1 -1</small>
+### SFVec3f [ ] **bboxSize** -1 -1 -1 <small>[0,∞) or −1 −1 −1</small>
 
 Bounding box size is usually omitted, and can easily be calculated automatically by an X3D player at scene-loading time with minimal computational cost. Bounding box size can also be defined as an optional authoring hint that suggests an optimization or constraint.
 
-#### Hint
+#### Hints
 
 - Can be useful for collision computations or inverse-kinematics (IK) engines.
+- Precomputation and inclusion of bounding box information can speed up the initialization of large detailed models, with a corresponding cost of increased file size.
+- [X3D Architecture, 10.2.2 Bounding boxes](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#BoundingBoxes){:target="_blank"}
+- [X3D Architecture, 10.3.1 X3DBoundedObject](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#X3DBoundedObject){:target="_blank"}
 
 ### SFVec3f [ ] **bboxCenter** 0 0 0 <small>(-∞,∞)</small>
 
-Bounding box center: optional hint for position offset from origin of local coordinate system.
+Bounding box center accompanies bboxSize and provides an optional hint for bounding box position offset from origin of local coordinate system.
+
+#### Hints
+
+- Precomputation and inclusion of bounding box information can speed up the initialization of large detailed models, with a corresponding cost of increased file size.
+- [X3D Architecture, 10.2.2 Bounding boxes](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#BoundingBoxes){:target="_blank"}
+- [X3D Architecture, 10.3.1 X3DBoundedObject](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#X3DBoundedObject){:target="_blank"}
 
 ### SFNode [ ] **shape** NULL <small>[Shape]</small>
 
-Field shape.
+The *shape* field provides a geometry proxy for specifying which geometry best represents the collidable object.
+
+## Advisories
 
-## Description
+### Hint
+
+- Content must be visible to be collidable and to be pickable.
 
-### Warning
+### Warnings
 
 - Avoid changing Shape geometry at run time to prevent performance problems.
+- Apply `containerField='shape'` to single Shape child node, not `containerField='children'` default.
 
 ## Example
 
 <x3d-canvas src="https://create3000.github.io/media/examples/RigidBodyPhysics/CollidableShape/CollidableShape.x3d" update="auto"></x3d-canvas>
 
-## External Links
+## See Also
 
-- [X3D Specification of CollidableShape](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rigidBodyPhysics.html#CollidableShape){:target="_blank"}
+- [X3D Specification of CollidableShape node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rigidBodyPhysics.html#CollidableShape){:target="_blank"}

package/docs/_posts/components/RigidBodyPhysics/CollisionCollection.md

@@ -1,6 +1,6 @@
 ---
 title: CollisionCollection
-date: 2022-01-07
+date: 2023-01-07
 nav: components-RigidBodyPhysics
 categories: [components, RigidBodyPhysics]
 tags: [CollisionCollection, RigidBodyPhysics]
@@ -15,7 +15,7 @@ tags: [CollisionCollection, RigidBodyPhysics]
 
 CollisionCollection holds a collection of objects that can be managed as a single entity for resolution of inter-object collisions.
 
-The CollisionCollection node belongs to the **RigidBodyPhysics** component and its default container field is *collider.* It is available since X3D version 3.2 or later.
+The CollisionCollection node belongs to the **RigidBodyPhysics** component and its default container field is *collider.* It is available from X3D version 3.2 or higher.
 
 ## Hierarchy
 
@@ -27,9 +27,13 @@ The CollisionCollection node belongs to the **RigidBodyPhysics** component and i
 
 ## Fields
 
-### SFNode [in, out] **metadata** NULL
+### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### SFBool [in, out] **enabled** TRUE
 
@@ -37,54 +41,55 @@ Enables/disables node operation.
 
 ### MFString [in, out] **appliedParameters** "BOUNCE"
 
-Default global parameters for collision outputs of rigid body physics system. Contact node can override parent CollisionCollection node. Selectable values for array: "BOUNCE" "USER_FRICTION" "FRICTION_COEFFICIENT-2" "ERROR_REDUCTION" "CONSTANT_FORCE" "SPEED-1" "SPEED-2" "SLIP-1" "SLIP-2".
+Default global parameters for collision outputs of rigid body physics system. Contact node can override parent CollisionCollection node. Selectable values for array: "BOUNCE" "USER_FRICTION" "FRICTION_COEFFICIENT_2" "ERROR_REDUCTION" "CONSTANT_FORCE" "SPEED_1" "SPEED_2" "SLIP_1" "SLIP_2".
 
 #### Hint
 
-- BOUNCE: bounce value is used; USER_FRICTION: apply user-supplied value; FRICTION_COEFFICIENT-2: apply frictionCoefficients values; ERROR_REDUCTION: apply softnessErrorCorrection value; CONSTANT_FORCE: apply softnessConstantForceMix value; SPEED-1: apply first component of surfaceSpeed array; SPEED-2: apply second component of surfaceSpeed array; SLIP-1: apply first component of slipFactors array; SLIP-2: apply second component of slipFactors array.
+- BOUNCE: bounce value is used; USER_FRICTION: apply user-supplied value; FRICTION_COEFFICIENT_2: apply frictionCoefficients values; ERROR_REDUCTION: apply softnessErrorCorrection value; CONSTANT_FORCE: apply softnessConstantForceMix value; SPEED_1: apply first component of surfaceSpeed array; SPEED_2: apply second component of surfaceSpeed array; SLIP_1: apply first component of slipFactors array; SLIP_2: apply second component of slipFactors array.
 
 ### SFFloat [in, out] **bounce** 0 <small>[0,1]</small>
 
-*bounce* indicates bounciness (0 = no bounce at all, 1 = maximum bounce).
+*bounce* indicates bounciness (0 = no *bounce* at all, 1 = maximum *bounce*).
 
-### SFFloat [in, out] **minBounceSpeed** 0.1
+### SFFloat [in, out] **minBounceSpeed** 0.1 <small>[0,∞)</small>
 
 *minBounceSpeed* m/s needed to bounce.
 
-### SFVec2f [in, out] **frictionCoefficients** 0 0
+### SFVec2f [in, out] **frictionCoefficients** 0 0 <small>[0,∞)</small>
 
 *frictionCoefficients* used for computing surface drag.
 
-### SFVec2f [in, out] **surfaceSpeed** 0 0
+### SFVec2f [in, out] **surfaceSpeed** 0 0 <small>(-∞,∞)</small>
 
 *surfaceSpeed* defines speed vectors for computing surface drag, if contact surfaces move independently of bodies.
 
-### SFVec2f [in, out] **slipFactors** 0 0
+### SFVec2f [in, out] **slipFactors** 0 0 <small>(-∞,∞)</small>
 
 *slipFactors* used for computing surface drag.
 
-### SFFloat [in, out] **softnessConstantForceMix** 0.0001
+### SFFloat [in, out] **softnessConstantForceMix** 0.0001 <small>[0,1]</small>
 
 *softnessConstantForceMix* value applies a constant force value to make colliding surfaces appear to be somewhat soft.
 
-### SFFloat [in, out] **softnessErrorCorrection** 0.8
+### SFFloat [in, out] **softnessErrorCorrection** 0.8 <small>[0,1]</small>
 
 *softnessErrorCorrection* indicates fraction of collision error fixed in a set of evaluations (0 = no error correction, 1 = all errors corrected in single step).
 
 ### MFNode [in, out] **collidables** [ ] <small>[X3DNBodyCollisionSpaceNode,X3DNBodyCollidableNode]</small>
 
-Input/Output field collidables.
+CollisionCollection node holds a collection of objects in the *collidables* field that can be managed as a single entity for resolution of inter-object collisions with other groups of collidable objects. A group consists of both collidable objects as well as spaces that may be collided against each other.
 
-## Description
+## Advisories
 
-### Hint
+### Hints
 
-- Contains an array of CollisionSpace, CollidableShape or CollidableOffset nodes (containerField='collidables').
+- Contains an array of CollisionSpace, CollidableShape or CollidableOffset nodes (`containerField='collidables').`
+- Content must be visible to be collidable and to be pickable.
 
 ## Example
 
 <x3d-canvas src="https://create3000.github.io/media/examples/RigidBodyPhysics/CollisionCollection/CollisionCollection.x3d" update="auto"></x3d-canvas>
 
-## External Links
+## See Also
 
-- [X3D Specification of CollisionCollection](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rigidBodyPhysics.html#CollisionCollection){:target="_blank"}
+- [X3D Specification of CollisionCollection node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rigidBodyPhysics.html#CollisionCollection){:target="_blank"}

package/docs/_posts/components/RigidBodyPhysics/CollisionSensor.md

@@ -1,6 +1,6 @@
 ---
 title: CollisionSensor
-date: 2022-01-07
+date: 2023-01-07
 nav: components-RigidBodyPhysics
 categories: [components, RigidBodyPhysics]
 tags: [CollisionSensor, RigidBodyPhysics]
@@ -15,7 +15,7 @@ tags: [CollisionSensor, RigidBodyPhysics]
 
 CollisionSensor generates collision-detection events.
 
-The CollisionSensor node belongs to the **RigidBodyPhysics** component and its default container field is *children.* It is available since X3D version 3.2 or later.
+The CollisionSensor node belongs to the **RigidBodyPhysics** component and its default container field is *children.* It is available from X3D version 3.2 or higher.
 
 ## Hierarchy
 
@@ -30,7 +30,11 @@ The CollisionSensor node belongs to the **RigidBodyPhysics** component and its d
 
 ### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### SFBool [in, out] **enabled** TRUE
 
@@ -40,26 +44,31 @@ Enables/disables node operation.
 
 *isActive* true/false events are sent when sensing starts/stops.
 
+#### Warning
+
+- It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.
+
 ### MFNode [out] **intersections** <small>[X3DNBodyCollidableNode]</small>
 
-Output field intersections.
+Output field *intersections*.
 
 ### MFNode [out] **contacts** <small>[Contact]</small>
 
-Output field contacts.
+Output field *contacts*.
 
 ### SFNode [in, out] **collider** NULL <small>[CollisionCollection]</small>
 
-Input/Output field collider.
+The *collider* field specifies a CollisionCollection node that holds a collidables field of nodes and spaces that are to be included in collision-detection computations.
 
-## Description
+## Advisories
 
 ### Hints
 
-- Contains CollisionCollection node (containerField='collider').
-- CollisionSensor also has output events: CollidableOffset and CollidableShape nodes (containerField='intersections'), Contact nodes (containerField='contacts').
+- Contains CollisionCollection node (`containerField='collider').`
+- CollisionSensor also has output events: CollidableOffset and CollidableShape nodes (`containerField='intersections'),` Contact nodes (`containerField='contacts').`
+- [Event timing details are explained in X3D Specification 4.4.8.3 Execution model](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/concepts.html#ExecutionModel){:target="_blank"}
+- Content must be visible to be collidable and to be pickable.
 
-## External Links
+## See Also
 
-- [X3D Specification of CollisionSensor](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rigidBodyPhysics.html#CollisionSensor){:target="_blank"}
-- [Event timing details are explained in 4.4.8.3 Execution model](https://www.web3d.org/files/specifications/19775-1/V3.3/Part01/concepts.html#ExecutionModel){:target="_blank"}
+- [X3D Specification of CollisionSensor node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rigidBodyPhysics.html#CollisionSensor){:target="_blank"}

package/docs/_posts/components/RigidBodyPhysics/CollisionSpace.md

@@ -1,6 +1,6 @@
 ---
 title: CollisionSpace
-date: 2022-01-07
+date: 2023-01-07
 nav: components-RigidBodyPhysics
 categories: [components, RigidBodyPhysics]
 tags: [CollisionSpace, RigidBodyPhysics]
@@ -13,9 +13,9 @@ tags: [CollisionSpace, RigidBodyPhysics]
 
 ## Overview
 
-CollisionSpace holds collection of objects considered together for resolution of inter-object collisions. Contains multiple CollidableShape, CollidableOffset, or CollisionSpace nodes (containerField='collidables').
+CollisionSpace holds collection of objects considered together for resolution of inter-object collisions. Contains multiple CollidableShape, CollidableOffset, or CollisionSpace nodes (`containerField='collidables').`
 
-The CollisionSpace node belongs to the **RigidBodyPhysics** component and its default container field is *children.* It is available since X3D version 3.2 or later.
+The CollisionSpace node belongs to the **RigidBodyPhysics** component and its default container field is *children.* It is available from X3D version 3.2 or higher.
 
 ## Hierarchy
 
@@ -29,9 +29,13 @@ The CollisionSpace node belongs to the **RigidBodyPhysics** component and its de
 
 ## Fields
 
-### SFNode [in, out] **metadata** NULL
+### SFNode [in, out] **metadata** NULL <small>[X3DMetadataObject]</small>
 
-Metadata are not part of the X3D world and not interpreted by the X3D browser, but they can be accessed via the ECMAScript interface.
+Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.
+
+#### Hint
+
+- [X3D Architecture 7.2.4 Metadata](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/core.html#Metadata){:target="_blank"}
 
 ### SFBool [in, out] **enabled** TRUE
 
@@ -49,16 +53,16 @@ Enables/disables node operation.
 
 - Using geometry is more accurate but slower.
 
-### SFBool [ ] **visible** TRUE
+### SFBool [in, out] **visible** TRUE
 
 Whether or not renderable content within this node is visually displayed.
 
-#### Hint
+#### Hints
 
-- The visible field has no effect on animation behaviors, event passing or other non-visual characteristics.
-- Content must be visible to be collidable and to be pickable.
+- The *visible* field has no effect on animation behaviors, event passing or other non-visual characteristics.
+- Content must be *visible* to be collidable and to be pickable.
 
-### SFBool [ ] **bboxDisplay** FALSE
+### SFBool [in, out] **bboxDisplay** FALSE
 
 Whether to display bounding box for associated geometry, aligned with world coordinates.
 
@@ -66,22 +70,37 @@ Whether to display bounding box for associated geometry, aligned with world coor
 
 - The bounding box is displayed regardless of whether contained content is visible.
 
-### SFVec3f [ ] **bboxSize** -1 -1 -1
+### SFVec3f [ ] **bboxSize** -1 -1 -1 <small>[0,∞) or −1 −1 −1</small>
 
 Bounding box size is usually omitted, and can easily be calculated automatically by an X3D player at scene-loading time with minimal computational cost. Bounding box size can also be defined as an optional authoring hint that suggests an optimization or constraint.
 
-#### Hint
+#### Hints
 
 - Can be useful for collision computations or inverse-kinematics (IK) engines.
+- Precomputation and inclusion of bounding box information can speed up the initialization of large detailed models, with a corresponding cost of increased file size.
+- [X3D Architecture, 10.2.2 Bounding boxes](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#BoundingBoxes){:target="_blank"}
+- [X3D Architecture, 10.3.1 X3DBoundedObject](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#X3DBoundedObject){:target="_blank"}
 
-### SFVec3f [ ] **bboxCenter** 0 0 0
+### SFVec3f [ ] **bboxCenter** 0 0 0 <small>(-∞,∞)</small>
 
-Bounding box center: optional hint for position offset from origin of local coordinate system.
+Bounding box center accompanies bboxSize and provides an optional hint for bounding box position offset from origin of local coordinate system.
+
+#### Hints
+
+- Precomputation and inclusion of bounding box information can speed up the initialization of large detailed models, with a corresponding cost of increased file size.
+- [X3D Architecture, 10.2.2 Bounding boxes](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#BoundingBoxes){:target="_blank"}
+- [X3D Architecture, 10.3.1 X3DBoundedObject](https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/grouping.html#X3DBoundedObject){:target="_blank"}
 
 ### MFNode [in, out] **collidables** [ ] <small>[X3DNBodyCollisionSpaceNode,X3DNBodyCollidableNode]</small>
 
-Input/Output field collidables.
+Collection of collidable objects as well as nested CollisionSpace collections
+
+## Advisories
+
+### Hint
+
+- Content must be visible to be collidable and to be pickable.
 
-## External Links
+## See Also
 
-- [X3D Specification of CollisionSpace](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rigidBodyPhysics.html#CollisionSpace){:target="_blank"}
+- [X3D Specification of CollisionSpace node](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/rigidBodyPhysics.html#CollisionSpace){:target="_blank"}