lee/renderdoc
1
0
Fork 0
mirror of https://github.com/baldurk/renderdoc.git synced 2026-05-29 13:20:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add a reference to where unstripped shader info is detailed

Browse Source
This commit is contained in:
baldurk
2016-05-16 15:42:42 +02:00
parent 6c24932746
commit e922e85aa3
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/how/how_debug_shader.rst
+3 -1
View File
@@ -6,7 +6,9 @@ This page goes into detail about how to set up your captures for debugging shade
Including debug info in shaders
-------------------------------
For the most part at least some debug information is included with shaders unless it is being explicitly stripped out at some point. There is usually an option to also include additional debug information - such as original source code in a high-level language. The exact process varies by API, but for D3D11 the flag ``/Zi`` to fxc or the equivalent flag to D3DCompile() will include additional debugging information, and ``/Qstrip_debug`` and ``/Qstrip_reflection`` will remove reflection information that can be useful - such as the names of variables in constant buffers.
For the most part at least some debug information is included with shaders unless it is being explicitly stripped out at some point. There is usually an option to also include additional debug information - such as original source code in a high-level language. The exact process varies by API, but for D3D11 the flag ``/Zi`` to fxc or the equivalent flag to ``D3DCompile()`` will include additional debugging information, and ``/Qstrip_debug`` and ``/Qstrip_reflection`` will remove reflection information that can be useful - such as the names of variables in constant buffers.
For more information on how to get this unstripped debug information to renderdoc, see :ref:`unstripped-shader-info`.
Debugging a vertex
------------------