Is there any support for capturing Vulkan profiling info similar to what’s produced by Nsight/CUDA or nvprof or nvvp?
I write a lot of compute shaders that aren’t associated with a swapchain/frame until late in the development cycle and after a large amount of integration.
For this reason, it would be valuable to profile a standalone Vulkan compute shader being launched on a queue.
I suspect many CUDA devs are porting kernels to Vulkan 1.1 now that it has first class support for compute primitives.
Let me know if you need more info.