<div dir="ltr">For example, from X3DUOM<div><br></div><div><ConcreteNode name="MultiTextureTransform"><br>         <InterfaceDefinition specificationUrl="<a href="https://www.web3d.org/specifications/X3Dv4/ISO-IEC19775-1v4-IS/Part01/components/texturing.html#MultiTextureTransform">https://www.web3d.org/specifications/X3Dv4/ISO-IEC19775-1v4-IS/Part01/components/texturing.html#MultiTextureTransform</a>"<br>                              appinfo="MultiTextureTransform contains multiple TextureTransform nodes, each provided for use by corresponding ImageTexture MovieTexture or PixelTexture nodes within a sibling MultiTexture node."><br>            <componentInfo name="Texturing" level="2"/><br>            <Inheritance baseType="X3DTextureTransformNode"/></div><div><br></div><div>[ snip ]</div><div><br></div><div>            <field name="textureTransform"<br>                   type="MFNode"<br>                   accessType="inputOutput"<br>                   acceptableNodeTypes="X3DSingleTextureTransformNode"<br>                   description="Zero or more contained TextureTransform nodes, for each of the different texture channels, that define 2D transformation applied to texture coordinates."/></div><div><br></div><div>[ snip ]</div><div><br></div><div>            <containerField default="textureTransform" type="xs:NMTOKEN"/><br>            <ContentModel><br>               <GroupContentModel name="ChildContentModelCore" minOccurs="0"/>                                                                                                                      <NodeContentModel name="TextureTransform"/><br>               <NodeContentModel name="ProtoInstance"/>                                                                                                                                          </ContentModel></div><div><br></div><div><br></div><div><br></div><div>===========================================================================</div><div><br></div><div>What I would like to see is more acceptableNodetypes on the textureTransform field, however that's accomplished!</div><div><br></div><div><br></div><div>Thanks!</div><div><br></div><div>John</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Aug 22, 2025 at 1:18 PM John Carlson <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</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 dir="ltr"><div>I think that X3D XML schema may have something, but I don't understand transfer to X3DUOM yet.</div><div><br></div><div>Help is desired.</div><div><br></div><div>Thanks,</div><div><br></div><div>John</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 22, 2025 at 1:01 PM John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</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 dir="ltr">Just to be aware, X3DSingleTextureTransformNode has no ConcreteNodes implementing it.  This affects X3D JSON, X3DUOM and X3D schema.<div><br></div><div>This especially affects users of MultiTextureTransform.</div><div><br></div><div>Thanks,</div><div><br></div><div>John<br><div><br></div><div><br></div><div><br></div></div></div>
</blockquote></div></div>
</blockquote></div>