Move graphics diagnostics docs to a new subdir (#264)

Author: BrianPeek

docs/debugger/0x-2x-4x-msaa-variants.md

@@ -1,90 +1,3 @@
 ---
-title: "0x-2x-4x MSAA Variants | Microsoft Docs"
-ms.custom: ""
-ms.date: "11/04/2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology: 
-  - "vs-ide-debug"
-ms.tgt_pltfrm: ""
-ms.topic: "article"
-ms.assetid: 668a6603-5082-4c78-98e6-f3dc871aa55b
-caps.latest.revision: 8
-author: "mikejo5000"
-ms.author: "mikejo"
-manager: "ghogen"
-translation.priority.ht: 
-  - "cs-cz"
-  - "de-de"
-  - "es-es"
-  - "fr-fr"
-  - "it-it"
-  - "ja-jp"
-  - "ko-kr"
-  - "pl-pl"
-  - "pt-br"
-  - "ru-ru"
-  - "tr-tr"
-  - "zh-cn"
-  - "zh-tw"
----
-# 0x/2x/4x MSAA Variants
-Overrides multi-sample anti-aliasing (MSAA) settings on all render targets and swap chains.  
-  
-## Interpretation  
- Multi-sample anti-aliasing increases visual quality by taking samples at multiple locations in each pixel; greater levels of MSAA take more samples, and without MSAA, only one sample is taken from the pixel's center. Enabling MSAA in your app usually has a modest but noticeable cost in rendering performance, but under certain workloads or on certain GPUs, it can be had with almost no impact.  
-  
- If your app already has MSAA enabled, then the lesser MSAA variants indicate the relative performance cost that the existing, higher-level MSAA incurs. In particular, the 0x MSAA variant indicates the relative performance of your app without MSAA.  
-  
- If your app doesn't already have MSAA enabled, then the 2x MSAA and 4x MSAA variants indicate the relative performance cost of enabling them in your app. When the cost is acceptably low, consider enabling MSAA to enhance the image quality of your app.  
-  
-> [!NOTE]
->  Your hardware might not fully support MSAA for all formats. If any of these variants encounter a hardware limitation that can't be worked around, its column in the performance summary table is blank and an error message is produced.  
-  
-## Remarks  
- These variants override the sample count and sample-quality arguments on calls to `ID3DDevice::CreateTexture2D` that create render targets. Specifically, these parameters are overridden when:  
-  
--   The `D3D11_TEXTURE2D_DESC` object passed in `pDesc` describes a render target; that is:  
-  
-    -   The BindFlags member has either the D3D11_BIND_TARGET flag or D3D11_BIND_DEPTH_STENCIL flag set.  
-  
-    -   The Usage member is set to D3D11_USAGE_DEFAULT.  
-  
-    -   The CPUAccessFlags member is set to 0.  
-  
-    -   The MipLevels member is set to 1.  
-  
--   The device supports the requested sample count (0, 2, or 4) and sample quality (0) for the requested render target format (D3D11_TEXTURE2D_DESC::Format member), as determined by `ID3D11Device::CheckMultisampleQualityLevels`.  
-  
- If the D3D11_TEXTURE2D_DESC::BindFlags member has the D3D_BIND_SHADER_RESOUCE or D3D11_BIND_UNORDERED_ACCESS flags set, then two versions of the texture are created; the first has these flags cleared for use as the render target, and the other is a non-MSAA texture that has these flags left intact to act as a resolve buffer for the first version. This is necessary because using an MSAA texture as a shader resource or for unordered access is unlikely to be valid—for example, a shader acting on it would generate incorrect results because it would expect a non-MSAA texture. If the variant has created the secondary non-MSAA texture, then whenever the MSAA render target is unset from the device context, its contents are resolved into the non-MSAA texture. Likewise, whenever the MSAA render target should be bound as a shader resource, or is used in an unordered access view, the resolved non-MSAA texture is bound instead.  
-  
- These variants also override MSAA settings on all swap chains created by using `IDXGIFactory::CreateSwapChain`, `IDXGIFactory2::CreateSwapChainForHwnd`, `IDXGIFactory2::CreateSwapChainForCoreWindow`, `IDXGIFactory2::CreateSwapChainForComposition`, and `ID3D11CreateDeviceAndSwapChain`.  
-  
- The net effect of these changes is that all rendering is done to an MSAA render target, but if your application uses one of these render targets or swap-chain buffers as a shader resource view or unordered access view, then data is sampled from the resolved, non-MSAA copy of the render target.  
-  
-## Restrictions and limitations  
- In Direct3D11, MSAA textures are more restricted than non-MSAA textures. For example, you can't call `ID3D11DeviceContext::UpdateSubresource` on an MSAA texture, and calling `ID3D11DeviceContext::CopySubresourceRegion` fails if the sample count and sample quality of the source resource and destination resource don't match, which can occur when this variant overrides the MSAA settings of one resource but not the other.  
-  
- When playback detects these kinds of conflicts, it makes a best effort to replicate the intended behavior, but it might not be possible to match its results exactly. Although it's uncommon for this to affect the performance of these variants in a way that misrepresents their impact, it is possible—for example, when flow control in a pixel shader is determined by the precise content of a texture—because the replicated texture might not have identical contents.  
-  
-## Example  
- These variants can be reproduced for render targets created by using `ID3D11Device::CreateTexture2D` by using code like this:  
-  
-```  
-D3D11_TEXTURE2D_DESC target_description;  
-target_description.BindFlags = D3D11_BIND_RENDER_TARGET;  
-target_description.SampleDesc.Count = 4; // 4x MSAA, can be 2 or 0 instead  
-target_description.SampleDesc.Quality = 0;  
-d3d_device->CreateTexture2D(&target_description, nullptr, &render_target);  
-```  
-  
-## Example  
- Or for swap chains created by using IDXGISwapChain::CreateSwapChain or D3D11CreateDeviceAndSwapChain by using code like this:  
-  
-```  
-DXGI_SWAP_CHAIN_DESC chain_description;  
-chain_description.SampleDesc.Count = 4; // 4x MSAA, can be 2 or 0 instead  
-chain_description.SampleDesc.Quality = 0;  
-  
-// Call IDXGISwapChain::CreateSwapChain or D3D11CreateDeviceAndSwapChain, etc.  
-```
+redirect_url: /visualstudio/debugger/graphics/0x-2x-4x-msaa-variants
+---

docs/debugger/16bpp-render-target-format-variant.md

@@ -1,68 +1,3 @@
 ---
-title: "16bpp Render Target Format Variant | Microsoft Docs"
-ms.custom: ""
-ms.date: "11/04/2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology: 
-  - "vs-ide-debug"
-ms.tgt_pltfrm: ""
-ms.topic: "article"
-ms.assetid: 24b22ad9-5ad0-4161-809a-9b518eb924bf
-caps.latest.revision: 5
-author: "mikejo5000"
-ms.author: "mikejo"
-manager: "ghogen"
-translation.priority.ht: 
-  - "cs-cz"
-  - "de-de"
-  - "es-es"
-  - "fr-fr"
-  - "it-it"
-  - "ja-jp"
-  - "ko-kr"
-  - "pl-pl"
-  - "pt-br"
-  - "ru-ru"
-  - "tr-tr"
-  - "zh-cn"
-  - "zh-tw"
----
-# 16bpp Render Target Format Variant
-Sets the pixel format to DXGI_FORMAT_B5G6R5_UNORM for all render targets and back buffers.  
-  
-## Interpretation  
- A render target or back buffer typically uses a 32bpp (32 bits per pixel) format such as B8G8R8A8_UNORM. 32bpp formats can consume a lot of memory bandwidth. Because the B5G6R5_UNORM format is a 16bpp format that's half the size of 32bpp formats, using it can relieve pressure on memory bandwidth, but at the cost of reduced color fidelity.  
-  
- If this variant shows a large performance gain, it likely indicates that your app consumes too much memory bandwidth. Performance gains can be especially pronounced when the profiled frame suffers from a significant amount of overdraw or contains a lot of alpha-blending.  
-  
- If the kinds of scenes that are rendered by your app don't require high-fidelity color reproduction, don't require the render target to have an alpha channel, and don't often contain smooth gradients—which are susceptible to banding artifacts under reduced color fidelity—consider using a 16bpp render target format to reduce memory bandwidth usage.  
-  
- If the scenes that are rendered in your app require high-fidelity color reproduction or an alpha channel, or smooth gradients are common, consider other strategies to reduce memory bandwidth usage—for example, reducing the amount of overdraw or alpha-blending, reducing the dimensions of the framebuffer, or modifying texture resources to consume less memory bandwidth by enabling compression or reducing their dimensions. As usual, you have to consider the image quality trade-offs that come with any of these optimizations.  
-  
- If your app would benefit from switching to a 16bpp back buffer but it's a part of your swap chain, you have to take additional steps because DXGI_FORMAT_B5G6R5_UNORM is not a supported back buffer format for swap chains created by using `D3D11CreateDeviceAndSwapChain` or `IDXGIFactory::CreateSwapChain`. Instead, you have to create a B5G6R5_UNORM format render target by using `CreateTexture2D` and render to that instead. Then, before you call Present on your swap chain, copy the render target onto the swap-chain backbuffer by drawing a full-screen quad with the render target as your source texture. Although this is an extra step that will consume some memory bandwidth, most rendering operations will consume less bandwidth because they affect the 16bpp render target; if this saves more bandwidth than is consumed by copying the render target to the swap-chain backbuffer, then rendering performance is improved.  
-  
- GPU architectures that use tiled rendering techniques can see significant performance benefits by using a 16bpp framebuffer format because a larger portion of the framebuffer can fit in each tile's local framebuffer cache. Tiled rendering architectures are sometimes found in GPUs in mobile handsets and tablet computers; they rarely appear outside of this niche.  
-  
-## Remarks  
- The render target format is reset to DXGI_FORMAT_B5G6R5_UNORM on every call to `ID3D11Device::CreateTexture2D` that creates a render target. Specifically, the format is overridden when the D3D11_TEXTURE2D_DESC object passed in pDesc describes a render target; that is:  
-  
--   The BindFlags member has the D3D11_BIND_REDNER_TARGET flag set.  
-  
--   The BindFlags member has the D3D11_BIND_DEPTH_STENCIL flag cleared.  
-  
--   The Usage member is set to D3D11_USAGE_DEFAULT.  
-  
-## Restrictions and limitations  
- Because the B5G6R5 format doesn't have an alpha channel, alpha content is not preserved by this variant. If your app's rendering requires an alpha channel in your render target, you can't just switch to the B5G6R5 format.  
-  
-## Example  
- The **16bpp Render Target Format** variant can be reproduced for render targets created by using `CreateTexture2D` by using code like this:  
-  
-```  
-D3D11_TEXTURE2D_DESC target_description;  
-  
-target_description.BindFlags = D3D11_BIND_RENDER_TARGET;  
-target_description.Format = DXGI_FORMAT_B5G6R5_UNORM;  
-d3d_device->CreateTexture2D(&target_description, nullptr, &render_target);  
-```
+redirect_url: /visualstudio/debugger/graphics/16bpp-render-target-format-variant
+---

docs/debugger/1x1-viewport-size-variant.md

@@ -1,52 +1,3 @@
 ---
-title: "1x1 Viewport Size Variant | Microsoft Docs"
-ms.custom: ""
-ms.date: "11/04/2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology: 
-  - "vs-ide-debug"
-ms.tgt_pltfrm: ""
-ms.topic: "article"
-ms.assetid: 3dbc3247-00f5-4644-8ff9-72e9febcf09a
-caps.latest.revision: 6
-author: "mikejo5000"
-ms.author: "mikejo"
-manager: "ghogen"
-translation.priority.ht: 
-  - "cs-cz"
-  - "de-de"
-  - "es-es"
-  - "fr-fr"
-  - "it-it"
-  - "ja-jp"
-  - "ko-kr"
-  - "pl-pl"
-  - "pt-br"
-  - "ru-ru"
-  - "tr-tr"
-  - "zh-cn"
-  - "zh-tw"
----
-# 1x1 Viewport Size Variant
-Reduces the viewport dimensions on all render targets to 1x1 pixels.  
-  
-## Interpretation  
- A smaller viewport reduces the number of pixels that must be shaded, but doesn't reduce the number of vertices that must be processed. Setting the viewport dimensions to 1x1 pixels effectively eliminates pixel-shading from your app.  
-  
- If this variant shows a large performance gain, it might indicate that your app consumes too much fillrate. This can indicate that the resolution you have chosen is too high for the target platform or that your app spends significant time shading pixels that are later overwritten (overdraw). This result suggests that decreasing the size of your framebuffer or reducing the amount of overdraw will improve your app's performance.  
-  
-## Remarks  
- The viewport dimensions are reset to 1x1 pixels after every call to `ID3D11DeviceContext::OMSetRenderTargets` or `ID3D11DeviceContext::RSSetViewports`.  
-  
-## Example  
- This variant can be reproduced by using code like this:  
-  
-```  
-D3D11_VIEWPORT viewport;  
-viewport.TopLeftX = 0;  
-viewport.TopLeftY = 0;  
-viewport.Width = 1;  
-viewport.Height = 1;  
-d3d_context->RSSetViewports(1, &viewport);  
-```
+redirect_url: /visualstudio/debugger/graphics/1x1-viewport-size-variant
+---

docs/debugger/TOC.md

@@ -234,53 +234,7 @@
 ### [How to: Debug Native DLLs](how-to-debug-native-dlls.md)
 ### [How to: Debug Injected Code](how-to-debug-injected-code.md)
 ## [Debugging GPU Code](debugging-gpu-code.md)
-## [Visual Studio Graphics Diagnostics](visual-studio-graphics-diagnostics.md)
-### [Overview of Visual Studio Graphics Diagnostics](overview-of-visual-studio-graphics-diagnostics.md)
-### [Getting Started with Visual Studio Graphics Diagnostics](getting-started-with-visual-studio-graphics-diagnostics.md)
-### [Capturing Graphics Information](capturing-graphics-information.md)
-### [GPU Usage](gpu-usage.md)
-### [Graphics Log Document](graphics-log-document.md)
-### [Graphics Frame Analysis](graphics-frame-analysis.md)
-#### [1x1 Viewport Size Variant](1x1-viewport-size-variant.md)
-#### [0x-2x-4x MSAA Variants](0x-2x-4x-msaa-variants.md)
-#### [Point, Bilinear, Trilinear, and Anisotropic Texture Filtering Variants](point-bilinear-trilinear-and-anisotropic-texture-filtering-variants.md)
-#### [16bpp Render Target Format Variant](16bpp-render-target-format-variant.md)
-#### [Mip-map Generation Variant](mip-map-generation-variant.md)
-#### [Half-Quarter Texture Dimensions Variant](half-quarter-texture-dimensions-variant.md)
-#### [BC Texture Compression Variant](bc-texture-compression-variant.md)
-### [Graphics Event List](graphics-event-list.md)
-### [Graphics State](graphics-state.md)
-### [Graphics Pipeline Stages](graphics-pipeline-stages.md)
-### [Graphics Event Call Stack](graphics-event-call-stack.md)
-### [Graphics Pixel History](graphics-pixel-history.md)
-### [Graphics Object Table](graphics-object-table.md)
-### [HLSL Shader Debugger](hlsl-shader-debugger.md)
-### [Command-Line Capture Tool](command-line-capture-tool.md)
-### [Graphics Diagnostics Examples](graphics-diagnostics-examples.md)
-#### [Walkthrough: Capturing Graphics Information](walkthrough-capturing-graphics-information.md)
-#### [Walkthrough: Capturing Graphics Information Programmatically](walkthrough-capturing-graphics-information-programmatically.md)
-#### [Walkthrough: Missing Objects Due to Device State](walkthrough-missing-objects-due-to-device-state.md)
-#### [Walkthrough: Missing Objects Due to Vertex Shading](walkthrough-missing-objects-due-to-vertex-shading.md)
-#### [Walkthrough: Missing Objects Due to Misconfigured Pipeline](walkthrough-missing-objects-due-to-misconfigured-pipeline.md)
-#### [Walkthrough: Debugging Rendering Errors Due to Shading](walkthrough-debugging-rendering-errors-due-to-shading.md)
-#### [Walkthrough: Using Graphics Diagnostics to Debug a Compute Shader](walkthrough-using-graphics-diagnostics-to-debug-a-compute-shader.md)
-#### [How to: Change the Graphics Diagnostics Playback Machine](how-to-change-the-graphics-diagnostics-playback-machine.md)
-#### [How to: Use Graphics Diagnostics with an ARM Device](how-to-use-graphics-diagnostics-with-an-arm-device.md)
-### [Reference (Programmatic Capture)](reference-programmatic-capture.md)
-#### [VsgDbg Class](vsgdbg-class.md)
-##### [VsgDbg::VsgDbg (Constructor)](vsgdbg-vsgdbg-constructor.md)
-##### [VsgDbg::~VsgDbg (Destructor)](vsgdbg-tilde-vsgdbg-destructor.md)
-##### [AddMessage](addmessage.md)
-##### [BeginCapture](begincapture.md)
-##### [CaptureCurrentFrame](capturecurrentframe.md)
-##### [Copy (Programmatic Capture)](copy-programmatic-capture.md)
-##### [EndCapture](endcapture.md)
-##### [Init](init.md)
-##### [ToggleHUD](togglehud.md)
-##### [UnInit](uninit.md)
-#### [DONT_SAVE_VSGLOG_TO_TEMP](dont-save-vsglog-to-temp.md)
-#### [VSG_DEFAULT_RUN_FILENAME](vsg-default-run-filename.md)
-#### [VSG_NODEFAULT_INSTANCE](vsg-nodefault-instance.md)
+## [Graphics Diagnostics](graphics/TOC.md)
 ## [Debugging Web Applications and Script](debugging-web-applications-and-script.md)
 ### [Debugging ASP.NET and AJAX Applications](debugging-aspnet-and-ajax-applications.md)
 #### [Preparing to Debug ASP.NET](preparing-to-debug-aspnet.md)

docs/debugger/addmessage.md

@@ -1,50 +1,3 @@
 ---
-title: "AddMessage | Microsoft Docs"
-ms.custom: ""
-ms.date: "11/04/2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology: 
-  - "vs-ide-debug"
-ms.tgt_pltfrm: ""
-ms.topic: "article"
-ms.assetid: 102a0404-a00c-4566-93f3-01bc8df63280
-caps.latest.revision: 5
-author: "mikejo5000"
-ms.author: "mikejo"
-manager: "ghogen"
-translation.priority.ht: 
-  - "de-de"
-  - "es-es"
-  - "fr-fr"
-  - "it-it"
-  - "ja-jp"
-  - "ko-kr"
-  - "ru-ru"
-  - "zh-cn"
-  - "zh-tw"
-translation.priority.mt: 
-  - "cs-cz"
-  - "pl-pl"
-  - "pt-br"
-  - "tr-tr"
----
-# AddMessage
-Adds a custom message to the graphics diagnostics *HUD* (Head-Up Display).  
-  
-## Syntax  
-  
-```C++  
-void AddMessage(  
-  wchar_t const * szMessage  
-);  
-```  
-  
-#### Parameters  
- `szMessage`  
- The message to be added to the HUD.  
-  
-## Remarks  
- The graphics diagnostics HUD is displayed in the upper-left corner of the app that's running under graphics diagnostics. It displays run-time information about the app and about graphics information capture, and messages that are added by calling this function.  
-  
- To add a message to the HUD, you don't have to be actively capturing graphics information—that is, a message can be added through an instance of the `VsgDbg` class, but the [Init](../debugger/init.md) member function does not to be called first. Messages are only displayed in the HUD, they are not recorded in the graphics log file.
+redirect_url: /visualstudio/debugger/graphics/addmessage
+---