glTF-Validator
glTF-Validator copied to clipboard
Tool to validate glTF assets.
It should test if all attribute accessors in a given node must have the same count. Reference: https://github.com/KhronosGroup/glTF/blob/main/extensions/2.0/Vendor/EXT_mesh_gpu_instancing/README.md
The spec specifically allows morphing of texcoord and color attributes. [Link](https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html#morph-targets) It is also supported by sample viewer. The description in [mesh.primitive.schema.json](https://github.com/KhronosGroup/glTF/blob/main/specification/2.0/schema/mesh.primitive.schema.json) is misleading. I will also raise an issue...
Dart 3.x will be released very soon, mid-2023, with some compatibility-breaking changes. We should look into upgrading the glTF validator to use Dart 3.x or else it will stop running...
This PR makes it possible to provide a list of the only errors we want to validate (opposite of ignoredIssues). In my case I only want to check for 'ACCESSOR_INVALID_FLOAT',...
This is not a bug, but rather a feature request. Along with this information: ```json "animationCount": 1, "materialCount": 1, "hasMorphTargets": true, "hasSkins": false, "hasTextures": true, "hasDefaultScene": true, "drawCallCount": 1, "totalVertexCount":...
In gLTF Specification 2.0.1 it says "Client implementations MAY optionally support morphed TEXCOORD_n and/or COLOR_n attributes." but validator fails to validate these optional attributes.
There are some typical problems that can crop up in models created by users who aren't well-versed in all the best practices for optimizing glTF assets. The validator could issue...
I followed the instruction in https://www.npmjs.com/package/gltf-validator to validate a GLB file. This file has invalid magic value, which can be detected by https://github.khronos.org/glTF-Validator/. But https://www.npmjs.com/package/gltf-validator cannot detect it. Does NPM...
Hi, from the last release some prefixes has been added, exists a way to know when a new glTF-Validator will be released to include those prefixes? Thanks, Luca
It would be helpful if the glTF Validator supported KHR_texture_basisu and mimeType:"image/ktx2". Currently the validator reports multiple Warnings and Infos related to KTX2, and thus does not list the dimensions...