Skip to content
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

Validation: using 3d image view as render target does not trigger an error #71

Closed
karl-lunarg opened this issue May 14, 2018 · 1 comment
Assignees
Labels
Incomplete Missing Validation VUs to be added
Milestone

Comments

@karl-lunarg
Copy link
Contributor

Issue by TiemoJung (MIGRATED)
Thursday Mar 22, 2018 at 15:42 GMT
Originally opened as KhronosGroup/Vulkan-LoaderAndValidationLayers#2507


Hi,

as the description says, having a 3d image view of a 3d image and using this view as render target does not trigger any errors.

Tested with 1.1.69.0.rc.334

@karl-lunarg karl-lunarg added this to the P1 milestone May 14, 2018
@KarenGhavam-lunarG KarenGhavam-lunarG added Incomplete Missing Validation VUs to be added and removed incomplete labels Sep 3, 2018
@daveh-lunarg
Copy link
Contributor

I'm having a hard time finding spec language that explicitly forbids this. VkImageType is not mentioned in either VkAttachmentDescription or VkRenderPassCreateInfo(2), AFAICT. It's probably not what the user intended, arguably. It might just end up with a frame rendered into slice 0 of the 3D image?

It's not unlikely I've just missed the statement or inference chain that prohibits this - if so please point to it and re-open the issue. Otherwise I'll add this as a warning for the assistant layer, #24.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Incomplete Missing Validation VUs to be added
Projects
None yet
Development

No branches or pull requests

4 participants