Alexey Knyazev

Another rationale. Endpoints, selectors, and tables are internal implementation details of the BasisLZ codec and have no meaning in the broad KTX context. On the other hand, slice offsets are...

By "eager decoder initialization" I mean decompressing Huffman tables. They are completely self-contained and could be decoded in parallel even before anything else is ready. By "knowing levels/faces/etc configuration" I...

> the wrap and filter properties are optional in glTF The wrapping is always defined in glTF. By default, it is _repeat_ when the sampler object or its wrapping parameters...

The GPU sampler state properties may be grouped like this: ### Wrapping - up to three independent axes (U/V/W); - normalized / unnormalized coordinates; - five wrapping options: - repeat;...

With regards to the topic of storage, i.e., external/embedded ANSI/IES LM-63 data vs JSON-inlined parameters, I think we need to consider the following two issues. #### ANSI/IES LM-63 Lifecycle The...

> We would actually want to support all versions: IESNA91, IESNA:LM-63-1995, IESNA:LM-63-2002, IES:LM-63-2019. IIRC, there was also a 1986 version that did not have a version identifier inside at all....

It's true that only Khronos-ratified extensions are covered by the Khronos IP framework. In all other cases, extension authors/contributors should be contacted directly to clarify IP-related issues. For these two...

Yes. They should either put exact terms or provide relevant contact information. Extension IP usually includes, but not limited to: - License for the extension specification including text, images, code...

@MarkCallow WebP has both lossy and lossless modes so we may consider adding it as a supported input format if there's enough demand.

- As of today, WebP is indeed the best non-GPU-compressed format for asset distribution. Not so much for DCC workflows due to limited tooling, although it's getting better. - Users...