Skip to content

[SPIRV] Support for SPV_EXT_fragment_shader_interlock #3564

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nickclark2016 opened this issue Mar 21, 2025 · 1 comment
Open

[SPIRV] Support for SPV_EXT_fragment_shader_interlock #3564

nickclark2016 opened this issue Mar 21, 2025 · 1 comment
Labels
Feature An improvement or feature Unresolved Waiting for a fix or implementation

Comments

@nickclark2016
Copy link

Description of Feature

I am trying to use RenderDoc to debug my implementation of Moment-Based OIT which takes advantage of ROVs and fragment shader interlock. In the current state of RenderDoc, I am able to check the state of the storage images before and after draw calls. I would like to be able to step through my shaders that use the ROVs and fragment interlocked sections. Without changing my existing shaders to not use this functionality, it is not possible to debug the fragment shaders using this functionality.

I would like support for the various OpExecutionModes provided by SPV_EXT_fragment_shader_interlock within the shader debugging functionality.

Environment

  • RenderDoc version: 1.37
  • Operating System: Windows 11 (Build 22631)
  • Graphics API: Vulkan 1.3
@baldurk baldurk added Feature An improvement or feature Unresolved Waiting for a fix or implementation labels Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature An improvement or feature Unresolved Waiting for a fix or implementation
Projects
None yet
Development

No branches or pull requests

3 participants
@baldurk @nickclark2016 and others