-
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
Using the same attachment as a color & input attachment for a subpass triggers questionable warnings #10
Comments
Comment by chrisforbes (MIGRATED) Yep, that's pretty awful. To do this properly we need to combine all the constraints on the layout, rather than making a fuss about each constraint individually. |
According to |
AttilioProvenzano-ARM
added a commit
to ARM-software/Vulkan-ValidationLayers
that referenced
this issue
Feb 27, 2020
This commit adds checks regarding: - Store ops for potentially transient images - Framebuffer attachments that should/should not be transient - Clearing attachments after load - Many instanced vertex buffers in a pipeline This corresponds to checks KhronosGroup#8, KhronosGroup#10-11, KhronosGroup#14 and KhronosGroup#32 from PerfDoc.
AttilioProvenzano-ARM
added a commit
to ARM-software/Vulkan-ValidationLayers
that referenced
this issue
Feb 27, 2020
This commit adds checks regarding: - Store ops for potentially transient images - Framebuffer attachments that should/should not be transient - Clearing attachments after load - Many instanced vertex buffers in a pipeline This corresponds to checks KhronosGroup#8, KhronosGroup#10-11, KhronosGroup#14 and KhronosGroup#32 from PerfDoc.
AttilioProvenzano-ARM
added a commit
to ARM-software/Vulkan-ValidationLayers
that referenced
this issue
Feb 27, 2020
This commit adds checks regarding: - Store ops for potentially transient images - Framebuffer attachments that should/should not be transient - Clearing attachments after load - Many instanced vertex buffers in a pipeline This corresponds to checks KhronosGroup#8, KhronosGroup#10-11, KhronosGroup#14 and KhronosGroup#32 from PerfDoc.
AttilioProvenzano-ARM
added a commit
to ARM-software/Vulkan-ValidationLayers
that referenced
this issue
Feb 28, 2020
This commit adds checks regarding: - Store ops for potentially transient images - Framebuffer attachments that should/should not be transient - Clearing attachments after load - Many instanced vertex buffers in a pipeline This corresponds to checks KhronosGroup#8, KhronosGroup#10-11, KhronosGroup#14 and KhronosGroup#32 from PerfDoc.
AttilioProvenzano-ARM
added a commit
to ARM-software/Vulkan-ValidationLayers
that referenced
this issue
Feb 28, 2020
This commit adds checks regarding: - Store ops for potentially transient images - Framebuffer attachments that should/should not be transient - Clearing attachments after load - Many instanced vertex buffers in a pipeline This corresponds to checks KhronosGroup#8, KhronosGroup#10-11, KhronosGroup#14 and KhronosGroup#32 from PerfDoc.
This was referenced Jul 9, 2020
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue by DominikWitczakAMD (MIGRATED)
Friday Oct 21, 2016 at 12:08 GMT
Originally opened as KhronosGroup/Vulkan-LoaderAndValidationLayers#1080
Consider an app which uses a renderpass attachment X both as a color & an input attachment in the same subpass. This triggers the following warnings:
However:
The text was updated successfully, but these errors were encountered: