You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During parsing of glTF Images that store their data in a data URI, the latter is discarded. Only images that reference an external file keep their URI, see
Therefore, when one uses a custom image loader that leaves image.image empty, the image data cannot be loaded later from the original data URI.
To Reproduce
OS
Compiler, compiler version, compile options
Please attach minimal and reproducible .glTF file if you got an issue related to .glTF data
Expected behaviour
The image's URI should not be discarded if it is not loaded into image.image
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
We are using a custom image loaderto avoid loading images into memory, since our models have Gigabytes of images. Naturally then the custom image writer needs to have access to the original image data. But the original image.uri has been lost during parsing.
The text was updated successfully, but these errors were encountered:
Describe the issue
During parsing of glTF Images that store their data in a data URI, the latter is discarded. Only images that reference an external file keep their URI, see
tinygltf/tiny_gltf.h
Line 4398 in 10b23b6
Therefore, when one uses a custom image loader that leaves
image.image
empty, the image data cannot be loaded later from the original data URI.To Reproduce
Expected behaviour
The image's URI should not be discarded if it is not loaded into
image.image
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
We are using a custom image loaderto avoid loading images into memory, since our models have Gigabytes of images. Naturally then the custom image writer needs to have access to the original image data. But the original image.uri has been lost during parsing.
The text was updated successfully, but these errors were encountered: