renderdoc

lee/renderdoc

0 Fork 0

mirror of https://github.com/baldurk/renderdoc.git synced 2026-10-12 07:11:51 +00:00

Files

T

baldurk 0b527fab49 Use rdc types instead of Qt containers in public QRenderDoc interface

* This is to support python bindings - the pyside implementation of
  QVector, QString, etc is not available to SWIG, so SWIG treates these
  all as opaque types.
* Rather than trying to set up bindings that work for rdcarray and
  QList/QVector, or implementing separate bindings, we instead just say
  that the public interface must use the rdc types. In most cases they
  seamlessly convert to/from Qt types anyway.
* In a couple of places we use an array of pairs instead of a map. In
  future we probably want an rdcdict or rdcmap with proper dict bindings
  in python.

2017-12-13 22:43:01 +00:00

app

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

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

replay

Use rdc types instead of Qt containers in public QRenderDoc interface

2017-12-13 22:43:01 +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.