renderdoc

lee/renderdoc

0 Fork 0

mirror of https://github.com/baldurk/renderdoc.git synced 2026-10-17 01:29:19 +00:00

Files

T

baldurk 6487acdf0f Fail to capture if Create*PipelineState has no valid shader code

* This typically means that the user hasn't checked correctly for SM6 feature
  support before trying to upload DXIL shader, which will then result in
  unpredictable behaviour or crashes on replay.
* During capture we detect this and flag it in the overlay text, and prevent
  capturing. On capture load we fail to load if we detect such a PSO.

2019-06-27 10:22:13 +01:00

app

Update copyright years to 2019

2019-02-01 18:32:13 +00:00

replay

Fail to capture if Create*PipelineState has no valid shader code

2019-06-27 10:22:13 +01:00

README.md

Re-organise external-facing headers to be more easily used

2014-09-13 12:52:25 +01:00

README.md

This folder can be extracted out and placed into your source tree if you want to use RenderDoc.

If you want to access RenderDoc while it's injected into your program, the app/ folder is what you want. This also contains functions for injecting RenderDoc into existing or new processes.
If you want to write a program that utilises RenderDoc's replay and analysis capabilities (e.g. writing a new UI, or an auto-testing/offline analysis tool), the replay/ folder is what you want.

You will need both folders if you want to launch processes with RenderDoc injected.