[x3d-public] Discussion: containerField for x3d.py XML export

[John Carlson]

I believe the Transform mentioned in the warnings is part of the skin. Yes,
search for "mesh_"... in the .x3d file.  You will see the skin (whose
geometry IndexedFaceSet below Transform) without the appropriate "skin"
containerField attribute.  I'm still working on an
appropriate HAnimHumanoid skinCoord field. skinCoord is another
containerField (but a bit harder than the others in my mind).  I'm creating
a b2xFindCoordinate() method which you can pass a child of the skin field,
and the method will search for a Coordinate name or DEF which it will
return to place in the skinCoord node as a USE reference.

I can send Don and Joe corrected .x3d files, if you want to see what a
corrected (per view3dscene) file looks like. But let me finish with
skinCoord first.

I am mainly speaking of HAnimHumanoid fields, fields at the HAnimHumanoid
level (Joe mentioned children containerFields for stuff
below humanoid_root).

More testing examples are desired, please send skeleton and animation
examples I can actually load into Blender.

On Sun, Sep 24, 2023 at 8:57 PM John Carlson <yottzumm at gmail.com> wrote:

> I'm merely referring to view3dscene warnings about children
> containerFields, attached.  Or just run tovrmlx3d --validate with a recent
> copy of the .x3d file in the link I sent you.
>
> John
>
> On Sun, Sep 24, 2023 at 7:47 PM Joe D Williams <joedwil at earthlink.net>
> wrote:
>
>> > —the default, children, is not an acceptable to view3dscene.
>>
>>
>>
>> The first Joint uses containerfield skeleton,then the rest use children.
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>
>> Sent: Sep 24, 2023 12:48 PM
>> To: John Carlson <yottzumm at gmail.com>
>> Cc: Peitso, Loren (CIV) <lepeitso at nps.edu>, X3D Graphics public mailing
>> list <x3d-public at web3d.org>
>> Subject: Re: [x3d-public] Discussion: containerField for x3d.py XML export
>>
>>
>>
>> Thanks for continued troubleshooting.
>>
>>
>>
>> Please do not do anything with containerField handling in x3d.py since it
>> is unique to XML encoding.
>>
>>
>>
>> If you encounter any incorrect handling, please provide a regular issue
>> report that notes
>>
>>    - Model, in .x3d/.x3dv and also .py
>>    - Error or warning that was encountered, relevant tools, etc.
>>
>>
>>
>> I can then isolate the problem and fix it.  When errors do occur, it is
>> usually an error in the scene, but sometimes a simple omission of some sort
>> somewhere deep in the code autogeneration of the library.
>>
>>
>>
>> p.s. also thanks for your recent issue reports on X3DJSAIL, very
>> helpful.  I have made a number of improvements this weekend, hoping to
>> publish tonight.
>>
>>
>>
>> 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:* John Carlson <yottzumm at gmail.com>
>> *Sent:* Sunday, September 24, 2023 11:34 AM
>> *To:* Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>; Michalis
>> Kamburelis <michalis.kambi at gmail.com>; Peitso, Loren (CIV) <
>> lepeitso at nps.edu>; X3D Graphics public mailing list <x3d-public at web3d.org
>> >
>> *Subject:* Discussion: containerField for x3d.py XML export
>>
>>
>>
>> First of all, great work on x3d.py, Loren and Don, I feel like I am
>> polishing a diamond.
>>
>>
>>
>> I am considering adding the containerField attribute (not field) to XML
>> output in x3d.py. This is mainly to support requirements of view3dscene.
>> It complains if I don’t add the containerField attributes in HAnim
>> (skeleton and joints containerFields, maybe more)—the default, children, is
>> not an acceptable to view3dscene.  Also, not having a skin containerField
>> is weird when dropping arbitrary Shape nodes into a HAnimHumanoid.
>>
>>
>>
>> Does adding the containerField attribute seem like a good idea, or should
>> I push back on browser vendors?
>>
>>
>>
>> I plan to do something like I do for VRML when printing out joints and
>> skeleton fields etc.  I won’t print out the containerField for obvious
>> fields, i have a list of these somewhere…geometry, appearance, material,
>> etc
>>
>>
>>
>> Should I allow the x3d.py app programmer to add a containerField
>> attribute, or should I compute it as best i can, and save browser vendors
>> the pain?
>>
>>
>>
>> I think what this means is passing an optional parameter to some
>> each.XML() method calls.
>>
>>
>>
>> After writing this message, the answer seems obvious.
>>
>>
>>
>> Comments?
>>
>>
>>
>> John
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230924/3ede2f83/attachment.html>