Bill Kristiansen

Principal Developer, DirectX

Principal Developer, Microsoft DirectX

Post by this author

Agility SDK 1.608.0: Enhanced Barriers and more

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 ...
Comments are closed.0 5

Preview Agility SDK 1.706.3-preview: SM 6.7, Enhanced Barriers and more

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...
Comments are closed.0 1

Agility SDK 1.602.4

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

D3D12 Enhanced Barriers Preview

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 ...
Comments are closed.0 1

D3D12 Debug Object Auto-Naming

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.

A Look Inside D3D12 Resource State Barriers

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.  ...
Comments are closed.0 0

DRED v1.2 supports PIX marker and event strings in Auto-Breadcrumbs

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 ...
Comments are closed.0 0

D3DConfig: A new tool to manage DirectX Control Panel settings

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 ...

Debugger Extension for DRED

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 ...
Comments are closed.0 1

New in D3D12 – DRED helps developers diagnose GPU faults

DRED stands for Device Removed Extended Data. DRED is an evolving set of diagnostic features designed to help identify the cause of unexpected device removal errors, delivering automatic breadcrumbs and GPU-page fault reporting on hardware that supports the necessary features (more about that later). DRED version 1.1 is available today in ...
Comments are closed.0 3

Feedback usabilla icon