In general we recommend using the latest available driver for your GPU. The following is a list of last known good drivers that work well with the current release of PIX.
|Release Date||Windows Driver Version||Version|
High Frequency Counters
We are working with each IHV to resolve these issues. Stay tuned for updates in future PIX releases.
- High Frequency Counter collection may run out of memory for large PIX captures on AMD GPUs.
- Some counters may be all zero on 18.50 drivers. This is resolved in upcoming AMD driver.
- Collecting High Frequency Counters will fail and/or crash after collecting Debug Layer Warnings in PIX.
- Top-of-pipe and end-of-pipe timestamps may be misattributed to the event immediately preceding the actual event. As a side effect, PIX may incorrectly attribute regions of High Frequency Counter graphs to the preceding event too.
- No known issues
Cannot capture application on a system using only Microsoft Basic Display GPU
PIX will fail to capture an application on a system that has defaulted to the ‘Microsoft Basic Display Adapter’ as the only supported GPU. This can be fixed by installing a device driver for the GPU hardware present on your system.
HLSL variables in DXIL debugger
This issue was resolved in PIX-2003.26.
Due to a change in DXCompiler’s debug information, PIX does not report HLSL variables for any DXIL shader compiled with versions of DXCompiler that were built from github source as of November 13th, 2019. This includes DXIL shaders built by PIX 1911.27 as part of Shader Edit and Continue. The only reasonable workaround is to compile the shaders with an older version of DXCompiler. A fix for PIX will be forthcoming. This is the specific DXCompiler commit that introduced the newer debug information: https://github.com/microsoft/DirectXShaderCompiler/commit/f4965b71dd878c42c219ec00d31c406c483fd045