[x3d-public] HAnim Examples

GPU Group gpugroup at gmail.com
Sun Apr 26 06:11:35 PDT 2020


Yes good catch John - I didn't groom the annex D scene in detail - that's
the way I found it and freewrl didn't complain. -Doug

On Sat, Apr 25, 2020 at 9:06 PM John Carlson <yottzumm at gmail.com> wrote:

> Also see HAnim2pt2 standard example, has skeleton containerField:
>
>
> https://github.com/Web3DConsortium/HAnim/blob/master/ISO-IEC19774/ISO-IEC19774-2/ISO-IEC19774-2v2.0/ISO-IEC19774-2v2.0-IS/MotionDataAnimation/ExampleMocapAnimationMotionObject.html#L92
>
>
> Thanks for clarification!
>
> John
>
> On Sat, Apr 25, 2020 at 10:02 PM John Carlson <yottzumm at gmail.com> wrote:
>
>> JSON translation of annexdA.x3d:
>> http://dug9.users.sourceforge.net/web3d/tests/hanim/annexdA.x3d
>>
>> X3D JSON looks like:
>>
>>       "-skeleton": {
>>         "HAnimHumanoid": {
>>           "@DEF": "hanim_AnnexD01Jin",
>>           "@info": [
>>             "humanoidVersion=2.0"
>>           ],
>>           "@name": "AnnexD01Jin",
>>
>> In my mind, the -skeleton goes inside the HAnimHumanoid, but defer to
>> experts.
>> See X3D XML:
>>
>>
>> <HAnimHumanoid DEF="hanim_AnnexD01Jin" info='"humanoidVersion=2.0"'
>> containerField="skeleton" name="AnnexD01Jin" scale="0.0225 0.0225 0.0225"
>> version="2.0">
>>
>>
>> Why the containerField????
>>
>>
>> Thanks,
>>
>> John
>>
>>
>> On Thu, Apr 23, 2020 at 9:45 PM GPU Group <gpugroup at gmail.com> wrote:
>>
>>> Implemented HAnimMotion - may need touchups.
>>>
>>> -Doug Sanden
>>>
>>>
>>> My experience implementing v4 HAnimMotion in freewrl
>>>
>>> - took 4 days
>>>
>>> - there are some fuzzy areas - specs draft from last summer, and HAnim
>>> specs don't match, and some inconsistencies in HAnim specs. For example
>>> startFrame and endFrame are mentioned in text but not in fields list.
>>>
>>> - the annexd scene in Hanim needed some touchups:
>>>
>>> -- put HAnimMotion node inside HAnimNumanoid
>>>
>>> -- changed frameTime='0.03' to frameDuration='0.03'
>>>
>>> -- in code I change angles from degrees to radians
>>>
>>> x not sure I have the sense of the angles and translations correct
>>>
>>> - perhaps scene authors can tell from screen-capture video - link below
>>>
>>>
>>> SPEC COMMENT >>>
>>>
>>> I initially thought and still after implementing think it would be
>>> useful to split the Motion node into MotionPlayer and MotionData
>>>
>>> Then for scenes with multiple characters doing bits of motion
>>> independently,
>>>
>>> HAnimHumanoid 1:1 HAnimPlay m:1 HAnimData
>>>
>>> so the data can be DEF/USEd by more MotionPlayers for different
>>> characters in the scene
>>>
>>> The MotionPlayer would hold state such as frameIndex for a specific
>>> Humanoid
>>>
>>> - and the MotionData would hold the float values and channel
>>> descriptions.
>>>
>>> <<< SPEC COMMENT
>>>
>>>
>>>
>>> http://dug9.users.sourceforge.net/web3d/tests/hanim/freeWRL%202020-04-23%2020-09-44.mp4
>>>
>>> http://dug9.users.sourceforge.net/web3d/tests/hanim/annexdA.x3d
>>>
>>>
>>>
>>> https://sourceforge.net/p/freewrl/git/ci/develop/tree/freex3d/src/lib/scenegraph/Component_HAnim.c
>>>
>>>
>>> - line 340 for 15 lines
>>>
>>> - line 1090+
>>>
>>> On Wed, Apr 22, 2020 at 5:44 PM GPU Group <gpugroup at gmail.com> wrote:
>>>
>>>> SPEC COMMENT > V4 > HANIMMOTION >>>>
>>>>
>>>> I'm parsing the Motion AnnexD scene with a few tweaks.
>>>> Initial thoughts:.
>>>> Q. should Motion be split into MotionPlayer and MotionData?
>>>> DEF/USE HanimHumanoid - marching troops - same skin and same
>>>> synchronizes walk
>>>> DEF/USE HAnimMotion - synchornized dancers -different skins and LOA,
>>>> but still moving in syncrhonized walk
>>>> - the Motion node would need to be parent-aware and hold a mapping to
>>>> each parent separately
>>>> DEF/USE HANimMotionData - several different characters in the scene
>>>> walking at different times
>>>> - you could do it the current node way, by including the motion data
>>>> for each separate HAnimHumanoid.HanimMotion
>>>> - but if the data was separate -and some of that data is a bit big and
>>>> ugly in the scene file- then you'd only need it once for all the characters.
>>>> -Doug Sanden
>>>> <<<<  SPEC COMMENT > V4 > HANIMMOTION
>>>>
>>>> On Mon, Apr 20, 2020 at 3:01 PM GPU Group <gpugroup at gmail.com> wrote:
>>>>
>>>>> Thanks Don, will read up.
>>>>> -Doug
>>>>>
>>>>> On Mon, Apr 20, 2020 at 2:47 PM Don Brutzman <brutzman at nps.edu> wrote:
>>>>>
>>>>>> [cc: group]
>>>>>>
>>>>>> Hi Doug.  Joe is on phone with me.  Joe notes that the HAnim2
>>>>>> specification includes a Motion object and HAnimMotion example (clause 6
>>>>>> part 2) but it is not in our X3D Example Archives - Basic HAnim examples.
>>>>>>
>>>>>> We have requested that Web3D replace the Draft International
>>>>>> Specification (DIS) on the website with the now completed International
>>>>>> Specification (IS) approved by ISO.
>>>>>>
>>>>>> Available already to Web3D members at
>>>>>>
>>>>>> [2.1]   GitHub: Web3D Consortium members, HAnim
>>>>>>         https://github.com/Web3DConsortium/HAnim
>>>>>>
>>>>>> [2.2]   GitHub: Web3D Consortium members, HAnim Specifications
>>>>>> combined parts 1 and 2
>>>>>>
>>>>>> https://github.com/Web3DConsortium/HAnim/raw/master/ISO-IEC19774-combined-IS.Web3D.zip
>>>>>>
>>>>>> On our Thursday afternoon call we will look at hands and feet (in
>>>>>> response to IEEE 3DBP group), HAnimMotion and triage of the remaining
>>>>>> examples.  I'll ask Anita to schedule a regular weekly zoom line for us,
>>>>>> details will be under MEMBERS > RESOURCES > TELECONFERENCE.
>>>>>>
>>>>>> On 4/20/2020 1:11 PM, GPU Group wrote:
>>>>>> > Q. is there an example scene using the v4 HAnimMotion node?
>>>>>> > -Doug Sanden
>>>>>> >
>>>>>> > On Fri, Apr 17, 2020 at 8:29 AM Joseph D Williams <
>>>>>> joedwil at earthlink.net <mailto:joedwil at earthlink.net>> wrote:
>>>>>> >
>>>>>> >     Hi All, a next practical step is to care for the web3D.org
>>>>>> HAnim Archives. Lots is there and nothing is obsoleted except for new names
>>>>>> for items of the skeleton but all can be updated. There is duplication and
>>>>>> some important items not adequately demonstrated.
>>>>>>
>>>>>> 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
>>>>>>
>>>>> _______________________________________________
>>> x3d-public mailing list
>>> x3d-public at web3d.org
>>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20200426/a0d87863/attachment.html>


More information about the x3d-public mailing list