Open kvark opened 11 months ago
Thanks for reporting. This model is using KHR_mesh_quantization
which isn't handled by the reader utility.
The extension is marked as required in the example file, so the library ought report it as unsupported in some way. It begs the question: should the library reject any glTF that has unsupported extensions under extensionsRequired
? In the next release there is an arbitrary extension API, so technically the burden would be passed onto the user.
A short term solution might be to fail creating the Reader
for assets with extensions required matching *_mesh_*
. Obviously, the long-term solution would be to add support for this extension.
https://github.com/gltf-rs/gltf/pull/418 will now report an error if the crate can't handle a particular extension, including this one, so I've rebranded this issue as a feature request to add support for this feature.
Is there no way to bypass the error if I need to use quantization @alteous ?
EDIT: looked at the docs and discovered from_reader_without_validation()
and from_slice_without_validation()
.
I created a PR for this #428
This is happening on "reader.read_positions()".
Example file: Fostral-shape.zip
I suspect this is because gltfPack-0.20 outputs 16-bit integer vertex coordinates by default instead of 32-bit floating points.