Mark Callow

Is there something blocking you from creating your own such functions using the switch code generated by https://github.com/KhronosGroup/KTX-Specification/blob/main/generate_format_switches.rb from the .json file you referenced? Nevertheless it may not be unreasonable...

> Spec clarification desired: Is a similar clarification needed for KHR_texture_basisu? > The metalness values are sampled from the B channel. The roughness values are sampled from the G channel....

> No. The recommendation is to prefer UASTC over ETS1S for ORM textures; the former provides enough quality to not worry much about cross-channel artifacts. Okay. Indeed the ASTC spec...

I encountered a similar problem with `ubuntu-latest` which is now Ubuntu 24.04. In my case it tells me it can't find `mono`. As in the case reported here, it tells...

I think this is more properly a bug against the 24.04 runner for not having the necessary packages. `ubuntu-22.04` has `mono-complete` and `libldtl-dev` installed which I needed and had to...

> I think this is more properly a bug against the 24.04 runner for not having the necessary packages. See https://github.com/actions/runner-images/issues/12342.

Why do you say current key-value storage is not practical? Generically values can be nul-terminated utf-8 strings. Are XML and JSON-LD not utf-8? Specifically what do you want to add...

@lexaknyazev I see no problem adding `KTXxmp`. Please provide a PR.

> Draft says to use colorModel KHR_DF_MODEL_UASTC_HDR (= 167) together with vkFormat VK_FORMAT_ASTC_4x4_SFLOAT_BLOCK (= 1000066000). Any issues with that? @lexaknyazev please let me know your opinion on this as soon...

A version of https://github.com/BinomialLLC/basis_universal/wiki/UASTC-HDR-Texture-Specification-v1.0 needs to be incorporated into the Data Format Specification. That document has two parts: a description of the UASTC HDR subset of ASTC and a description...