Quick answer: Export a self-contained .glb (binary, embedded buffers and images), or keep the .gltf, .bin, and image files together with intact relative paths.
A glTF that loads geometry but no textures usually lost its image references. The text .gltf format points to images by path, so moving the file, renaming a folder, or losing the .bin sidecar breaks the links and the model imports bare.
How to fix it
1. Prefer .glb for delivery
Export a single binary .glb with buffers and images embedded. One self-contained file cannot lose its sidecars, which is the most common cause of missing textures.
2. Keep sidecar files together
If you must use .gltf, ship the .bin and all image files alongside it with their original relative paths intact. Moving any of them breaks the URIs.
3. Re-resolve textures after import
If links are broken in the engine, reassign the texture files manually or re-export, then confirm the material samples them rather than a default white map.
Catching the ones you can't reproduce
The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.
Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.
This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.
The errors you never hear about are the ones quietly costing you players. Visibility turns them into a worklist.