{"action":"opened","issue":{"url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/issues/390","repository_url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs","labels_url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/issues/390/labels{/name}","comments_url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/issues/390/comments","events_url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/issues/390/events","html_url":"https://github.com/KhronosGroup/Vulkan-Docs/issues/390","id":180861987,"number":390,"title":"Unclear render pass VU for vkCmdExecuteCommands","user":{"login":"krOoze","id":3791331,"avatar_url":"https://avatars.githubusercontent.com/u/3791331?v=3","gravatar_id":"","url":"https://api.github.com/users/krOoze","html_url":"https://github.com/krOoze","followers_url":"https://api.github.com/users/krOoze/followers","following_url":"https://api.github.com/users/krOoze/following{/other_user}","gists_url":"https://api.github.com/users/krOoze/gists{/gist_id}","starred_url":"https://api.github.com/users/krOoze/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/krOoze/subscriptions","organizations_url":"https://api.github.com/users/krOoze/orgs","repos_url":"https://api.github.com/users/krOoze/repos","events_url":"https://api.github.com/users/krOoze/events{/privacy}","received_events_url":"https://api.github.com/users/krOoze/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-10-04T10:55:09Z","updated_at":"2016-10-04T10:55:09Z","closed_at":null,"body":"Render pass restriction from `vkCmdExecuteCommands` VU:\r\n\r\n> If vkCmdExecuteCommands is being called within a render pass instance, any given element of pCommandBuffers must have been recorded with a render pass that is compatible with the current render pass - see Section 7.2, “Render Pass Compatibility”\r\n\r\nIt is unclear what \"recorded with a render pass\" means. I suggest it should mention `VkCommandBufferInheritanceInfo::renderPass`. (It was similarly fixed for the `subpass` parameter in 1.0.14, but this somehow remained.)\r\n\r\nIt would be made clear with fixing the above, but I would also object to the \"recorded with\" (used here and few other places to refer to `vkBeginCommandBuffer()`'s parameters). To cite the spec:\r\n\r\n> Commands are recorded into a command buffer by calling API commands of the form `vkCmd*`. \r\n\r\n `vkBegin*()` commands do not start with `Cmd`.\r\nAlso they switch the buffer to a recording state, which itself cannot be considered recorded operation (or it would be replayed on each submission)."}}
{"actor":{"display_login":"krOoze"}}