-
Notifications
You must be signed in to change notification settings - Fork 410
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing validation for VkExternalMemoryImageCreateInfo with valid externalFormat #1934
Comments
There are places where VK_KHR_external_memory extension requires that a VkFormat be VK_FORMAT_UNDEFINED. This CL highlights some of those cases but I doubt it is complete or of production quality at this time. Issue: KhronosGroup#1934 Change-Id: I140e5b63cd85acee2697454920e1bd5c10f46d77
Reference CL can be found here: courtney-g@40e10b6 That's not final or complete, just what I changed to get validation happy. I'll leave it to LunarG to provide production code. |
So this was an issue I already have caught and made the internal spec fixes a few weeks ago, but the change is in the 1.x.143 headers which are currently being pulled in (also left a comment explaining this exact issue yesterday) So if you don't mind waiting, once the #1926 gets pulled in, I have a change to fix the whole |
Awesome, that sounds great! |
@spencer, I'm hoping this is unblocked now, yes? |
While adding support to ANGLE for importing external images I ran into validation errors that I don't think are errors.
In particular, I was getting complaints about an invalid VkFormat of VK_FORMAT_UNDEFINED. While it's generally true that having a VkFormat of VK_FORMAT_UNDEFINED is not valid, there are cases when using the VK_KHR_external_memory extension where it's required.
The text was updated successfully, but these errors were encountered: