-
Notifications
You must be signed in to change notification settings - Fork 200
dev.UsingRenderDoc
Thomas Mann edited this page Jan 14, 2024
·
1 revision
If you're developing new effects, debugging with RenderDoc is insanely useful. It looks more intimidating than it is:
It's freeware and you can download the windows version from https://renderdoc.org/builds
After installation, ...
- exit T3.exe, if it's running
- in your IDE (Rider or Visual Studio) use Build → Build Solution
- start RenderDoc
- find the "Launch Application" tab
- setup the Executable Path and Working directory. For me this looks like:
Press [Launch]. Tooll should start in its window. Notice the RenderDoc overlay in the top left corner:
Press F12 to capture a frame. Then find and select the tab called "t3 [PID 12334]" and double click the screenshot of the frame capture:
Select the "Texture Viewer" Tab and then explore the render steps on the left:
The Pipeline state will the give you a detailed overview of what PRECISELY the graphics card did for this frame:
- You can analyze and download(!) all textures
- See and debug all shaders
- Check if an effect was called with the parameters you expected
- Check and analyze and download all relevant structure buffers
Reference
Getting started
- Basic Concepts
- How Tooll Works
- Keyboard shortcuts
- Video tutorials
- Rendering Videos
- Exporting to Executable
- Creating new Operators
- Tooll for live performances
- Presets and Snapshots
- Optimizing Rendering Performance
- Using backups
- Realtime Rendering for Artists
Advanced features