Arseny Kapoulkine

@MarkCallow Two biggest issues were no mip-map generation support and no JPEG conversion support.

> But perhaps in view of all the jpeg images produced by digital cameras I should revisit that. Since glTF supports PNG and JPEG, I would expect any tool that...

Here's an Avocado model built with new padding rules as per https://github.com/KhronosGroup/KTX-Specification/pull/117 [Avocado-newpadding.zip](https://github.com/KhronosGroup/glTF/files/4173933/Avocado-newpadding.zip)

Yeah this looks like a bug in transcoder. The Basis transcoder has the same code as Mark quoted: ``` std::vector dst_data; ... emscripten::val memory = emscripten::val::module_property("HEAP8")["buffer"]; emscripten::val memoryView = emscripten::val::global("Uint8Array").new_(memory,...

Yeah - both issues are one and the same. I've fixed both in this branch by fixing the transcoder: https://github.com/zeux/three.js/tree/feat-ktx2loader You can grab the .js/.wasm from this branch, and I'll...

https://github.com/KhronosGroup/KTX-Software/pull/175

gltfpack (which I'd recommend as the reference compressor for EXT_meshopt_compression) disables filters on the time track. When uniform sampling is used for animation, there's no real need for the filters...

This is a great illustration! It would make sense to me to add something like this as an example. Note that the extension is intentionally not specifying the *exact* method...

(1) is what is intended in the spec. You can use KHR_texture_transform to correct this to any desired range. I can submit a PR to clarify that (I think this...

FWIW I understand that integer texture coordinates may seem weird but the motivation behind this extension in general is to decouple storage format from the interpretation a bit more. So...