Release Notes

New Features and Capabilities

For a listing of new features and capabilities, see Release Notes for 2024.2.

Known Issues and Limitations

  • Nsight Aftermath covers only GPU crashes. CPU crashes in the NVIDIA graphics driver, the D3D runtime, the Vulkan loader, or the application cannot be captured.

  • Nsight Aftermath is only fully supported on Turing or later GPUs.

D3D

  • Nsight Aftermath is only fully supported for D3D12 devices. Only basic support with a reduced feature set (no API resource tracking and no shader address mapping) is available for D3D11 devices.

  • Nsight Aftermath is fully supported on Windows 10 and newer, with limited support on Windows 7.

  • Nsight Aftermath has known compatibility issues with the D3D12 Debug Layer:

    • When initializing the API via GFSDK_Aftermath_DXxx_Initialize, if the debug runtime is detected it will return GFSDK_Aftermath_Result_FAIL_D3dDllInterceptionNotSupported.

    • If using the monitor, some GPU exceptions will not trigger a GPU dump from Aftermath

    • We are actively looking for ways to reduce these compatibility issues

  • Any tools that use a D3D API interception layer, such as Microsoft PIX or Nsight Graphics, will conflict with markers and resource tracking in Aftermath.

  • Shader line mappings are only supported for DXIL shaders, i.e., Shader Model 6 or above. Line mappings for shaders in DXBC shader byte code format are unsupported.

  • Shader line mappings are not yet supported for shaders compiled with the DirectX Shader Compiler’s -Zs option for generating “slim PDBs”.

Vulkan

  • Shader line mappings are not yet supported for SPIR-V shaders compiled with the NonSemantic.Shader.DebugInfo.100 extended instruction set, i.e., shaders compiled with the -gVS option of glslangValidator or the -fspv-debug=vulkan-with-source option of the DirectX Shader Compiler.