You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is in vkFormatString and isValidFormat so ktx info and ktx validate should be fine as these are the functions they use for printing the name and checking validity. vk2dfd however produces nothing for this format. makevk2dfd.pl needs to be fixed and some tests added. Once that is fixed the code in unittests.cc to avoid running the bytesPlane0 test for this format must be removed.
There is no intention to support this in ktx create except via raw files.
The text was updated successfully, but these errors were encountered:
This includes a new round-trip test of vk2dfd and dfd2vk for all Vulkan
formats except multi-plane and modifications to both functions, or
rather their generators, to fix support for some formats, including
VK_FORMAT_R16G16_S10_5_NV and the YUV 4:2:2 single plane formats. Those
listed required changes to`interpretDFD`.
Fixes#859.
Co-authored-by: Andrew Garrard <[email protected]>
Over in KhronosGroup/KTX-Specification#206 we've decided to support this format.
It is in
vkFormatString
andisValidFormat
soktx info
andktx validate
should be fine as these are the functions they use for printing the name and checking validity.vk2dfd
however produces nothing for this format.makevk2dfd.pl
needs to be fixed and some tests added. Once that is fixed the code inunittests.cc
to avoid running the bytesPlane0 test for this format must be removed.There is no intention to support this in
ktx create
except via raw files.The text was updated successfully, but these errors were encountered: