NVIDIA-RTX / NVIDIA-RTX/Streamline
Streamline incompatibility with VK_EXT_descriptor_heap
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 159
- PR merge metrics
- No merged PRs in 30d
Description
When using VK_EXT_descriptor_heap, DLSS and DLSS-G are unable to read user-provided images. DLSS output is black. DLSS-G generates an image, but it's the same as if no motion vectors were provided. Debug visualizations are black for all user-provided images.
There are no errors and all images are still being created with the correct parameters, including the image view.
Binding a dummy descriptor set right before evaluating the DLSS feature seems to restore some funcionality, but the workaround doesn't work for DLSS-G since there is no evaluate call.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with VK_EXT_descriptor_heap and compare behavior for DLSS and DLSS-G when user-provided images are supplied. Use the dummy descriptor-set binding workaround as a diagnostic, then verify that DLSS output, DLSS-G motion vectors, and debug visualizations correctly use those images without the workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100