mirror of
https://github.com/baldurk/renderdoc.git
synced 2026-10-08 13:21:45 +00:00
* To remove renderdoc (e.g. if the API version doesn't match what is expected), user code can call RENDERDOC_Shutdown() to remove the running thread and undo any library hooks, then unload the dynamic library. * This still isn't recommended as there could be unexpected side-effects, and it will definitely break if this happens after any APIs have been initialised, but it's an option.
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.