search

KhronosGroup / glTF

glTF – Runtime 3D Asset Delivery
Other
7.13k stars 1.14k forks source link

KHR_image_ktx2 scheme missing metadata offset & size. #1619

Closed MarkCallow closed 4 years ago

MarkCallow commented 5 years ago

Doesn't it need metadataByteOffset, metadataByteLength, imagesByteLength and uncompressedImagesByteLength?

lexaknyazev commented 5 years ago

I thought that since metadata has JSON representation, there's no need to keep a pointer to its original form. It may be useful for custom keys, so I'll add it.

Considering that levels array has byte lengths for each level, I don't think that we need to keep the aggregates. As a general rule, I'd avoid data redundancy to reduce the number of corner cases.

donmccurdy commented 4 years ago

We are planning to skip the KHR_image_ktx2 extension, and the scheme data mentioned above, and instead rely on the KHR_texture_basisu (as well as potential non-basis IBL extensions) to explicitly allow KTX references from image entries.