[x3d-public] HAnimHumanoid skin first or HAnimHumanoid skinCoord first

[John Carlson]

Remember, it’s not how the app Python looks, but how x3d.py chooses to
output VRML and XML that matters.  The app programmer doesn’t have control
of HAnimHumanoid field order output, x3d.py does.  Either we choose which
field is first, or significant changes need to be made to allow field order
to be specified by the app programmer.

John

On Thu, Jun 12, 2025 at 6:39 AM John Carlson <yottzumm at gmail.com> wrote:

> Technically, there’s a 3rd choice, which just DEF/USEs Coordinates like 2,
> but puts the skin field first.
>
> Your thoughts?
>
> John
>
> On Wed, Jun 11, 2025 at 9:22 PM John Carlson <yottzumm at gmail.com> wrote:
>
>> Users of x3d.py output.
>>
>> Choice between skin field or skinCoord field first in HAnimHumanoid
>> output:
>>
>> 1) skin first,
>>
>> Better for single skin mesh, since AFAIK, skinCoord USE can’t reference
>> multiple meshes if second.   Or can it?  This approach is  also simpler.
>>
>> 2) skinCoord first,
>>
>> Better for multiple skin mesh, all points are gathered in a single
>> Coordinate, which multiple IndexedFaceSet can USE in their coord field.  I
>> believe that Aaron has implemented this for Maya.  I believe Michalis says
>> this is not preferred.   I believe x3d.py does this.
>>
>> I am moving from 1 to 2 in the Blender exporter, particularly, because
>> there aren’t Site or Segment nodes in Blender that I know of. (Blender
>> bones become joints).  Sandrunner example from Vince doesn’t have a single
>> mesh
>>
>> I am not sure if I should continue with Blender.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250612/c78dbd8a/attachment.html>