[x3d-public] HAnimHumanoid.joints. MFString would be better

[Joe D Williams]

Yes, it should be an mfstring of the name= string.
The rules for finding the string to animate is firm in the spec so no need to use the DEF/USE form in joints node.
I think we had a problem using SUE with a name field so we chose to USE the DEF name, to me a mistake, because we never in hanim use a joint DEF node. 
Also, if NO joints field then all Joint(s) are used; if joints field then only use the ones listed. 
segments node and sites node same, just field of name strings.
Joe

-----Original Message-----
From: Extensible 3D (X3D) Graphics public discussion <x3d-public at web3d.org>
Sent: Jun 13, 2025 6:26 PM
To: X3D Graphics public mailing list <x3d-public at web3d.org>
Cc: John Carlson <yottzumm at gmail.com>
Subject: [x3d-public] HAnimHumanoid.joints. MFString would be better

MFString would be better for HAnimHumanoid.joints, as some systems will have to exclude joints, sites and segments fields in rendering.  But if you don’t have a skeleton field, then you might want to render what’s in the joints, etc. fields, so I’m torn.
 
John


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250615/9c270de9/attachment.html>