Domingos Dellamonica Jr., PhD

> As far as I understand, neither version 2 nor version 3 of the Image API make any assumptions about the order of `sizes`. This is my understanding as well....

Would serializing the scene with .toJSON work for you? For the full scene, [the JSON file](https://dotproductstaging.blob.core.windows.net/uploads/scene.json?sv=2023-01-03&st=2024-02-22T15%3A57%3A20Z&se=2024-02-29T15%3A57%3A00Z&sr=b&sp=r&sig=BZLn8u6RyYGPVhrBLVPsPkmqDdNbGjQEm%2FcliudtpZw%3D) is ~185Mb. I loaded the saved scene* and could reproduce the bug with it....

OK, I'll try a much smaller scene, but I'll need some time to prepare code + data. Please bear with me.

Here's a small project. [repro.zip](https://github.com/gkjohnson/three-gpu-pathtracer/files/14389905/repro.zip) There are fewer textures to go around, but none of the faces got the right texture.  

OK, so the GTLF exporter is splitting the mesh and that is why it worked then. Do you plan to add support for this? If not, do you have any...

Thanks for the info. It is not a critical feature, I can work with the GLTF step for now. The project is indeed professional and I've just sent a humble...