Skip to content
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

Wireframe unavailable for draw calls with vertex format VK_FORMAT_R8G8B8A8_UINT #3511

Open
Izhido opened this issue Dec 28, 2024 · 1 comment
Labels
Bug A crash, misbehaviour, or other problem Need More Info More information is needed from a user to work on this issue

Comments

@Izhido
Copy link

Izhido commented Dec 28, 2024

Description of Bug

To be more specific, RenderDoc does not seem to show the wireframe for a draw call selected in the Event Browser, in the "VS In" tab of the Preview window in Mesh Viewer, if the data format of the vertices in the draw call is VK_FORMAT_R8G8B8A8_UINT (that is, four 8-bit integer vertex values).

The "VS Out" tab does not seem to be affected by the issue.

Oddly enough, triangles and vertices can be selected in the "VS In" tab, and the effect of that is shown in the VS Input table above the Preview. Meaning, the triangles do exist somewhere in there, but the wireframe is simply not shown.

Steps to reproduce

Load and play the attached capture, "adtears-small.rdc", in RenderDoc.

adtears-small.zip

Virtually all of the draw calls, up to #562, use VK_FORMAT_R32G32B32_SFLOAT or VK_FORMAT_R32G32B32A32_SFLOAT as their vertex format, except for the last 3 calls ( #572, #575, #585 ).
Select any of the 3 calls mentioned.
Wireframe is shown in the "VS Out" tab, but not in the "VS In" tab.

Environment

  • RenderDoc version: 1.34 (Meta Fork 68.2)
  • Operating System: Host: Windows 11 24H2 / Device: Oculus Quest 3
  • Graphics API: Vulkan 1.1
@baldurk
Copy link
Owner

baldurk commented Dec 30, 2024

If this is a problem you're encountering on Oculus's fork you need to report it to them. No support is given here for their fork for obvious reasons.

Does this happen on the mainline RenderDoc?

@baldurk baldurk added Bug A crash, misbehaviour, or other problem Need More Info More information is needed from a user to work on this issue labels Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A crash, misbehaviour, or other problem Need More Info More information is needed from a user to work on this issue
Projects
None yet
Development

No branches or pull requests

2 participants