{"action":"created","issue":{"url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/issues/485","repository_url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs","labels_url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/issues/485/labels{/name}","comments_url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/issues/485/comments","events_url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/issues/485/events","html_url":"https://github.com/KhronosGroup/Vulkan-Docs/issues/485","id":220203044,"number":485,"title":"Exposing more debugging/profiling functionality in the next version","user":{"login":"edrickhong","id":17538361,"avatar_url":"https://avatars3.githubusercontent.com/u/17538361?v=3","gravatar_id":"","url":"https://api.github.com/users/edrickhong","html_url":"https://github.com/edrickhong","followers_url":"https://api.github.com/users/edrickhong/followers","following_url":"https://api.github.com/users/edrickhong/following{/other_user}","gists_url":"https://api.github.com/users/edrickhong/gists{/gist_id}","starred_url":"https://api.github.com/users/edrickhong/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/edrickhong/subscriptions","organizations_url":"https://api.github.com/users/edrickhong/orgs","repos_url":"https://api.github.com/users/edrickhong/repos","events_url":"https://api.github.com/users/edrickhong/events{/privacy}","received_events_url":"https://api.github.com/users/edrickhong/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-04-07T12:43:54Z","updated_at":"2017-04-07T13:28:04Z","closed_at":null,"body":"Is it possible to have more debugging facilities in vulkan in the next update? Not so much like the layers, though they are great. I was hoping functionality like being able to step through shaders and the like would be great. Historically, GL has been dependent on vendors to release some kind of debugging tool. Rather than relying solely on the vendor, exposing debugging functionality would greatly benefit the vulkan tools ecosystem. If possible, I'd like it to be in the main spec. \r\n\r\nOn a side note, is VK_NVX_device_generated_commands going to make it in the next version? "},"comment":{"url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/issues/comments/292535994","html_url":"https://github.com/KhronosGroup/Vulkan-Docs/issues/485#issuecomment-292535994","issue_url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/issues/485","id":292535994,"user":{"login":"NicolBolas","id":905466,"avatar_url":"https://avatars0.githubusercontent.com/u/905466?v=3","gravatar_id":"","url":"https://api.github.com/users/NicolBolas","html_url":"https://github.com/NicolBolas","followers_url":"https://api.github.com/users/NicolBolas/followers","following_url":"https://api.github.com/users/NicolBolas/following{/other_user}","gists_url":"https://api.github.com/users/NicolBolas/gists{/gist_id}","starred_url":"https://api.github.com/users/NicolBolas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/NicolBolas/subscriptions","organizations_url":"https://api.github.com/users/NicolBolas/orgs","repos_url":"https://api.github.com/users/NicolBolas/repos","events_url":"https://api.github.com/users/NicolBolas/events{/privacy}","received_events_url":"https://api.github.com/users/NicolBolas/received_events","type":"User","site_admin":false},"created_at":"2017-04-07T13:28:04Z","updated_at":"2017-04-07T13:28:04Z","body":"The specification defines the behavior of the system. Debugging is an issue that happens outside of the Vulkan system's behavior.\r\n\r\nThe reason debugging is dependent on vendors is because debugging is *dependent on vendors*. They're the ones with the hardware, so those are the ones who can actually expose some kind of debugging functionality. They are the gate keepers of the hardware.\r\n\r\nThe best that might be able to happen is that LunarG would get with the vendors and come up with some internal API for exposing debugging functionality. But even that would have to be optional to some degree, because not all vendors have the time or inclination to do so. And Vulkan adoption will not be served by making vendors do *more* work rather than less."}}
{"actor":{"display_login":"NicolBolas"}}