Support for VK_NV_raw_access_chains

Open
#3,743 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
cpp

Research direction

Start by tracing RenderDoc's existing Vulkan extension handling and the capture path affected when VK_NV_raw_access_chains is exposed. Compare the required extension behavior with similar supported Vulkan features, then verify that captures of applications using the extension succeed without breaking existing Vulkan captures.

Written by the indexing model from the issue text.

Description

Feature Unresolved

Description of Feature

Hi. I'm currently working on an nvk implementation of VK_NV_raw_access_chains and trying to debug a performance issue with a game that I do not have which is running under vkd3d (Lego Builder's Journey) https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/38874#note_3232008 Taking captures of that game fails when VK_NV_raw_access_chains is available and used by vkd3d.

vkd3d automatically uses VK_NV_raw_access_chains when support is enabled in the driver, so I believe we need support in renderdoc if we want to continue using renderdoc for dx12 games once that feature lands.

It would be nice if renderdoc supported VK_NV_raw_access_chains.

Environment

  • RenderDoc version: 1.41
  • Operating System: Arch Linux
  • Graphics API: Vulkan
Dominant language
C++
Stars
11.2k
Forks
1.8k
Avg merge
5h 19m
Merged PRs (30d)
4

Getting set up

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 baldurk/renderdoc

All issues in baldurk/renderdoc

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.