renderdoc

mirror of https://github.com/baldurk/renderdoc.git synced 2026-07-18 21:47:13 +00:00

Files

T

baldurk 3f8e2e7f99 Change the check for when copyRange/destroyRange can be trivially done

* Even if a struct isn't trivial (e.g. it contains a constructor) it can still
  be trivially copyable (just POD with memcpy), or trivially destructable (with
  no destructor). Make sure we don't fall back to slower copies/destroys for
  this case as it's relatively common.

2019-01-22 18:48:07 +00:00

app

Add DiscardFrameCapture to in-application API, bumped to version 1.4.0

2019-01-08 11:35:48 +00:00

replay

Change the check for when copyRange/destroyRange can be trivially done

2019-01-22 18:48:07 +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.