<div dir="ltr"><div>Thanks Holger.</div><div><br></div><div>a. I was not able to figure out who the original creator was from the README files or github history - "Microsoft" perhaps? Appreciate your upgrading this.</div><div><br></div><div>b. Commented out undefined field in ImageTexture: <!-- colorSpaceConversion='false' --></div><div><br></div><div>c. Was CannonExterior.avif used in this model, or should it be deleted?</div><div><ul><li><a href="https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/CannonExterior.avif">https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/CannonExterior.avif</a></li></ul></div><div>d. Changed X3D version to 4.1 since Tangent node is present</div><div><br></div><div>e. Once again looks identical in X_ITE and Castle. 👍</div><div><br></div><div>f. This was an important example to finally get added because it revealed important gaps in X3D XML Schema and DOCTYPE. Now updated, along with X3DUOM, X3DJSAIL, and X3D Ontology with X3DPSAIL x3d.py to follow.</div><div><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">11 JAN 2026, brutzman, seelig<br>- (v4.0, v4.1) MultiTextureTransform can also contain TextureTransform3D and<br> TextureTransformMatrix3D in addition to TextureTransform</blockquote><div><ul><li> X3D Specifications: Schema and DOCTYPE Validation</li><li><a href="https://www.web3d.org/specifications">https://www.web3d.org/specifications</a></li></ul></div></div><div>g. Hopefully the publication efforts and metadata look good. Published in version control and online at</div><div><ul><li>X3D Example Archives: X3D4AM, X3D for Advanced Modeling, Gltf Sample Models, Sheen Cloth</li><li>MultiTexture model converted from glTF</li><li><a href="https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/SheenClothIndex.html">https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/SheenClothIndex.html</a></li></ul><div>Have fun with advanced rendering using
X3D! 😀</div></div><div><br></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div style="color:rgb(34,34,34)"><font face="monospace">all the best, Don</font></div><div style="color:rgb(34,34,34)"><font face="monospace">-- </font></div><div style="color:rgb(34,34,34)"><font face="monospace">X3D Graphics, Maritime Robotics, Distributed Simulation</font></div><div style="color:rgb(34,34,34)"><font face="monospace">Relative Motion Consulting <a href="https://RelativeMotion.info" target="_blank">https://RelativeMotion.info</a></font></div></div></div></div><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Sun, Jan 11, 2026 at 12:30 PM Holger Seelig <<a href="mailto:holger.seelig@yahoo.de">holger.seelig@yahoo.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:13px"><div></div>
<div dir="ltr"><div><div dir="ltr">Here is a very simple example with only one shape that uses MultiTextureTransform (two different TextureTransformMatrix3D nodes) and MultiTextureCoordinate (where both TextureCoordinate node are actually the same). I have added a SheenCloth.x3d, converted with X_ITE. I have modified the original conversion file to make it work in Castle Model Viewer (removed the SheenMaterialExtension node, added proper NavigationInfo and Viewpoint, added MultiTextureCoordinate because Castle needs this, X_ITE uses the last TextureCoordinate if a mapping does not match). I attached the whole folder with all textures and the converted file SheenCloth.x3d.</div><div><br></div><div>This file is originally from the glTF-Sample-Assets from Khronos:</div><div><a href="https://github.com/KhronosGroup/glTF-Sample-Assets/tree/main/Models/SheenCloth" target="_blank">https://github.com/KhronosGroup/glTF-Sample-Assets/tree/main/Models/SheenCloth</a></div><div><br></div></div><div>Best regards,</div><div dir="ltr">Holger</div></div><div><br></div>
</div><div id="m_7123313597087370416yahoo_quoted_9154627677">
<div style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:13px;color:rgb(38,40,42)">
<div>
Am Sonntag, 11. Januar 2026 um 04:45:19 MEZ hat Don Brutzman <<a href="mailto:don.brutzman@gmail.com" target="_blank">don.brutzman@gmail.com</a>> Folgendes geschrieben:
</div>
<div><br></div>
<div><br></div>
<div><div id="m_7123313597087370416yiv5491415234"><div><div dir="ltr"><div dir="ltr"><div>[cc: x3d-public since this topic has ballooned to be much bigger than originally expected]</div><div><br clear="none"></div><div>Background: working on putting two of Michalis' Castle Model Viewer examples for X3D 4.1 Tangent node into the X3D Example Archives.</div><div><ul><li>X3D Example Archives: X3D4AM, X3D for Advanced Modeling, Gltf Sample Models, Cat By Muru</li><li><a rel="nofollow noopener noreferrer" shape="rect" href="https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/CatByMuruIndex.html" target="_blank">https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/CatByMuruIndex.html</a></li><li><a rel="nofollow noopener noreferrer" shape="rect" href="https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/CatByMuruX_ITE.html" target="_blank">https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/CatByMuruX_ITE.html</a></li></ul>and<br clear="none"><ul><li>X3D Example Archives: X3D4AM, X3D for Advanced Modeling, Gltf Sample Models, Halloween Pumpkin Lantern Knight</li><li><a rel="nofollow noopener noreferrer" shape="rect" href="https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/HalloweenPumpkinLanternKnightIndex.html" target="_blank">https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/HalloweenPumpkinLanternKnightIndex.html</a></li><li><a rel="nofollow noopener noreferrer" shape="rect" href="https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/HalloweenPumpkinLanternKnightX_ITE.html" target="_blank">https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/HalloweenPumpkinLanternKnightX_ITE.html</a></li></ul></div><div>=================</div><div><br clear="none"></div><div>Continuing, mostly finishing this long thread:</div><div><br clear="none"></div><div>Thanks Holger for the TextureTransform technique. I have applied that change in two models (CatByMuru.x3d and HalloweenPumpkinLanternNight.x3d to good effect.</div><div><br clear="none"></div><div>Have also added the following tooltip.</div><div><ul><li>X3D Tooltips: TextureTransform</li><li><a rel="nofollow noopener noreferrer" shape="rect" href="https://www.web3d.org/x3d/content/X3dTooltips.html#TextureTransform" target="_blank">https://www.web3d.org/x3d/content/X3dTooltips.html#TextureTransform</a></li></ul></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px"><div><div>Hint: image flip horizontal <TextureTransform DEF='FlipHorizontal' scale='-1 1' translation='-1 0'/></div></div><div><div>Hint: image flip vertical <TextureTransform DEF='FlipVertical' scale='1 -1' translation='0 -1'/></div></div><div><br clear="none"></div></blockquote>Noticed that when you apply such a TextureTransform, it is a child of the parent Appearance node, and not part of each ImageTexture (like the CGE attribute). When there is an associated PhysicalMaterial and no mapping field is defined, that means the TextureTransform applies to all of the ImageTexture fields (baseTexture, emissiveTexture, metallicRoughnessTexture, normalTexture, occlusionTexture). Similarly for UnlitMaterial.</div><div dir="ltr"><br clear="none"></div><div>Michalis, should I leave mapping="" blank throughout, or else apply a value there (perhaps mapping='flipVertical' throughout)?</div><div dir="ltr"><br clear="none"></div><div dir="ltr">We don't appear to mention this case explicitly in the specification, but I think the prose is OK and does not allow any other interpretation. (We can add more words for clarity if anyone wants to.)</div><div dir="ltr"><ul><li>X3D Architecture version 4.1 draft, clause 12 Shape component12.2.2 Appearance characteristics</li><li><a rel="nofollow noopener noreferrer" shape="rect" href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/shape.html#AppearanceCharacteristics" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/shape.html#AppearanceCharacteristics</a></li></ul><div dir="ltr">Also thanks Michalis, I have added generateMipMaps='true' to TextureProperties nodes, and handled DEF/USE.</div><div dir="ltr"><ul><li><TextureProperties DEF='AveragePixel' generateMipMaps='true' magnificationFilter='AVG_PIXEL' minificationFilter='AVG_PIXEL_AVG_MIPMAP'/></li></ul><div>HalloweenPumpkinLanternKnight.x3d model is too large for X3DJSAIL to load, unfortunately (currently 2.6MB) and so I was not able to reduce the extra-long floats in there (no more than 7 digits of precision are needed).</div><div><br clear="none"></div><div>Michalis, the character</div><table style="font-size:12.7px;background-color:rgb(248,249,250);color:rgb(0,0,0);margin:1em 0px;border-width:0px 1px 1px 0px;border-style:solid;border-color:rgb(170,170,170);border-spacing:0px;font-family:sans-serif"><tbody><tr><td colspan="1" rowspan="1" style="border-width:1px 0px 0px 1px;border-style:solid;border-color:rgb(170,170,170);padding:0.2em 0.4em"><span style="font-family:monospace,monospace">dollar;</span></td><td colspan="1" rowspan="1" style="border-width:1px 0px 0px 1px;border-style:solid;border-color:rgb(170,170,170);padding:0.2em 0.4em"><a rel="nofollow noopener noreferrer" shape="rect" href="https://en.wikipedia.org/wiki/$" title="$" style="color:rgb(0,43,184);background:none;text-decoration-line:none" target="_blank">$</a></td><td colspan="1" rowspan="1" style="border-width:1px 0px 0px 1px;border-style:solid;border-color:rgb(170,170,170);padding:0.2em 0.4em"><a rel="nofollow noopener noreferrer" shape="rect" href="https://en.wikipedia.org/wiki/Basic_Latin_(Unicode_block)" title="Basic Latin (Unicode block)" style="color:rgb(0,43,184);background:none;text-decoration-line:none" target="_blank">U+</a>0024</td></tr></tbody></table>is not within the range allowed for XML NMTOKEN (name token) data type, and so it is not recommended for X3D model interoperability across all file encodings and programming-language bindings. See </div><div dir="ltr"><ul><li>XML Recommendation, v1.1 (Second edition), World Wide Web Consortium (W3C), 2.3 Common Syntactic Constructs, Names and Tokens</li><li><a rel="nofollow noopener noreferrer" shape="rect" href="https://www.w3.org/TR/xml11/#sec-common-syn" target="_blank">https://www.w3.org/TR/xml11/#sec-common-syn</a></li></ul></div><div dir="ltr">DEF/USE, proto and other names in X3D Example Archive models are always conservative for best interoperability, additional suggestions always welcome. Further details are maintained at</div><div dir="ltr"><ul><li>X3D Scene Authoring Hint, NamingConventions</li><li><a rel="nofollow noopener noreferrer" shape="rect" href="https://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#NamingConventions" target="_blank">https://www.web3d.org/x3d/content/examples/X3dSceneAuthoringHints.html#NamingConventions</a></li></ul><div>Giving a node DEF='head' is legal, but it is confusing for the XML encoding, so I usually change things like that for clarity... which is often essential in the X3D Example Archives. Not sure if we should add 'head' to the list of reserved words.</div><div><br clear="none"></div><div><b>Both the CatByMuru and HalloweenPumpkinLanternKnight models are looking good and looking consistent, both for Castle Model Viewer and X_ITE/Playground/Sunrize. Bravo!</b></div><div><br clear="none"></div><div>X3DOM looks quite different (perhaps differing application of PBR textures in Physical Material node). Perhaps someone wants to work on that open-source codebase... examples in the X3dForAdvancedModeling GltfSampleModels directly provide a lot of excellent test cases for glTF compatibility, with many others working already.</div><div><br clear="none"></div></div><div>New issue: since multiple TextureTransform nodes might be needed within an Appearance, should we allow multiple TextureTransform nodes in Appearance? Right now that is an SFNode field. If you think there is a use case that an author (or converter) would want more than one TextureTransform in the Appearance node, please advise.</div><div><ul><li>12.4.2 Appearance</li><li><a rel="nofollow noopener noreferrer" shape="rect" href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/shape.html#Appearance" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4.1-CD/Part01/components/shape.html#Appearance</a></li></ul><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><pre style="color:rgb(0,0,0);font-size:11.05px;margin-left:25px">Appearance : X3DAppearanceNode {
SFNode [in,out] acousticProperties NULL [AcousticProperties]
SFFloat [in,out] alphaCutoff 0.5 [0,1]
SFString [in,out] alphaMode "AUTO" ["AUTO", "OPAQUE", "MASK", "BLEND"]
SFNode [in,out] backMaterial NULL [X3DOneSidedMaterialNode]
SFNode [in,out] fillProperties NULL [FillProperties]
SFNode [in,out] lineProperties NULL [LineProperties]
SFNode [in,out] material NULL [X3DMaterialNode]
SFNode [in,out] metadata NULL [X3DMetadataObject]
SFNode [in,out] pointProperties NULL [PointProperties]
MFNode [in,out] shaders [] [X3DShaderNode]
SFNode [in,out] texture NULL [X3DTextureNode]
<span style="background-color:rgb(255,255,0)">SFNode</span> [in,out] textureTransform NULL [X3DTextureTransformNode]
}</pre></blockquote></div></div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div style="color:rgb(34,34,34)"><font face="arial, sans-serif">Have fun using glTF models in X3D! 😀</font></div><div style="color:rgb(34,34,34)"><font face="monospace"><br clear="none"></font></div><div style="color:rgb(34,34,34)"><font face="monospace">all the best, Don</font></div><div style="color:rgb(34,34,34)"><font face="monospace">-- </font></div><div style="color:rgb(34,34,34)"><font face="monospace">X3D Graphics, Maritime Robotics, Distributed Simulation</font></div><div style="color:rgb(34,34,34)"><font face="monospace">Relative Motion Consulting <a rel="nofollow noopener noreferrer" shape="rect" href="https://RelativeMotion.info" target="_blank">https://RelativeMotion.info</a></font></div></div></div></div><br clear="none"></div><br clear="none"><div id="m_7123313597087370416yiv5491415234yqt84296"><div><div dir="ltr">On Sun, Jan 4, 2026 at 1:11 PM Holger Seelig <<a rel="nofollow noopener noreferrer" shape="rect" href="mailto:holger.seelig@yahoo.de" target="_blank">holger.seelig@yahoo.de</a>> wrote:<br clear="none"></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Instead of a flipVertically field, it is also possible to achieve this with a TextureTransform node<div><br clear="none"></div><div>DEF FlipVertically TextureTransform {</div><div> translation 0 -1</div><div> scale 1 -1</div><div>}</div><div><br clear="none"></div><div>Another solution is to flip all texture coordinates (y’ = 1 - y). </div><div><br clear="none"></div><div>After all investigations I think that Castle and X_ITE are on the right way representing glTF textures, but all the examples miss a flipVertically in either way.</div><div><br clear="none"></div><div>Best regards,</div><div>Holger</div><div><br clear="none" id="m_7123313597087370416yiv5491415234m_101065893907288755lineBreakAtBeginningOfMessage"><div>
<div style="color:rgb(0,0,0);letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="color:rgb(0,0,0);letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="color:rgb(0,0,0);letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="color:rgb(0,0,0);letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="color:rgb(0,0,0);letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="color:rgb(0,0,0);letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="color:rgb(0,0,0);letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="color:rgb(0,0,0);letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="color:rgb(0,0,0);letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="color:rgb(0,0,0);letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="text-indent:0px"><div style="color:rgb(0,0,0);letter-spacing:normal;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">—</div><div style="color:rgb(0,0,0);letter-spacing:normal;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">Holger Seelig<br clear="none"><a rel="nofollow noopener noreferrer" shape="rect" href="mailto:holger.seelig@yahoo.de" target="_blank">holger.seelig@yahoo.de</a><br clear="none"><br clear="none"></div></div></div></div></div></div></div></div></div></div></div></div>
</div>
<div><br clear="none"><blockquote type="cite"><div>Am 04.01.2026 um 01:32 schrieb Michalis Kamburelis <<a rel="nofollow noopener noreferrer" shape="rect" href="mailto:michalis.kambi@gmail.com" target="_blank">michalis.kambi@gmail.com</a>>:</div><br clear="none"><div><div dir="ltr">Hello Don,<br clear="none"><br clear="none">Great, thanks for the analysis of the file and tests on other browsers! Answers:<br clear="none"><br clear="none"><div>1. flipVertically:</div><div><br clear="none"></div><div> - This is documented on <a rel="nofollow noopener noreferrer" shape="rect" href="https://castle-engine.io/x3d_implementation_texturing_extensions.php#section_flip_vertically" target="_blank">https://castle-engine.io/x3d_implementation_texturing_extensions.php#section_flip_vertically</a> , with reasons why.</div><div><br clear="none"></div><div> - We talked about it in the past on x3d-public already.</div><div><br clear="none"></div><div> - No, I don't think now that it deserves to be added to spec. Let it remain CGE extension. CGE should export with TextureTransform making this "flipVertically" unnecessary, and the files spec-conforming. Implementing this by "flipVertically" in CGE is just an optimization (see link above), effectively, since it's zero overhead to flip at loading. I feel it can remain CGE extension, actually.</div><div><br clear="none"></div><div> - So, give me time, I'll fix these models to not use flipVertically :)</div><div><br clear="none"></div><div>2. $ in name:</div><div><br clear="none"></div><div> - I was under impression that $ is actually OK inside name in X3D. We use it in special situations (when "encoding" names with arbitrary chars from other formats) deliberately.</div><div><br clear="none"></div><div> - Spec <a rel="nofollow noopener noreferrer" shape="rect" href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19776-2v4.0-WD1/Part02/grammar.html" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19776-2v4.0-WD1/Part02/grammar.html</a> about "IdRestChars" implies $ is OK. ("$" is 0x24), from what I can tell.</div><div><br clear="none"></div><div> - CGE code derived from this is <a rel="nofollow noopener noreferrer" shape="rect" href="https://github.com/castle-engine/castle-engine/blob/7dccdbb455d544e3659d6f049cde9bcf428c3c86/src/scene/load/x3dloadinternalutils.pas#L82" target="_blank">https://github.com/castle-engine/castle-engine/blob/7dccdbb455d544e3659d6f049cde9bcf428c3c86/src/scene/load/x3dloadinternalutils.pas#L82</a> .</div><div><br clear="none"></div><div> - So: Are you sure "$" is not valid in X3D name? Where is this mentioned in spec? If that's the case -> no problem, I'll fix our code, and the test models.</div><div><br clear="none"></div><div>3. """Wondering why you have those EXPORT statements"""</div><div><br clear="none"></div><div> - Our glTF->X3D converter EXPORTs some named nodes, to allow animation of them by the outer X3D file.</div><div><br clear="none"></div><div> - In short, it doesn't matter for these particular examples, these EXPORTS are not used in this case.</div><div><br clear="none"></div><div>4. """<Transform DEF='head'/> has DEF name that illegally overrides a reserved word from the X3D Specification"""</div><div><br clear="none"></div><div> - I was not aware that such names are disallowed.</div><div><br clear="none"></div><div> - "head" is not mentioned as keyword on <a rel="nofollow noopener noreferrer" shape="rect" href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19776-2v4.0-WD1/Part02/grammar.html" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19776-2v4.0-WD1/Part02/grammar.html</a> . </div><div><br clear="none"></div><div> - It's not used by classic encoding, it's only an element name in X3D XML. I don't see how node name "head" could be really confused with element <head> in X3D?</div><div><br clear="none"></div><div> - That said, we could fix the model (and CGE converter). Can you show me where in the specification is the "head" for node name disallowed? I can add a logic to our converter to avoid "head" name then.</div><div><br clear="none"></div><div>5. """<TextureProperties DEF=''/> requires generateMipMaps='true' since minificationFilter='AVG_PIXEL_AVG_MIPMAP""""</div><div><br clear="none"></div><div> - I'll fix it, indeed spec says "Mipmaps are required for filtering modes with MIPMAP in their value."</div><div><br clear="none"></div><div> - Note that CGE ignores this field. Only the filtering determines whether we need mipmaps... so to us, generateMipMaps field is actually not useful.</div><div><br clear="none"></div><div> - (And it could be confusing in case of files like DDS or KTX, where mipmaps are part of the image. In such case, we have mipmaps, we use them -> but we don't "generate" them).</div><div><br clear="none"></div><div> - Anyhow, that's all minor notes :) We can just place generateMipMaps='true'.</div><div><br clear="none"></div><div>6. About the float precision: We have a --float-precision option to Castle Model Converter, it was just not used for this. I can indeed reexxport this with smaller precision.</div><div><br clear="none"></div><div>Summary: Give me time :) and I'll fix</div><div><br clear="none"></div><div>- AD 1 - flipVertically</div><div>- AD 5- generateMipMaps</div><div>- AD 6 - float precision</div><div><br clear="none"></div><div>in the models. </div><div><br clear="none"></div><div>For 2 other questions, I'll appreciate a link to spec :), but of course we could also adjust to them, nothing problematic there :) This applies to:</div><div><br clear="none"></div><div>- AD 2 - $ in name</div><div>- AD 4 - "head" in name</div><div><br clear="none"></div><div>Regards,</div><div>Michalis</div></div><br clear="none"><div><div dir="ltr">sob., 3 sty 2026 o 07:11 Don Brutzman <<a rel="nofollow noopener noreferrer" shape="rect" href="mailto:don.brutzman@gmail.com" target="_blank">don.brutzman@gmail.com</a>> napisał(a):<br clear="none"></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><span style="font-family:arial,sans-serif">Thank you very much for recovering those, Michalis!</span></div><div><div dir="ltr"><div dir="ltr"><div style="color:rgb(34,34,34)"><font face="arial, sans-serif"><br clear="none"></font></div><div style="color:rgb(34,34,34)"><font face="arial, sans-serif">I copied all three and put originals in version control, and began work on first. Next step, ran/committed .x3d version through X3D Canonicalization (C14N) so that any changes which occur are evident. Also added a variety of meta tags.</font></div><div style="color:rgb(34,34,34)"><font face="arial, sans-serif"><br clear="none"></font></div><div style="color:rgb(34,34,34)"><font face="arial, sans-serif">Validation diagnostics quickly found the following errors:</font></div><div style="color:rgb(34,34,34)"><ul><li>Attribute "flipVertically" must be declared for element type "ImageTexture". (now omitted, may look funny)</li><li>Attribute value "CastleEncoded_Pose_scene$46$fbx" of type IDREF must be an NCName when namespaces are enabled. (changed $ character to underscore _ character)</li></ul><div>If you would like to add <i>flipVertical </i>and <i>flipHorizontal </i>attributes to ImageTexture, or to interface X3DSingleTextureNode (ImageTexture, MovieTexture, PixelTexture), please propose that on x3d-public mail list. Seems plausible to me, if glTF has something like that then let's do it consistently. No need to add "ly" suffix to names of such boolean fields. If everyone reaches consensus (or interest at least) then I can add them to XML DOCTYPE and Schema for draft version 4.1.</div><div><br clear="none"></div><div>Continued work on other diagnostics...</div><div><br clear="none"></div><div>Wondering why you have those EXPORT statements?</div><div><br clear="none"></div><div>Got illegal DEF name warning, renamed 'head' to 'modelHead'</div><div><ul><li><Transform DEF='head'/> has DEF name that illegally overrides a reserved word from the X3D Specification [/X3D/Scene/Transform/Transform/Transform/Transform[1], error]<br clear="none"></li></ul></div><div>Got several X3D Schematron warnings like this, do you agree?</div><div><ul><li><TextureProperties DEF=''/> requires generateMipMaps='true' since minificationFilter='AVG_PIXEL_AVG_MIPMAP' mode indicates MIPMAP rendering [/X3D/Scene/Transform/Transform/Transform/Transform[1]/Transform/Group/Shape/Appearance/PhysicalMaterial/ImageTexture[4]/TextureProperties, error]</li><li>looks like those three nodes are identical might be single DEF with one USE</li></ul></div><div>Got a Schematron warning to take advantage of DEF/USE, and so did that.</div><div><ul><li><ImageTexture DEF=''/> url array address(es) duplicate the url definition found in a preceding node, consider DEF/USE to reduce download delays and memory requirements for url content (url='"textures/lambert2_metallicRoughness.png" "<a rel="nofollow noopener noreferrer" shape="rect" href="https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/textures/lambert2_metallicRoughness.png" target="_blank">https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/textures/lambert2_metallicRoughness.png</a>"') [/X3D/Scene/Transform/Transform/Transform/Transform[1]/Transform/Group/Shape/Appearance/PhysicalMaterial/ImageTexture[4], warning]</li><li>provided DEF, USE ='MetallicRoughness' while preserving containerField values</li></ul></div><div>Gave it a white background for better visibility.</div><div><br clear="none"></div><div>Added identifying WorldInfo.</div><div><br clear="none"></div><div>When I ran the model through X3DJSAIL to reduce precision from 15 digits to 8 digits after decimal point, file size went from 867KB to 471KB. I think we can safely go down to 6 digits (micrometer resolution). Such reduction is valuable for large models, converters can have a switch for lossless/lossy conversion as an option.</div><div><br clear="none"></div><div>Now online at</div><div><ul><li>X3D Example Archives: X3D4AM, X3D for Advanced Modeling, Gltf Sample Models, Cat By Muru Scene</li><li>Converted glTF model showing use of Tangent node</li><li><a rel="nofollow noopener noreferrer" shape="rect" href="https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/CatByMuruSceneIndex.html" target="_blank">https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/GltfSampleModels/CatByMuruSceneIndex.html</a></li></ul><div>Castle and X_ITE look similar, X3DOM looks quite different (likely differing application of PBR textures).</div></div><div><br clear="none"></div><div><span id="m_7123313597087370416yiv5491415234m_101065893907288755cid:ii_mjxwhv4c0"><image.png></span><br clear="none"></div><div><span id="m_7123313597087370416yiv5491415234m_101065893907288755cid:ii_mjxwj8su1"><image.png></span><br clear="none"></div><div></div><div><br clear="none"></div><span id="m_7123313597087370416yiv5491415234m_101065893907288755cid:ii_mjxwlag83"><image.png></span><br clear="none"></div><div style="color:rgb(34,34,34)"><font face="monospace"><br clear="none"></font></div><div style="color:rgb(34,34,34)"><font face="monospace">all the best, Don</font></div><div style="color:rgb(34,34,34)"><font face="monospace">-- </font></div><div style="color:rgb(34,34,34)"><font face="monospace">X3D Graphics, Maritime Robotics, Distributed Simulation</font></div><div style="color:rgb(34,34,34)"><font face="monospace">Relative Motion Consulting <a rel="nofollow noopener noreferrer" shape="rect" href="https://relativemotion.info/" target="_blank">https://RelativeMotion.info</a></font></div></div></div></div><br clear="none"></div></div></div><br clear="none"><div><div dir="ltr">On Fri, Jan 2, 2026 at 5:05 PM Michalis Kamburelis <<a rel="nofollow noopener noreferrer" shape="rect" href="mailto:michalis.kambi@gmail.com" target="_blank">michalis.kambi@gmail.com</a>> wrote:<br clear="none"></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I provided 3 sample models using Tangent in my answer to Don in<br clear="none">
thread "[x3d-public] Specification review progress: PNG3, Tangent<br clear="none">
node, HAnim weekly progress" on July :)<br clear="none">
<br clear="none">
See <a rel="nofollow noopener noreferrer" shape="rect" href="https://github.com/castle-engine/demo-models/tree/master/bump_mapping/tangents" target="_blank">https://github.com/castle-engine/demo-models/tree/master/bump_mapping/tangents</a><br clear="none">
. It's probably easiest to "git clone" the whole repository<br clear="none">
<a rel="nofollow noopener noreferrer" shape="rect" href="https://github.com/castle-engine/demo-models" target="_blank">https://github.com/castle-engine/demo-models</a> to have all additional<br clear="none">
files (like textures).<br clear="none">
<br clear="none">
Details:<br clear="none">
<br clear="none">
- They look pretty and have been created by actual artists :) Original<br clear="none">
versions obtained in glTF format from Sketchfab.<br clear="none">
<br clear="none">
- They are on versions of Creative Commons licenses. So it's OK to<br clear="none">
reuse them, if you credit the authors. 2 of them on CC-BY-4.0 (so even<br clear="none">
commercial usage is allowed, you just need to credit the authors). 1<br clear="none">
of them on CC-BY-NC-SA-4.0, so no commercial usage allowed (don't know<br clear="none">
if it's a problem for X3D Examples Archive).<br clear="none">
<br clear="none">
- They were created by converting glTF versions to X3D using Castle<br clear="none">
Model Viewer.<br clear="none">
<br clear="none">
- I removed some CGE extensions from them (they don't contain<br clear="none">
animation in any way, including Skin), but admittedly I didn't test<br clear="none">
them in other browsers. Reports about compatibility with other X3D<br clear="none">
browsers are welcome. If there's anything non-spec-complaint in these<br clear="none">
examples -> let me know and I'll fix it.<br clear="none">
<br clear="none">
- Note that the models only make sense together with all the textures,<br clear="none">
they have textures in "textures/" subdirectory.<br clear="none">
<br clear="none">
- They are also larger files. I recall I tried to create some "more<br clear="none">
minimal" test, but from what I recall they just looked ugly /<br clear="none">
non-sensical :)<br clear="none">
<br clear="none">
Regards and have a great 2026 everyone ! :),<br clear="none">
Michalis<br clear="none">
<br clear="none">
<br clear="none">
<br clear="none">
<br clear="none">
<br clear="none">
pt., 2 sty 2026 o 07:33 Don Brutzman <<a rel="nofollow noopener noreferrer" shape="rect" href="mailto:don.brutzman@gmail.com" target="_blank">don.brutzman@gmail.com</a>> napisał(a):<br clear="none">
><br clear="none">
> happy 2026! i hope everyone is well.<br clear="none">
><br clear="none">
> FYI i have deployed updates and support for draft x3d 4.1 development and will announce soon...<br clear="none">
><br clear="none">
> X3D Specifications: Schema and DOCTYPE Validation<br clear="none">
> <a rel="nofollow noopener noreferrer" shape="rect" href="https://www.web3d.org/specifications" target="_blank">https://www.web3d.org/specifications</a><br clear="none">
><br clear="none">
> I was looking back through prior mail and had trouble finding some examples...<br clear="none">
><br clear="none">
> If any of you have a simple X3D example for FontLibrary, or for Tangent node, I'd be happy to add it to our X3D Examples Archive. This will help me test/confirm all the tools are working OK.<br clear="none">
><br clear="none">
> Appreciate your considering this request, and all your many efforts.<br clear="none">
><br clear="none">
> all the best, Don<br clear="none">
> --<br clear="none">
> X3D Graphics, Maritime Robotics, Distributed Simulation<br clear="none">
> Relative Motion Consulting <a rel="nofollow noopener noreferrer" shape="rect" href="https://relativemotion.info/" target="_blank">https://RelativeMotion.info</a><br clear="none">
</blockquote></div>
</blockquote></div>
</div></blockquote></div><br clear="none"></div></div></blockquote></div></div></div>
</div></div></div>
</div>
</div></div></blockquote></div>