<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Please consider that each of the “sites” “segments” and “joints” nodes are very old and now artificial techniques for the author to indicate the actual nodes that were to be used in the animation. That way, the way it was intended to work is that a ‘standard’ model could be used for the skeleton then the author could include those duplicative lists of skeleton parts to be used. Probably not the best way to do it? The USE node is not even adequate notation for this and it was never intended to be.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Well, anyway, I have never found a vrml or x3d hanim player that actually needs those worthless lists that have now become actual USE nodes, for hecks’s sake. The best way to get rid of the problem is to get the site, segment, and joint lists.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>These lists should be deleted from the standard because they are useless and error-prone in current xml and classic vrml implementations. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks for noticing how this requirement has evolved to be an actual irritation and defect regarding author’s intent rather than just an unneeded artifact.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks and best, </p><p class=MsoNormal>Joe</p><p class=MsoNormal> </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;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:michalis.kambi@gmail.com">Michalis Kamburelis</a><br><b>Sent: </b>Tuesday, June 19, 2018 1:46 PM<br><b>To: </b><a href="mailto:andreasplesch@gmail.com">Andreas Plesch</a><br><b>Cc: </b><a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Re: [x3d-public] HAnim only skeleton renderable ?</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> 2018-06-19 14:34 GMT+02:00 Andreas Plesch <andreasplesch@gmail.com>:</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>><o:p> </o:p></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>><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Indeed the contents of "HAnimHumanoid.joints" should not be rendered.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>See</p><p class=MsoNormal>- My (from view3dscene and Castle Game Engine point of view) notes</p><p class=MsoNormal>about H-Anim on https://castle-engine.io/x3d_implementation_hanim.php</p><p class=MsoNormal>.</p><p class=MsoNormal>- Instant Reality overview of H-Anim usage:</p><p class=MsoNormal>http://doc.instantreality.org/tutorial/humanoid-animation/ .</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Regards,</p><p class=MsoNormal>Michalis</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>x3d-public mailing list</p><p class=MsoNormal>x3d-public@web3d.org</p><p class=MsoNormal>http://web3d.org/mailman/listinfo/x3d-public_web3d.org</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>