<div dir="ltr">Hi Joe,<div><br></div><div>ok. Most of the HAnim scenes in the web3d examples archive probably populate these fields with USE references. My vague sense is that they do that only out of a perception that this is required or recommended, not for a functional purpose, but I did not go through those in detail.</div><div><br></div><div>I will see if and how it is possible to special case the nodes in these fields in x3dom, perhaps by removing them from the list of drawable objects.</div><div><br></div><div>On a spec. tangent,
<span style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">19774-2/V2.0 Annex B, here</span></div><div><br></div><div><a href="http://www.web3d.org/documents/specifications/19774-2/V2.0/MotionDataAnimation/ExampleKeyframeAnimation.html" target="_blank">http://www.web3d.org/documents/specifications/19774-2/V2.0/MotionDataAnimation/ExampleKeyframeAnimation.html</a><br></div><div><br></div><div>and
<span style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">19774-1/V2.0</span>
Annex F</div><div><br></div><div><a href="http://www.web3d.org/documents/specifications/19774-1/V2.0/HAnim/Design.html" target="_blank">http://www.web3d.org/documents/specifications/19774-1/V2.0/HAnim/Design.html</a><br></div><div><br></div><div>define a containerField='skeleton' for the example Humanoid whose parent is the Scene. This is probably an editing oversight.</div><div><br></div><div>-Andreas</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jun 19, 2018 at 6:52 PM Joseph D Williams <<a href="mailto:joedwil@earthlink.net" target="_blank">joedwil@earthlink.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="#954F72"><div class="m_-8524481470132272613m_-9204150644141973658WordSection1"><ul style="margin-top:0in" type="disc"><li class="m_-8524481470132272613m_-9204150644141973658MsoListParagraph" style="margin-left:0in">So my question is if only the nodes in the skeleton field should be<u></u><u></u></li></ul><p class="MsoNormal">rendered while the USE references in the joints and segments fields<u></u><u></u></p><p class="MsoNormal">should not be rendered and are provided exclusively for other purposes<u></u><u></u></p><p class="MsoNormal">(like kinematics) ? I could not quite answer that question from the<u></u><u></u></p><p class="MsoNormal">standard language.</p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Forget these fields they are leftovers from when the skeleton was not included in the user code and the fields just defined which of the skeleton parts in the ‘standard’ model that was not even accessible to the actual user, these fields were all he got to author, and some animation. </p><p class="MsoNormal">Anyway, unless somebody can clearly show the need for these, then should be dumped, and never treated as required. When it became feasible to permit the skeleton into the actual user code, these fields became excess but for some reason nobody will delete them. </p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Thanks again, </p><p class="MsoNormal">Joe</p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><u></u> <u></u></p><div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal" style="border:none;padding:0in"><b>From: </b><a href="mailto:andreasplesch@gmail.com" target="_blank">Andreas Plesch</a><br><b>Sent: </b>Tuesday, June 19, 2018 5:35 AM<br><b>To: </b><a href="mailto:x3d-public@web3d.org" target="_blank">X3D Graphics public mailing list</a><br><b>Subject: </b>[x3d-public] HAnim only skeleton renderable ?</p></div><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">In my first attempt to improve the implemention of HAnim nodes and</p><p class="MsoNormal">fields in x3dom, most (all?) shapes making up the Nancy humanoid from</p><p class="MsoNormal">Nancy, native tags, were rendered multiple times, on top of each</p><p class="MsoNormal">other.</p><p class="MsoNormal">The reason turned out to be the USE references in the joints and</p><p class="MsoNormal">segments field of Humanoid.</p><p class="MsoNormal">Since a USE node places another instance of a DEF node into the scene</p><p class="MsoNormal">graph, all the Shapes in the joint and segment nodes were duplicated.</p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">So my question is if only the nodes in the skeleton field should be</p><p class="MsoNormal">rendered while the USE references in the joints and segments fields</p><p class="MsoNormal">should not be rendered and are provided exclusively for other purposes</p><p class="MsoNormal">(like kinematics) ? I could not quite answer that question from the</p><p class="MsoNormal">standard language.</p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">-Andreas</p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">-- </p><p class="MsoNormal">Andreas Plesch</p><p class="MsoNormal">Waltham, MA 02453</p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">_______________________________________________</p><p class="MsoNormal">x3d-public mailing list</p><p class="MsoNormal"><a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a></p><p class="MsoNormal"><a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a></p><p class="MsoNormal"><u></u> <u></u></p></div></div></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="m_-8524481470132272613gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Andreas Plesch<br>Waltham, MA 02453</div></div></div>