Ease "device lost" debugging

Open
#116 6 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp

Research direction

Review the DirectX DRED, Vulkan diagnostic checkpoints, NVIDIA Nsight Aftermath, and AMD AGS references first. No repository files, tests, entry points, or acceptance criteria are named; identify NRI's device-loss path and define the diagnostic behavior required for each vendor integration before implementation.

Written by the indexing model from the issue text.

Description

d3d11 d3d12 extension vk
Dominant language
C++
Stars
505
Forks
93
Avg merge
22h 34m
Merged PRs (30d)
19

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA-RTX/NRI

All issues in NVIDIA-RTX/NRI

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.