renderdoc

lee/renderdoc

0 Fork 0

mirror of https://github.com/baldurk/renderdoc.git synced 2026-10-08 21:31:36 +00:00

Files

T

baldurk 82a0e055ba Change how replay programs are identified, from filename to sym export

* Instead of checking on the filename, we look for a specially named
  exported symbol somewhere in a module that's already loaded.
* This allows us to mark the python module as a replay program, so if
  it's loaded into the python interpreter it will be able to use the
  replay API.

2017-08-31 18:34:19 +01:00

app

Batch update copyright years everywhere

2017-01-06 12:13:31 +00:00

replay

Change how replay programs are identified, from filename to sym export

2017-08-31 18:34:19 +01: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.