[x3d-public] X3DPickSensorNode intersectionType values BOUNDS and GEOMETRY are undefined.

[Don Brutzman]

Dick and I met for X3D Specification Editors meeting today.

On 4/25/2020 11:45 AM, Don Brutzman wrote:
> Specification prose is missing definitions, intersectionType values BOUNDS and GEOMETRY are undefined.
> 
> ========================
> 38.3.2 X3DPickSensorNode
> https://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/picking.html#X3DPickSensorNode
> 
> SFString [] intersectionType "BOUNDS" ["GEOMETRY"|"BOUNDS"|...]
> 
> The intersectionType field specifies the precision of the collision computation. The intersectionType constants may be extended by the individual concrete node to provide additional options.

We inserted as second sentence in paragraph above:

When testing intersections, "BOUNDS" indicates that the pickingGeometry is intersected with the bounding box of the pickable object, whereas "GEOMETRY" indicates that the pickingGeometry is intersected with the geometry of the pickable object.

> EXAMPLE 1 An intersectionType may be used to specify the specific algorithm used for the detection.
> ========================
> 
> Entered as Mantis issue 1294
> https://www.web3d.org/member-only/mantis/view.php?id=1294
> 
> Draft definitions welcome, anybody want this?

all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman