From 10053b8be801cb2a99a916d329a4e5f4f3cb81c8 Mon Sep 17 00:00:00 2001 From: baldurk Date: Mon, 9 Jan 2017 11:42:47 +0000 Subject: [PATCH] Update docs to mention that Vulkan/D3D12 don't support Map() verifying --- docs/getting_started/faq.rst | 2 ++ docs/window/capture_log_attach.rst | 2 ++ 2 files changed, 4 insertions(+) diff --git a/docs/getting_started/faq.rst b/docs/getting_started/faq.rst index e863cb9a9..589813a7c 100644 --- a/docs/getting_started/faq.rst +++ b/docs/getting_started/faq.rst @@ -156,6 +156,8 @@ Yes RenderDoc can be configured to insert a boundary marker at the end of the me To enable this behaviour, select the ``Verify Map() Writes`` option when :doc:`capturing <../window/capture_log_attach>`. +Note this is only supported on D3D11 and OpenGL currently, since Vulkan and D3D12 are lower overhead and do not have the infrastructure to intercept map writes. + RenderDoc is complaining about my OpenGL app in the overlay - what gives? ------------------------------------------------------------------------- diff --git a/docs/window/capture_log_attach.rst b/docs/window/capture_log_attach.rst index ffece90ea..dc5d3e979 100644 --- a/docs/window/capture_log_attach.rst +++ b/docs/window/capture_log_attach.rst @@ -144,6 +144,8 @@ If the application creates a command list early and replays it indefinitely with This option adds checking to any ``Map()`` calls that adds a boundary marker after any ``Map()`` pointer returned during a captured frame. These markers are checked on ``Unmap()`` and if they have been modified a message box will pop up alerting you to this, and you can click Yes to break in the debugger in the target application and investigate the problem. +Note this is only supported on D3D11 and OpenGL currently, since Vulkan and D3D12 are lower overhead and do not have the infrastructure to intercept map writes. + ---------- | ``Auto start`` Default: ``Disabled``