Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] VerifyAccessorBounds does not support component type other than FLOAT #231

Closed
hu-xd opened this issue Apr 16, 2024 · 3 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@hu-xd
Copy link

hu-xd commented Apr 16, 2024

First:
glTF Validator and BabylonJs Sandbox reports no errors for the glb model file.

Description:
when Accessor has a component type other than FLOAT, for example 5121 (UNSIGNED_BYTE),
which is used as RGB / RGBA for "COLOR_0", VerifyAccessorBounds will report error, then ModelRoot.Load throws.

  • OS: Windows
  • SharpGLTF Version alpha-0031
@hu-xd hu-xd added the bug Something isn't working label Apr 16, 2024
@vpenades
Copy link
Owner

Do you have a model I can use for testing?

@hu-xd
Copy link
Author

hu-xd commented Apr 17, 2024

yes here it is a sample gltf model
https://gist.github.com/hu-xd/d9c4ec6268bad598e1b92e2ca50f299e

@hu-xd
Copy link
Author

hu-xd commented Apr 17, 2024

Exception message:
SharpGLTF.Validation.DataException: Accessor[2] memory: Value[0] is out of bounds. 255 <= 1 <= 255 (Parameter 'memory')Model generated by <> seems to be malformed; Please, check the file at https://github.khronos.org/glTF-Validator/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants