Title: Vulkan: VK_FORMAT_R8_UNORM missing in Vulkan::getFormat

Open Beginner friendly
#133 0 comments 0 reactions 0 assignees View on GitHub

@0z5a is already working on this.

Since Nov 19, 2026.

  • #137 by @0z5a — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
c
Domain
backend

Research direction

Start by reading vulkan.cpp and compare Vulkan::getFormat with getNativeFormat, which the issue says already handles VK_FORMAT_R8_UNORM. Check the format mappings for R16G16_UINT and R16G16_SINT as well. Confirm the relevant formats are returned correctly and that the undefined-format log no longer occurs for the reported R8_UNORM case.

Written by the indexing model from the issue text.

Description

Hi,

With latest sdk I got sl.log to be flooded with "Cannot have undefined format", 4 times per DLSS evaluation.

It seems to happen because I tag kBufferTypeBiasCurrentColorHint with an R8_UNORM texture, and Vulkan::getFormat in vulkan.cpp has no case for VK_FORMAT_R8_UNORM (getNativeFormat has it).

I think this should fix it:
case VK_FORMAT_R8_UNORM: format = eFormatR8UN; break;

R16G16_UINT and R16G16_SINT seem to be missing from getFormat too.

Thanks!

Dominant language
C
Stars
1.4k
Forks
174
PR merge metrics
No merged PRs in 30d

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 NVIDIA-RTX/Streamline

All issues in NVIDIA-RTX/Streamline

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.