Ease "device lost" debugging

[dzhdanNV]

https://microsoft.github.io/DirectX-Specs/d3d/DeviceRemovedExtendedData.html
https://registry.khronos.org/vulkan/specs/latest/man/html/VK_NV_device_diagnostic_checkpoints.html
https://developer.nvidia.com/nsight-aftermath
https://gpuopen.com/learn/rgd_1_0_tutorial/
AMD: custom markers from AGS lib

[duckdoom5]

NVRHI supports Aftermath for crash dumps, which is very valuable to have for games/apps that have been released (to be able to get dumps from users).

I have not looked into it much, but from what I have seen (by briefly looking over the commit) in the NVRHI repo it requires GAPI specific code.
Is this feature planned or is it possible to add this as an extension on top of NRI?

[duckdoom5]

In the other issue you mentioned Aftermath is for D3D12, but the link states it supports vulkan as well:

NVIDIA® Nsight™ Aftermath is a library that integrates into a D3D12 or Vulkan

[dzhdanNV]

Is this feature planned or is it possible to add this as an extension on top of NRI?

Feels like an extension for NRI. I'm doing a release right now, then another release improving "ultimate bindless" support (finally, direct descriptor heap indexing in HLSL will work in VK). Then I'm OK to start to work on this.

NVIDIA® Nsight™ Aftermath is a library that integrates into a D3D12 or Vulkan

Cool. Simpler for me :) The other option is DRED for D3D12 (vendor agnostic) and VK_NV_device_diagnostic_checkpoints or VK_AMD_buffer_marker, since there is no a vendor agnostic extension in VK.

[duckdoom5]

Awesome! I don't need this any time soon so take your time :)

[dzhdanNV]

v172 release brings better handling and reporting of DEVICE_LOST error. Additionally, starting from this release AbortExecution is no longer called for user-actionable errors (DEVICE_LOST and OUT_OF_DATE). These changes were a preliminary work for this issue.

[dzhdanNV]

Aftermath is D3D12/Vulkan nowadays.
VK_EXT_device_fault = DRED