three-gltf-viewer VS glTF-Blender-IO

i tested it on https://gltf-viewer.donmccurdy.com/ now and it showed well with texture and all features...

Check if the file is correct first via https://gltf-viewer.donmccurdy.com

If you're unfamiliar with glTF, it is a more modern 3D content format developed by the Khronos Group. Windows has a built-in viewer, but unfortunately the renderer it uses makes all the models look like they were dipped in gloss. I often use: https://gltf-viewer.donmccurdy.com/

Does the animation play correctly when you open the model in a viewer like https://sandbox.babylonjs.com/ or https://gltf-viewer.donmccurdy.com/ ? If so, the problem is likely related to your three.js code, and you may have better luck asking on the [three.js forums](https://discourse.threejs.org/).

In blender and in windows 3d viewer it shows up clean and as intended, but in a glb viewer like gltf viewer ( which works the same as shopify , same errors)

Not much to go on, but maybe your scene doesn't have lighting. Try loading the glb with gltf-viewer or gltf.report

Does it look the same in gltf-viewer? Does the textures tab show the correct images on gltf.report?

Drop it in gltf-viewer or try importing it in Blender to make sure. I feel it's much more likely you're just getting a cached version. If it turns out to be the case, just keep devtools open and tick 'Disable cache' on the Network tab

gltf-viewer is best for just viewing scenes: Its UI is dead simple, you can navigate, choose cameras, playing animations, it meets the viewing needs, and... If you think about it, a web app is ideal, because new extensions are being officially ratified into gltf as time goes on. In a month or so it'll have gpu instance meshes, before long there'll be materialx... and I can't even name a non-web viewer that supports files with mesh compression or even gpu compressed textures yet. With a web app you can be sure it's up to date and should support features before they are even widely used

[1] https://github.com/KhronosGroup/glTF-Blender-IO/issues/1913

I found this GitHub issue which describes exactly the same problem, except it's for glTF export rather than FBX. It was fixed by adding an "Optimize animations" setting that you can disable in the export menu, but there's no such setting for FBX export.

If not, you would need to share the `.blend` file, or to report a bug on the [Blender glTF addon](https://github.com/KhronosGroup/glTF-Blender-IO/issues). The screenshots look fine, but it's not possible to guess this issue from just screenshots.

If you happen to be using the newer version of glTF-Blender-IO from github, they did add support for arbitrary vertex attributes, but you still have to obey the rules of gltf materials so you will not be able to export a material that uses arbitrary vertex attributes. A material like that would need to be implemented in your engine

this document is super valuable: https://docs.blender.org/manual/en/latest/addons/import_export/scene_gltf2.html it tells you all the maps that can be exported and how.

Gltf export documentation is here : https://docs.blender.org/manual/en/latest/addons/import_export/scene_gltf2.html

The way to be sure you can export the content is to read up on what the export format is capable of. This manual page about the glTF exporter is awesome, you really can't hope for better than that

It looks like there's a bit of politics around the Microsoft/DDS support in the glTF addon. They don't want to support it, because apparently it's not up to standards. However, this thread mentions a fork that does support this method.

Materials won't export to an intermediary file format like glTF unless you follow the instructions in the Blender manual that outline what limitations you need to work within. If you ignore those limits then the material data is discarded.