GPU Debug Scopes
wunkolo.github.io
GPU Debug Scopes
1–8 of 8 posts
Re: GPU Debug Scopes
#2What are other cross platform (as in cross-GPU) tools other than RenderDoc that can show GPU debug info?
I found Microsoft Pix, but it's not very useful for Vulkan except showing some performance counters.
Re: GPU Debug Scopes
#3What are other cross platform (as in cross-GPU) tools other than RenderDoc that can show GPU debug info? I found Microsoft Pix, but it's not very useful for Vulkan except showing some performance counters.
Just RenderDoc really. PIX is DirectX only, and everything else is vendor specific.
I don't really know why you wouldn't just use your vendor's tooling though. The only thing I use RenderDoc for is I find debugging with it a bit easier than NSight when I need to find a problem, but for anything performance related I use NSight (and would use PIX as well if Nvidia didn't gimp it).
Oh also Intel's IGA I've found to be very buggy as well, so I avoid that.
Re: GPU Debug Scopes
#4Cool to see how the Vulkan and OpenGL implementations differ. Also did not ever expect to see Paint Roller on HN.
Re: GPU Debug Scopes
#5What are other cross platform (as in cross-GPU) tools other than RenderDoc that can show GPU debug info? I found Microsoft Pix, but it's not very useful for Vulkan except showing some performance counters.
Just RenderDoc really. PIX is DirectX only, and everything else is vendor specific. I don't really know why you wouldn't just use your vendor's tooling though. The only thing I use RenderDoc for is I find debugging with it a bit easier than NSight when I need to find a problem, but for anything performance related I use NSight (and would use PIX as well if Nvidia didn't gimp it). Oh also Intel's IGA I've found to be…
What's AMD's equivalent to Renderdoc these days?
Re: GPU Debug Scopes
#6Earlier quoted context omitted.
Just RenderDoc really. PIX is DirectX only, and everything else is vendor specific. I don't really know why you wouldn't just use your vendor's tooling though. The only thing I use RenderDoc for is I find debugging with it a bit easier than NSight when I need to find a problem, but for anything performance related I use NSight (and would use PIX as well if Nvidia didn't gimp it). Oh also Intel's IGA I've found to be…
What's AMD's equivalent to Renderdoc these days?
To my knowledge they don’t offer a frame debugger any more
Re: GPU Debug Scopes
#7Earlier quoted context omitted.
Just RenderDoc really. PIX is DirectX only, and everything else is vendor specific. I don't really know why you wouldn't just use your vendor's tooling though. The only thing I use RenderDoc for is I find debugging with it a bit easier than NSight when I need to find a problem, but for anything performance related I use NSight (and would use PIX as well if Nvidia didn't gimp it). Oh also Intel's IGA I've found to be…
What's AMD's equivalent to Renderdoc these days?
AMD has some tools for debugging performance related issues called Radeon GPU Profiler/Analyzer and gfxreconstruct (mainly just a replay tool, but can help when comparing across cards), but for debugging shaders running incorrectly on our hardware we use and support both render doc and Microsoft PIX.
Re: GPU Debug Scopes
#8What are other cross platform (as in cross-GPU) tools other than RenderDoc that can show GPU debug info? I found Microsoft Pix, but it's not very useful for Vulkan except showing some performance counters.
Just RenderDoc really. PIX is DirectX only, and everything else is vendor specific. I don't really know why you wouldn't just use your vendor's tooling though. The only thing I use RenderDoc for is I find debugging with it a bit easier than NSight when I need to find a problem, but for anything performance related I use NSight (and would use PIX as well if Nvidia didn't gimp it). Oh also Intel's IGA I've found to be…
Tools may be vendor specific but they're still portable. I use Intel GPA on my AMD card with no issues, I just don't get the extra counters and features Intel GPUs might get.