[x3d-public] NavigationInfo avatarSize

[Don Brutzman]

Good catch.  The avatarSize field needs to be a 3-tuple in order to prevent assigning a values array of incorrect length.

Added as Mantis issue 1239
	"NavigationInfo avatarSize type should be SFVec3f rather than MFFloat"
	http://www.web3d.org/member-only/mantis/view.php?id=1239

Dick and I were discussing something similar a week ago.  There was some concern that SFVec3f was a vector per se, and inappropriate.

BTW avatarSize is on my short list for worst field design... the three components are not interdependent and author animation might easily want to set a single one independently.  However you cannot modify just one of three values without involving a Script which adds a lot of code complexity, requires higher profile/component support, and inserts a needless impediment to user navigation.

So for X3D v4 we might further consider splitting out avatarSize into three separate SFFloat fields: avatarCollisionDistance, avatarHeightAboveTerrain and avatarWalkHeightMax.

Good discussion topic for this week's X3D Working Group teleconference, all inputs welcome.

On 5/11/2018 8:27 PM, John Carlson wrote:
> http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/navigation.html
> 
> 
>     23.4.4 NavigationInfo
> 
> NavigationInfo : X3DBindableNode {
> 
>    MFFloat  [in,out] avatarSize      [0.25 1.6 0.75]   [0,∞)
> 
> Should this be SFVec3f instead of MFFloat?
> 
> I don’t know the specifics.
> 
> Wondering. Probably not.  My fuzz generator is generating at 5 element float array, FYI.
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