<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:229274543;
mso-list-type:hybrid;
mso-list-template-ids:-2092138634 -1 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0D8;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>In character animation the skeleton created during the rigging process <br>is never rendered. It is a collection of points in space that the skin <br>is anchored to. During development and animation, the skeleton may be <br>rendered by the animation and/or rigging tool; but geometry is never <br>created for it. Of course an author may choose to create a mesh for the <br>skeleton, in which case it would be rendered as regular geometry.</li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This is such a superficial and limited and even wrong response that the author should be requested to finally have a knowledgeable conversation about it.</p><p class=MsoNormal>If you told the above to anyone with practical experience in generating skeletal-skin based animations, you would be ignored, or at least considered as a bare novice without an understanding of a ’rigging’ and binding and combinations of techniques to animate blocks of geometries and’ skin surface features vertex by vertex. Further, they have not looked into or understood transport products like gltf get and use the animate a skeleton, other geometries, and the entire character, Finally, this person has never taken the steps to explore how the x3d hanim character captures the important, basic features of the classic realistic skeleton-based humanoid at several levels of detail using all standard x3d features (indeed, except for the ‘skin’ action, but the skin is currently widely implenmnted). </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hey, if it was easy, anyone could do it. Well, it is that easy when you actually consider that if you want to experiment with x3d hanim you really don’ necessarily have to use the ‘medical’ names. A simple proof of x3d hanim is that when you select biped in mast anly tool, you get an x3d hanim loa3, or very close. If the tool Is treating vrml and x3d right, then you should ba able to start with biped, create geometries for sin, segments, sites, whatever then animate the thing and export to x3d. Note that last I saw the free bitmanagement studio and contact work fine in x3d hanim and are free and naturally should be used when evaluating other hanim tools. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks and Best, </p><p class=MsoNormal>Joe</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></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:andreasplesch@gmail.com">Andreas Plesch</a><br><b>Sent: </b>Tuesday, June 19, 2018 12:58 PM<br><b>To: </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><div><div><p class=MsoNormal>Thanks Leonard,</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>this is quite helpful although I got the impression that in HAnim skeleton is contrasting segments and joints and represents the physical body to be rendered.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>But you are correct that there should be answer that does not require assumptions. Perhaps it is productive to focus on the prototype implementation and understand that better first.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Andreas</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Date: Tue, 19 Jun 2018 07:15:00 -0700</p></div></div><p class=MsoNormal style='margin-left:4.8pt'>From: Leonard Daly <<a href="mailto:Leonard.Daly@realism.com" target="_blank">Leonard.Daly@realism.com</a>><br>To: <a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>Subject: Re: [x3d-public] HAnim only skeleton renderable ?<br>Message-ID: <<a href="mailto:c1af840f-df0a-0eee-fc73-7878aac680b2@realism.com" target="_blank">c1af840f-df0a-0eee-fc73-7878aac680b2@realism.com</a>><br>Content-Type: text/plain; charset="utf-8"; Format="flowed"<br><br>Andreas,<br><br>This does not directly answer your question.<br><br>In character animation the skeleton created during the rigging process <br>is never rendered. It is a collection of points in space that the skin <br>is anchored to. During development and animation, the skeleton may be <br>rendered by the animation and/or rigging tool; but geometry is never <br>created for it. Of course an author may choose to create a mesh for the <br>skeleton, in which case it would be rendered as regular geometry.<br><br>Leonard Daly<br><br><br><br>> In my first attempt to improve the implemention of HAnim nodes and<br>> fields in x3dom, most (all?) shapes making up the Nancy humanoid from<br>> Nancy, native tags, were rendered multiple times, on top of each<br>> other.<br>> The reason turned out to be the USE references in the joints and<br>> segments field of Humanoid.<br>> Since a USE node places another instance of a DEF node into the scene<br>> graph, all the Shapes in the joint and segment nodes were duplicated.<br>><br>> So my question is if only the nodes in the skeleton field should be<br>> rendered while the USE references in the joints and segments fields<br>> should not be rendered and are provided exclusively for other purposes<br>> (like kinematics) ? I could not quite answer that question from the<br>> standard language.<br>><br>> -Andreas<br>><br><br>-- <br>*Leonard Daly*<br>3D Systems & Cloud Consultant<br>LA ACM SIGGRAPH Past Chair<br>President, Daly Realism - /Creating the Future/<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180619/9a5f08d4/attachment-0001.html" target="_blank">http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20180619/9a5f08d4/attachment-0001.html</a>><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>x3d-public mailing list<br><a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br><a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br><br><br>------------------------------<br><br>End of x3d-public Digest, Vol 111, Issue 65<br>*******************************************</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>