[x3d-public] X3DSingleTextureTransformNode has no concrete nodes. X3DUOM, X3D Schema

[John Carlson]

Yes, I don't understand how that transfers to X3DUOM and then to
MUX3DJS yet.  There's magic there that is not explained.

On Fri, Aug 22, 2025 at 1:17 PM Michalis Kamburelis <
michalis.kambi at gmail.com> wrote:

> X3DSingleTextureTransformNode is an ancestor of 3 nodes in spec:
>
> - TextureTransform (
>
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/texturing.html
> )
>
> - TextureTransform3D (
>
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/texture3D.html
> )
>
> - TextureTransformMatrix3D ( also in
>
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/texture3D.html
> )
>
> So, the X3D spec is correct, from what I can see. We also implement it
> like that in Castle Game Engine. So all 3 nodes above are valid in
> "Appearance.textureTransform" or
> "MultiTextureTransform.textureTransform".
>
> If a particular software / schema is missing above inheritance, this
> shall be fixed indeed, to allow the nodes everywhere they should be.
>
> Regards,
> Michalis
>
> pt., 22 sie 2025 o 20:02 John Carlson via x3d-public
> <x3d-public at web3d.org> napisał(a):
> >
> > Just to be aware, X3DSingleTextureTransformNode has no ConcreteNodes
> implementing it.  This affects X3D JSON, X3DUOM and X3D schema.
> >
> > This especially affects users of MultiTextureTransform.
> >
> > Thanks,
> >
> > John
> >
> >
> >
> > _______________________________________________
> > x3d-public mailing list
> > x3d-public at web3d.org
> > http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250822/16e1d27c/attachment.html>