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
Describe the bug
Using any of the kinc_g4_texture_init_*() functions on my debian 11 + vulkan machine will result in a vulkan error message (see below)
To Reproduce
Update Kinc in the Texture-Kinc and run.
Running with Vulkan validation layers enabled.
Chosen Vulkan device: Quadro K2200
Failed to find extension VK_KHR_format_feature_flags2
Vulkan ERROR: Code -1094930823 : Validation Error: [ VUID-VkImageCreateInfo-imageCreateMaxMipLevels-02251 ] Object 0: handle = 0x55555ad66c78, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xbebcae79 | vkCreateImage(): Format VK_FORMAT_R8G8B8A8_UNORM is not supported for this combination of parameters and VkGetPhysicalDeviceImageFormatProperties returned back VK_ERROR_FORMAT_NOT_SUPPORTED. The Vulkan spec states: Each of the following values (as described in Image Creation Limits) must not be undefined imageCreateMaxMipLevels, imageCreateMaxArrayLayers, imageCreateMaxExtent, and imageCreateSampleCounts (https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/vkspec.html#VUID-VkImageCreateInfo-imageCreateMaxMipLevels-02251)
The text was updated successfully, but these errors were encountered:
My computer doesn't run into this problem (Windows/Vulkan/3080Ti) so I reverted the relevant change for now. But can you please check what VK_IMAGE_USAGE_STORAGE_BIT exactly caused the problem in Backends/Graphics5/Vulkan/.../texture.c.h?
Looks like cee6b0e is working. I reverted back to 3fa0f4e to get the error again, but I'm not quite sure what you're asking me to check. Here are some debug infos, hope that helps.
Describe the bug
Using any of the kinc_g4_texture_init_*() functions on my debian 11 + vulkan machine will result in a vulkan error message (see below)
To Reproduce
Update Kinc in the Texture-Kinc and run.
Execution Environment:
The text was updated successfully, but these errors were encountered: