renderdoc

lee/renderdoc

0 Fork 0

mirror of https://github.com/baldurk/renderdoc.git synced 2026-10-12 23:29:26 +00:00

Files

T

baldurk b070a371e2 Improve D3D11 predication handling, and track other asyncs independently

* Instead of replaying predication, we now always skip it during replay,
  so all objects will render. This is much more consistent and
  understandable behaviour instead of things mysteriously disappearing
  with no obvious reason why.
* We track the predication that would have happened and replay Begin/End
  pairs so that we can know if the predication *would* have failed.
* This is displayed in the UI (currently in the raster state, for lack
  of a better location) with the pass/fail that would have happened.
* This information can feed into other places for analysis like the
  pixel history.

2017-12-20 23:41:08 +00:00

app

Add a helper macro for obtaining renderdoc's handle from VkInstance

2017-10-23 13:43:38 +01:00

replay

Improve D3D11 predication handling, and track other asyncs independently

2017-12-20 23:41:08 +00:00

README.md

…

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.