<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:1755785366;
mso-list-type:hybrid;
mso-list-template-ids:1874203428 -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><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>Monday, May 28, 2018 11:47 AM<br><b>To: </b><a href="mailto:joedwil@earthlink.net">Joseph D Williams</a><br><b>Cc: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a>; <a href="mailto:x3dom-users@lists.sourceforge.net">x3dom mlist</a>; <a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Re: both X3DOM and X_ITE.</p></div><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>There just does not seem a lot of demand or requests by users or</li></ul><p class=MsoNormal>customers. Of course, this may be a chicken and egg problem.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>And, that if you hae soething that works, like contact and instant, maybe you don’t need to complain. </p><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>Contributions to x3dom or x_ite are always welcome, in any case.</li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Great a contribution to either is a contribution to X3D. </p><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>For x3dom, my interest would be probably the glTF angle. glTF has</li></ul><p class=MsoNormal>character animation. Here is an example:</p><p class=MsoNormal>https://www.donmccurdy.com/2017/11/06/creating-animated-gltf-characters-with-mixamo-and-blender/</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Great, I will look. The basic x3d hanim skeleton, bindings, animations, and geometries can be stored in gltf. I hope I can look back in the hanim archives to see a comparison I did. No doubt gltf can transport the good stuff with the only problem that gltf uses unit quats instead of axis-angle. </p><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>The best explanation, apart from studying glTF loaders, is apparently</li></ul><p class=MsoNormal>in this figure, sorry about that:</p><p class=MsoNormal>https://raw.githubusercontent.com/KhronosGroup/glTF/master/specification/2.0/figures/gltfOverview-2.0.0a.png</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>OK, I will look for more recent info, but I don’t think anything in this has changed. Structure and data – names may be different but the data and its application is the same. Now I know there may be some new tech but for the basics stuf, not much has changed in the last 20 years since hanim was specified. </p><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>There is probably a lot of overlap between glTF and HAnim and it would</li></ul><p class=MsoNormal>be important to understand how both relate to each other to be able to</p><p class=MsoNormal>support both. I think Leonard tried to tackle this but focusing</p><p class=MsoNormal>specifically on glTF-HAnim may be constructive. For example, a</p><p class=MsoNormal>translation of a simple glTF character to an HAnim humanoid would be a</p><p class=MsoNormal>good first step.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>A better first step would be to transcode an HAnim humanoid into gltf and back again. From what I saw it would work. After all, it is all the same structure and same data. I was going to work on the Boxman and the JoeKick models in the x3d hanim example archives</p><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>A functional, minimal subset of HAnim of nodes and/or a Proto-based</li></ul><p class=MsoNormal>implementation of the nodes would also help implementers.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Of course we have the proto-based nodes for HAnim where the geometries are children of Segments (bones) and we animate the skeleton. A prototype for seamless skin animation is Boxman in x3d hanim archives - it needs a fancy script to move skin. Since there are no other features of x3d that approximate the way skin is animated, there are no scriptless prototypes. </p><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>A main challenge will be probably the requirement to have vertex</li></ul><p class=MsoNormal>geometry manipulation in a shader on the GPU. This is done only for</p><p class=MsoNormal>displacement textures of a CommonSurfaceShader node currently in</p><p class=MsoNormal>x3dom.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Yes, we need to control individual ‘skin’ vertices according to a simple weighting algorithm depending upon rotation of one or more joints. That has been a problem, yet it is so basic, that and morph shape, that we should have both features outside the Humanoid container. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If anyone wants to learn character animation, anything you learn about x3d hanim will not be a waste of time. X3d hanim still documents an industry standard approach where inputs were taken from all major toolmakers because strangely, even back in the late 1990’s there was great input from users to the biggies that they had to allow data to be exported and transported between applications. Only the names were changed to prevent favoritism and preserve innocence – ooh, and to bring the secretive data structures and bindings out into the open. . <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>-Andreas</li></ul><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>On Mon, May 28, 2018 at 10:42 AM, Joseph D Williams</p><p class=MsoNormal><joedwil@earthlink.net> wrote:</p><p class=MsoNormal>>> both X3DOM and X_ITE …</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>> The discussions about both X3DOM and X_ITE are, to me, missing a very</p><p class=MsoNormal>> important feature. Neither of these tools can do HAnim skeleton controlled</p><p class=MsoNormal>> deformable skin. This is a very important feature, lending itself to many</p><p class=MsoNormal>> important applications in addition to HAnim. There have been several</p><p class=MsoNormal>> discussions about the hanim joint(s) to deformable skin bindings and as far</p><p class=MsoNormal>> as I have seen, there is no doubt that the way x3d specifies the basic, most</p><p class=MsoNormal>> simple, and most transportable technique to achieve the result. So, as the</p><p class=MsoNormal>> HAnim standard takes the next step, why not move a bit toward implementing</p><p class=MsoNormal>> this important capability in your browsers. BSContact does it, I think</p><p class=MsoNormal>> Instant does it mostly but x3dom and x_ite don’t.</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>> Thanks and Best,</p><p class=MsoNormal>><o:p> </o:p></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><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-- </p><p class=MsoNormal>Andreas Plesch</p><p class=MsoNormal>Waltham, MA 02453</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>