Hi, and thanks for reporting those issues
We are currently working on those problems and should incorporate them in our processing pipeline soon, but as you have pointed out there are indeed some models which don’t pass the validation phase, for multiple kind of reasons.
Although the animations (DUPLICATE_CHANNELS and NON_INCREASING errors) can indeed be problematic in a pipeline (but will be fixed soon), most of the ACCESSOR_NON_UNIT validation errors appear in buffers associated with tangents, and often on degenerate geometries (which are not necessarily cleaned in every file).
As your pipeline is automated, you can therefore safely override the severity level of those in a config.yml file, as explained here for now, or recompute the primitives’ tangent spaces on your own if needed to pass the validation test.
Some, if not most, of the “INVALID_FLOAT” error messages are also due to bad tangents linked to the previous error, and should therefore be treated accordingly if the “accessor_non_unit” error is detected.
Two points I’d like to emphasize:
- Although the models uploaded after those changes should in theory comply with a “strict” glTF validator, we can not guarantee that oldest ones will be reprocessed soon, and some of them might still fail some of the validation steps as we have not always been 100% strict with the glTF validation (mostly due to the diversity of files and software that we support).
- If you encounter some recurrent glTF errors other than the ones mentioned above and that you think are truly corrupting the glTF, do not hesitate to share them with us as you just did in this thread (error with some of the models impacted). Such feedbacks are of course welcome, and can help us detect some behaviors we would have otherwise missed !
Thanks again for the report !