Issues with specifications about ktx-software HOT 4 CLOSED

I assume this is the right place
No, but don't worry. I understand you had problems trying to use the Khronos Bugzilla. I'll add a repo for specification issues and move this issue there once it is set up. I'll fix the issues in a little while.

Congratulations on being the first person to spot the hidden cookie. I am afraid there is no prize.

1. You can find KTX files in https://github.com/KhronosGroup/KTX-Software/tree/master/testimages. You can find some more complex ones, including a cubemap texture in https://github.com/msc-/KTX-Software/tree/incoming/tests/testimages. I'll be moving these to this repo's incoming branch in the near future.

2. The padding bytes can be any value. They are ignored by loaders and are there simply to maintain 4-byte alignment for the imageSize fields.

3. Mobile devices were a major target for KTX. These require that 32-bit values be aligned on 4-byte boundaries. To keep loaders a little simpler we make sure that all 32-bit values in the the KTX file are 4-byte aligned. One does not typically explain this sort of thing in specifications but I suppose I can add a footnote. Isn't "% 4" sufficient clue that this is about modulo 4?

from ktx-software.

Please refile this at https://github.com/KhronosGroup/KTX-Specification/issues and close this one. Sorry to ask but I have not found a way to mark an issue as filed by somebody else or ensure a particular user will receive notifications about updates to the issue.

from ktx-software.

Moved to KhronosGroup/KTX-Specification#1

from ktx-software.

Thanks.

from ktx-software.