News report

Microsoft Open-Sources DxTimingCaptureLibrary for DirectX GPU Profiling

Microsoft's new MIT-licensed DxTimingCaptureLibrary exposes PIX-derived DirectX ETW data for custom game-engine profilers on Windows 10 and 11.

On this page
  1. Microsoft has extracted DirectX timing code from PIX into a standalone library
  2. The main change is reusable ETW interpretation rather than a new graphics feature
  3. Microsoft ships samples for residency logging, Perfetto traces and D3D12 errors
  4. Why this matters for PC game development

Microsoft has extracted DirectX timing code from PIX into a standalone library

Microsoft released DxTimingCaptureLibrary on September 30, 2026 as an open-source C++ library under the MIT license. The DirectX team says it works on Windows 10 and Windows 11 and is intended to make DirectX Event Tracing for Windows data easier to consume in tools such as in-engine game profilers.

The library comes from code used by PIX Timing Captures. Microsoft says the DirectX data shown in the PIX Timing Capture interface is available through DxTimingCaptureLibrary, but the release is not PIX itself: developers provide the ETW session and consume the interpreted data through callbacks in their own tooling.

What DxTimingCaptureLibrary can expose to developer tools
TelemetryExamplesWhy it matters
GPU timingTop-of-pipe and bottom-of-pipe timestamps for command-list workHelps correlate submitted DirectX work with GPU execution timing
Memory residencyPaging, eviction and migration failuresCan reveal pressure and movement between video and system memory
DirectStorageRead and status requestsLets a profiler place storage activity alongside graphics telemetry
Pipeline state compilationCompilation eventsCan help identify when pipeline creation work occurs
Display timingMonitor VSync eventsProvides timing context around presentation and display cadence
Runtime diagnosticsD3D runtime failure logs and PIX markers/countersAdds graphics-runtime and application instrumentation to the same analysis path

The main change is reusable ETW interpretation rather than a new graphics feature

DirectX components including the D3D12 runtime, DXGI and the DirectX kernel already emit ETW events. The difficult part for a custom profiler is interpreting and correlating events from multiple providers. DxTimingCaptureLibrary packages that interpretation layer and calls application-defined interfaces when relevant data becomes available.

That makes the release primarily developer infrastructure. It does not increase game frame rates by itself, change the DirectX rendering pipeline, or automatically eliminate stutter. Its value is that engine and performance teams can integrate richer Windows graphics telemetry into the tools they already use to diagnose timing, residency, compilation and presentation behavior.

Microsoft ships samples for residency logging, Perfetto traces and D3D12 errors

Microsoft's announcement includes a basic logging sample that can focus on DirectX residency and paging, a D3D12 journal sample that reports runtime failures, and a Perfetto sample that converts GPU timing callbacks into a trace connecting GPU command-list work with CPU-side markers. A memory-treemap sample is also described as work in progress.

The high-level integration flow is to configure an ETW session with the needed DirectX events, route those events to the library's handler, implement the callback interfaces relevant to the tool, and consume the callbacks as matching events arrive.

Why this matters for PC game development

PC graphics debugging spans the application, D3D12, drivers, memory residency, storage and the Windows graphics kernel. A reusable Microsoft-supported interpretation layer lowers the amount of ETW-specific plumbing an engine team needs before it can reason about those layers together.

The release also fits Microsoft's broader 2026 push to improve Windows GPU developer tooling. DxTimingCaptureLibrary is narrower than features such as DirectX Dump Files: it focuses on turning timing and related ETW telemetry into data that custom tools can consume, while crash-dump workflows target post-failure GPU diagnosis.

Sources

Primary and technical sources

These sources support the reporting and analysis above. Current stories are updated when later evidence materially changes the facts.

  1. 01 Microsoft DirectX Developer Blog

    Introducing DxTimingCaptureLibrary

Related

Technical guide

16 GB vs 32 GB vs 64 GB RAM for Gaming PCs

Choose 16 GB, 32 GB, or 64 GB of system RAM for a gaming PC by measuring the games and simultaneous workloads you actually run instead of relying on a universal capacity rule.