Introducing Fence Barriers We are excited to share the preview release of Fence Barriers (Tier-1), a new capability now available in AgilitySDK 1.719-preview (https://devblogs.microsoft.com/directx/directx12agility/). Fence Barriers expand on Enhanced Barriers to provide support for signaling and waiting on fences during command buffer execution. ...

We’ve published another Agility SDK, version 1.608.0.  This Agility SDK has support for Enhanced Barriers, and a few minor DX12 features. That’s right: these features no longer require developer mode to run on your machine! Head to Agility SDK Downloads to grab it. Enhanced Barriers For an overview of Enhanced Barriers, please see here for our...

In addition to support for Shader Model 6.7, this preview Agility SDK contains improved support for Enhanced Barriers and some smaller features  For more on the public release of Shader Model 6.7, please see our 1.606.3 announcement. With the addition of preview Enhanced Barriers and Relaxed Format Casting support, raw gathers will achieve their...

This is a bug-fix-only update to 1.602.0. No new features. NuGet Gallery | Microsoft.Direct3D.D3D12 1.602.4 Bug Fixes  

Good news for developers frustrated by confusing and inefficient D3D12 resource barriers, Enhanced Barriers are coming soon to D3D12, and are available now for experimental preview. Enhanced Barriers are a new set of D3D12 API’s that give developers independent control over GPU work synchronization, texture layout transitions, and cache flushing (“...

As of Windows 10 Release Preview 20236, there is now an option to enable automatic naming of D3D12 objects. Debug Object Auto-Names are unique, and descriptive, and are easy to enable programmatically or using d3dconfig.

Many D3D12 developers have become accustomed to managing resource state transitions and read/write hazards themselves using the ResourceBarrier API. Prior to D3D12, such details were handled internally by the driver.  However, D3D12 command lists cannot provide the same deterministic state tracking as D3D10 and D3D11 device contexts.  Therefore, st...

In Windows 10 1903, DRED 1.1 provided D3D12 developers with the ability to diagnose device removed events using GPU page fault data and automatic breadcrumbs. As a result, TDR debugging pain has been greatly reduced.  Hooray!  Unfortunately, developers still struggle to pinpoint which specific GPU workloads triggered the error.  So, we've made a fe...

The DirectX Control Panel (DXCpl.exe) has dutifully given developers the ability to configure Direct3D debug settings for nearly two decades.  But what started as a simple utility for controlling D3D debug output and driver type selection has struggled to keep up with modern DX12 debugging options.  In addition, the UI-based DXCpl doesn’t integrate...

Microsoft recently announced the release of DRED (Device Removed Extended Data) for D3D12 in the Windows 10 May 2019 Update (previously referred to as the Windows 10 19H1 Preview).  Buried in that post is a mention that Microsoft is working on a debugger extension to help simplify post-mortem analysis of DRED.  Good news, that debugger extension is...