<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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
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" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>"""<o:p></o:p></p><p class=MsoNormal>Hey, my stuff no longer works! My models (in glTF, X3D, whatever) have<o:p></o:p></p><p class=MsoNormal>vertexes at coordinates like Z = 0.00001, 0.00002, 0.00003. And now,<o:p></o:p></p><p class=MsoNormal>after processing and saving to X3D using your tools, they are all<o:p></o:p></p><p class=MsoNormal>equal zero, resulting in bugs (things start to fight in Z buffer).<o:p></o:p></p><p class=MsoNormal>"""<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Not surprizing because there is nothing in Hanim that requires that precision.<o:p></o:p></p><p class=MsoNormal>These are all zero. Show example. <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:michalis.kambi@gmail.com">Michalis Kamburelis</a><br><b>Sent: </b>Friday, February 10, 2023 5:13 AM<br><b>To: </b><a href="mailto:brutzman@nps.edu">Brutzman, Donald (Don) (CIV)</a><br><b>Cc: </b><a href="mailto:joedwil@earthlink.net">Joseph D Williams</a>; <a href="mailto:x3d-public@web3d.org">X3D Public Mailing List (x3d-public@web3d.org)</a><br><b>Subject: </b>Re: Wishlist for view3dscene</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks, and sorry for a delay in answering!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The "description" field has been added to texture nodes and few more,</p><p class=MsoNormal>as you can see in another thread on x3d-public :)</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As for digits precision when saving: it's not so easy, in general it's</p><p class=MsoNormal>(one of) the problems that come from X3D using text representation for</p><p class=MsoNormal>floats in per-vertex data. Namely, if we cut the saved numbers to 4</p><p class=MsoNormal>decimal places, I'm 90% sure that I will get a valid bugreport from</p><p class=MsoNormal>someone:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>"""</p><p class=MsoNormal>Hey, my stuff no longer works! My models (in glTF, X3D, whatever) have</p><p class=MsoNormal>vertexes at coordinates like Z = 0.00001, 0.00002, 0.00003. And now,</p><p class=MsoNormal>after processing and saving to X3D using your tools, they are all</p><p class=MsoNormal>equal zero, resulting in bugs (things start to fight in Z buffer).</p><p class=MsoNormal>"""</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Surely we could add a configuration option for it, but it feels</p><p class=MsoNormal>counter-productive, when my recommendation to everyone would be still</p><p class=MsoNormal>"use the maximum precision, to be safe". I would add a feature that I</p><p class=MsoNormal>explicitly say should not be used.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In the end, the longer text representation for numbers only hurts the</p><p class=MsoNormal>file size. And I don't believe we can really fix it by outputting less</p><p class=MsoNormal>digits. The right solution is storing per-vertex data in a binary</p><p class=MsoNormal>blob, when each float is binary 4 bytes, so it's</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>- efficient storage</p><p class=MsoNormal>- efficient reading by X3D implementation to a "float[] array", no</p><p class=MsoNormal>need for text parsing.</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><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>śr., 28 gru 2022 o 21:00 Brutzman, Donald (Don) (CIV)</p><p class=MsoNormal><brutzman@nps.edu> napisał(a):</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Hi Michalis. Joe and I are really enjoying the many excellent features of view3dscene.</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>> Here are some suggested refinements and improvements.</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>> View3dscene converter: round off significant digits, rather than 10+ decimal places. (For example, suggested values in HAnim spec go to 4 decimal places.</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>> View3dscene: note that we have added ‘description’ field to many nodes in X3D4, including ImageTexture.</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> 1 warnings:</p><p class=MsoNormal>> X3D: Unknown X3D field name (unhandled X3D XML attribute) "description" in node "ImageTexture"</p><p class=MsoNormal>> Scene URL: "C:\x3d-code\www.web3d.org\x3d\content\examples\HumanoidAnimation\Skin\JoeSkeletonSkinSiteSaluteWalk.x3d".</p><p class=MsoNormal>> Use "File->View Warnings" menu to view these warnings again.</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>> Coming soon: import test of three models in HAnim Motion specification.</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> https://www.web3d.org/documents/specifications/19774/V2.0/MotionDataAnimation/MotionDataAnimation.html</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>> Again thanks for great work.</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>> all the best, Don</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> --</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> X3D graphics, virtual worlds, Navy robotics https:// faculty.nps.edu/brutzman</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></body></html>