renderdoc-gpu-debug

Inspect and debug GPU frame captures with RenderDoc via the rdc-cli command line.

3|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill renderdoc-gpu-debug-jose-polanco-oxte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: renderdoc-gpu-debug
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/graphics/sub-skills/renderdoc-gpu-debug
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill renderdoc-gpu-debug-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rdc-cli, and includes references (resource) components.

What problem does it solve? Debugging rendering artifacts, broken shaders, and GPU performance issues requires deep visibility into frame captures, which is slow and manual through the RenderDoc GUI. This Skill automates capture, inspection, and pixel-level debugging of Vulkan, D3D11, D3D12, and OpenGL frames through the rdc-cli command line. ## Core Features & Use Cases - Frame Capture & Exploration: Capture frames from executables, list draw calls, render passes, and events, and browse the capture through a virtual filesystem. - Pipeline & Shader Inspection: Examine pipeline state (rasterizer, blend, depth-stencil), shader source, disassembly, reflection, and constant buffer values at any draw call. - Pixel-Level Debugging: Query pixel history, pick pixel colors, and trace shader execution line-by-line for pixels, vertices, and compute threads. - Shader Edit-Replay: Modify shaders without recompiling the application, replace them in the capture, and export render targets to verify changes. - Use Case: A user reports broken shadows in their Vulkan renderer. Open the .rdc capture, export the shadow map as a PNG, check depth bias in the rasterizer state, inspect the lighting pass shader constants, and trace a shadowed pixel to find the root cause. ## Quick Start Ask the AI to open your RenderDoc capture file and list the render passes and draw calls to begin investigating a rendering issue.

Frequently Asked Questions about renderdoc-gpu-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a RenderDoc capture from the command line?

Use rdc-cli to open the .rdc file with rdc open, then explore with commands like rdc draws, rdc passes, and rdc pipeline. Export render targets as PNGs with rdc rt and close the session with rdc close when finished.

How to capture a frame from a Vulkan application with RenderDoc?

Run rdc capture -o output.rdc -- /path/to/app from the application's working directory. The RenderDoc Vulkan layer must be registered in HKCU\SOFTWARE\Khronos\Vulkan\ImplicitLayers and ENABLE_VULKAN_RENDERDOC_CAPTURE=1 must be set.

Does RenderDoc support D3D12 and OpenGL debugging?

Yes, rdc-cli works with Vulkan, D3D11, D3D12, and OpenGL captures. The same inspection commands for draws, pipeline state, shaders, and pixel history apply across all supported graphics APIs.

Why does RenderDoc capture fail with no swapchain error?

Headless Vulkan apps without vkQueuePresentKHR cannot be captured because frame boundaries are defined by present calls. Use --trigger mode with manual rdc capture-trigger, an interactive windowed mode, or the Python API via capture_frame.py.

How do I find why a pixel renders the wrong color?

Run rdc pixel X Y to get the pixel history showing which draws wrote to it, then use rdc pick-pixel and rdc debug pixel EID X Y --trace to step through shader execution. Check bound textures, constant buffers, and blend state for the responsible draw.

Can I edit shaders without recompiling my application?

Yes, extract shader source with rdc shader --source, edit the file, build it with rdc shader-build, and swap it in using rdc shader-replace. Export the render target to verify the change, then restore originals with rdc shader-restore-all.