Converting my scene to gltf/glb textures wrapping to default

Description of the problem

I am using three js gltf exporter to convert my scene to a gltf/glb format. Everything gets exported nicely except the textures repeat that i have applied. I have a view to change the wrapS and wrapT at run time in the application but after exporting they get reset to default.

Here is the code that changes the textures, and it gets rendered correctly.

let txt = new THREE.TextureLoader().load(color.texture);

txt.repeat.set(color.size[0], color.size[1], color.size[2]);
txt.wrapS = THREE.RepeatWrapping;
txt.wrapT = THREE.RepeatWrapping;

new_mtl = new THREE.MeshPhongMaterial({
    map: txt,
    shininess: color.shininess ? color.shininess : 10
});

parent.traverse((o) => {
    if (o.isMesh && o.nameID != null) {
        if (o.nameID == type) {
            o.material = new_mtl;
            materials[o.uuid] = new_mtl;
        }
    }
});

Here is how it looks in browser: https://imgur.com/eh65Jf4 And when it gets exported and previewed with (https://gltf-viewer.donmccurdy.com/ or https://sandbox.babylonjs.com/): https://imgur.com/bJxm8nI

This is the code I used for exporting model:

exporter.parse(theModel, function (gltf) {
    saveJSON(gltf, 'model.glb');
}, {
    trs: false,
    onlyVisible: true,
    truncateDrawRange: true,
    binary: false,
    forceIndices: false,
    forcePowerOfTwoTextures: true,
    maxTextureSize: 4096,
});

Three.js version

• Dev
• r115

Browser

• All of them
• Chrome
• Firefox
• Internet Explorer

OS

• All of them
• Windows
• macOS
• Linux
• Android
• iOS

Hardware Requirements (graphics card, VR Device, …)

[Mugen87]

You have actually used three.js from release R108 and GLTFLoader and GLTFExporter from release R92. This combination is not allowed. The core and examples files always have to match in their version. After upgrading all files to R115, the export works as expected.

Updated fiddle: https://jsfiddle.net/h2ar4opf/1/

[donmccurdy]

^Filing the issue was my suggestion, it had looked like a bug to me. Glad to hear it was just a version mismatch!