renderdoc

mirror of https://github.com/baldurk/renderdoc.git synced 2026-07-29 02:41:08 +00:00

Files

T

baldurk 9460fbd970 Add feature to globally hook processes to inject indirectly.

* This allows you to hook into processes that are difficult to launch
  directly with the existing functionality in RenderDoc.
* This is rather risky, as it modifies the AppInit_DLLs registry key to
  inject a small shim dll that checks for the desired process and injects
  the full renderdoc.dll. If that registry key got left, or if there was
  some incompatibility with the shim dll, you could have problems. It
  should only ever be used as a last resort if there's no other way to
  capture.

2014-10-05 13:57:11 +01:00

app

Add feature to globally hook processes to inject indirectly.

2014-10-05 13:57:11 +01:00

replay

Add feature to globally hook processes to inject indirectly.

2014-10-05 13:57:11 +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.