From 4847a2e8761c9aafc06754a3afaf574d97924659 Mon Sep 17 00:00:00 2001 From: baldurk Date: Thu, 12 Nov 2015 14:25:12 +0100 Subject: [PATCH] Move stepping into vkCmdExecuteCommands to post-1.0 * The solution I have in mind for this will just be too much churn and large changes like that should be avoided at this point. --- ReleaseNotes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ReleaseNotes.md b/ReleaseNotes.md index 756310e55..9c184d5fb 100644 --- a/ReleaseNotes.md +++ b/ReleaseNotes.md @@ -26,7 +26,6 @@ Known Issues * Memory/image barriers are as yet unverified, potentially could lead to bad capture or replay. * Sparse images with mips or array slices will not properly replay -* Stepping inside vkCmdExecuteCommands * Only 2D non-array non-integer textures can currently be displayed. * Auto texture range-fit or histogram display is not implemented. * Debug overlays other than drawcall highlight and wireframe aren't implemented. @@ -41,6 +40,7 @@ Future work, post 1.0 In no particular order, features that are not planned until after 1.0. * More than one VkInstance/VkDevice/VkQueue triple +* Stepping inside vkCmdExecuteCommands * Support for replaying captures on a different machine to where they were captured * Shader debugging * Pixel history