Gltf-blender-io: KHR_texture_transform support?

[donmccurdy]

It seems that this code has disappeared: https://github.com/KhronosGroup/glTF-Blender-IO/search?q=KHR_texture_transform&unscoped_q=KHR_texture_transform

https://github.com/KhronosGroup/glTF-Blender-IO/commit/2786bbd8de72f48bf66189bca09956b24494f818

[UX3D-nopper]

It just has been moved:

[donmccurdy]

I mean that the term, "KHR_texture_transform" no longer appears anywhere in this codebase, except in the description of that checkbox — the code has accidentally been removed, I think. A test export confirms this isn't working:

[dsinni]

Would definitely love to see this feature. IMHO, if the transforms are displaying in the renderer, it would be amazing (and would make the most sense) if they where exported.

The Texture Coordinate + Mapping + Image Texture configuration seems to be fairly common (so common in fact that Ctrl + T does this automatically with Node Wrangler), so holding out hope that this can be translated effectively in export.

Keep up the great work!

[EtagiBI]

The problem is still present it todays Blender build (Win64, December 10, 01:07:43 - 168a6a4bfc1).

[emackey]

@julienduroure Can you push the latest? Thanks!

Sorry, got my days mixed up. This is already up there.

[donmccurdy]

From Gitter, it sounds like KHR_texture_transform was working for @dsinni. @EtagiBI could you share a screenshot of the material configuration as well, and ensure you've enabled the Texture Transforms export option?

[dsinni]

Yes, I can confirm that it is in fact working.

The original texture contains only 4 tiles along X and Y and I'm scaling by 3 in each direction:

My node graph looks something like this:

[EtagiBI]

@EtagiBI could you share a screenshot of the material configuration as well, and ensure you've enabled the Texture Transforms export option?

Works fine with todays build of Blender. Thanks.