[x3d-public] IMPORTANT: insistence on professional use of x3d-public mailing list

Sat Sep 9 09:53:43 PDT 2023

1.	Joe is completely correct about the importance of studying the HAnim specification, and corresponding X3D4 specification.  I’ve also linked our 108 X3D models, partitioned into 9 directory categories, each of which has many contextual links to tutorials, videos, and references.

*	Humanoid animation (HAnim) architecture 2.0
*	https://www.web3d.org/documents/specifications/19774/V2.0/index.html

*	X3D 4.0 Architecture and base components, clause 26 Humanoid Animation (HAnim) component
*	https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-IS.proof/Part01/components/hanim.html

*	HumanoidAnimation (HAnim) X3D Examples Archive
*	https://www.web3d.org/x3d/content/examples/HumanoidAnimation

2.	Non-HAnim export is not HAnim.  Apples are not oranges, either.  As ever, figuring out mappings to any single one of multiple provided HAnim templates is a suggested path to adjust a model of interest.  Validation tools then confirm correctness and guide gradual improvement.  This is consistent with the excellent guidance that Joe provided (and you rejected) below.

I must wonder if you are paying attention.  Despite many-times-repeated guidance provided, your email below does not reflect understanding of these basic principles.

3.	Your use of pejorative terms is inappropriate for this professional mailing list.  For your information, not for further discussion:

*	Wikipedia, gaslighting
*	https://en.wikipedia.org/wiki/Gaslighting

4.	John, many of your posts have excellent value and such contributions are consistently acknowledged with thanks.  However your repeated posting of fragmentary, misdirecting, or simply incorrect claims is disrupting the important work of many people using this archived mailing list.

Posting to x3d-public should be your last resort after checking appropriate examples and references, not your reflex response.  Following that carefulness, your posts will have far greater value.

Something must change.  Please self-moderate better.

Very respectfully yours.

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 https://faculty.nps.edu/brutzman

From: x3d-public <x3d-public-bounces at web3d.org> On Behalf Of John Carlson
Sent: Saturday, September 9, 2023 5:51 AM
To: Joe D Williams <joedwil at earthlink.net>
Cc: X3D Graphics public mailing list <x3d-public at web3d.org>
Subject: Re: [x3d-public] standard HAnimHumanoid DEF field value or name field value

Sorry, I know about names and DEFs for joint, segments and sites. I was asking about the HAnimHumanoid node itself, if that wasn't clear.  I don't see it in the LOA4 or your hierarchy at all.  A better tip than gaslighting me would help.

Specifically, what name and DEF standards are there for the node I mentioned?

Most of my current joints come out of tovrmlx3d as Transforms, so rules are different.

I used to know these things, based on looking at user code.  But the user code I'm looking at isn't even HAnim at this point. That's what I'm trying to remedy. I'm trying to insert a node that's not there, and I don't currently have any prefixes.

Simply put, is name="HAnim" correct for the HAnimHumanoid node?  Can I use "HAnim" for a DEF if there's no prefix?

John

On Sat, Sep 9, 2023 at 7:04 AM Joe D Williams <joedwil at earthlink.net <mailto:joedwil at earthlink.net> > wrote:

Study the HAnim standard to see there are exact definitions for all DEF naming of joints, segments, sites based on the name substituted for hanim_ in your example and the type of object. .

Joe

-----Original Message-----
From: John Carlson <yottzumm at gmail.com <mailto:yottzumm at gmail.com> >
Sent: Sep 8, 2023 6:38 PM
To: X3D Graphics public mailing list <x3d-public at web3d.org <mailto:x3d-public at web3d.org> >, Joe D Williams <joedwil at earthlink.net <mailto:joedwil at earthlink.net> >
Subject: standard HAnimHumanoid DEF field value or name field value

Here's how I do Humanoids I generate:

<HAnimHumanoid DEF='hanim_HAnim'  info='"humanoidVersion=2.0"' name='HAnim' scale='1 1 1' translation='0 0 0' version='2.0'>

I'm guessing there's no standard or widely accepted values for either the name value or the DEF value.

Is there a requirement that some substring be in the name or DEF values?

I'm not seeing anything in the LOA4 or Joe's hierarchy.

I'll just construct my own, like everyone else!

Thanks!

John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230909/9aa33313/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5464 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230909/9aa33313/attachment-0001.p7s>