On Mon Aug 17 20:27:20 2026 +0000, Francisco Casas wrote:
I wouldn't fix the dynamic state validation errors this way, but any other validation errors seem useful to fix. Got it. I removed 2/3 and 3/3 then. It makes sense to eventually fix these with the debug callback. (hi Validation Layer lead here)
saw this on the linux dev discord So yes, this is invalid in the spec {width=695 height=70} But dynamic state has a been full of subtle things like this that we have changed in the pass Like for example, we [discussed before](https://gitlab.khronos.org/vulkan/vulkan/-/issues/4116) ``` vkCmdSetColorWriteEnableEXT(cb, 2, [true, true]); vkCmdSetColorWriteEnableEXT(cb, 1, [false]); ``` On some drivers will cause the `attachment[1]` to turn `false` due to some driver implementations But setting it with zero, **might** be different 1. I went ahead and created an issue in https://github.com/KhronosGroup/Vulkan-Docs/issues (we will go over it our next Wednesday group meeting) 2. There is a chance some driver will go "sorry, we will break if you pass zero" 3. There is a chance that we can write tests and agree that this is valid everywhere -- https://gitlab.winehq.org/wine/wine/-/merge_requests/11688#note_149219