Whenever I export a glb, it won’t export correctly unless “copy textures to output” is checked, and it generates a bunch of copies of the assigned textures to the exported folder. I would like to embed the textures into the glb without generating these textures. An example of what happens if it isn’t checked is textures won’t show up at all, and the mesh will appear white.
This is in Maya, correct?
Looking at this, the behavior is somewhat strange.
I think at the very least, we shouldn’t write the individual texture files to disk when exporting to .glb. Disabling it only seems to work for .babylon export, as gltf and glb export appears to ignore this setting.
Yeah this is in Maya 2019.
1 Like
Great! our texture export code is…messy to put it lightly, but I think I’ll have a fix soon. I just need to validate that I haven’t broken any paths we use for exporting glTF textures.
Fix is checked in 
Awesome!
1 Like
I think the last change may have broken something. I am making content for the new Adobe Aero app on ios, and while the glb’s exported with your latest update look fine in Babylon sandbox viewer, they do not work in Adobe Aero, and load with “missing texture” checker patterns on them. Older animations exported with past versions of Babylon still have their textures so I don’t think it is the Aero app. Something has changed where it isn’t recognizing the textures. I will revert to an older Aero app to see if it fixes anything.
Update: Older stabler versions of Aero do not fix the problem. Some data is being lost with the newer version of Babylon.
Can you help by diffing a working gltf vs a non-working one? I assume that Aero may be stumbling over relatively pathing to the same directory for a GLTFImage.
I reverted to babylon version 20191108.5 from november 8th 2019 somewhat arbitrarily and it worked, the glb exported with all the generated textures again, and the app has them.