nvngx_dlssd 310.9.1 (SL 2.14.1): WRITE_AFTER_WRITE sync hazard on NGX-internal images during first Vulkan evaluate; 310.7.0 is clean
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- computer-graphics
Research direction
Reproduce the first Vulkan evaluate using NGX_VULKAN_CREATE_DLSSD_EXT1 and NGX_VULKAN_EVALUATE_DLSSD_EXT with synchronization validation enabled. Compare nvngx_dlssd.dll 310.9.1 against 310.7.0 and inspect the reported nv.ngx.dlssd.resource hazards. Done means the newer DLL produces no WRITE_AFTER_WRITE validation messages.
Written by the indexing model from the issue text.
Description
Environment
- RTX 5090, driver 610.88, Windows 11, Vulkan 1.4.341
- Vulkan SDK 1.4.357 validation layer with synchronization validation enabled
nvngx_dlssd.dll310.9.1 from the Streamline 2.14.1 release zip, NGX used directly (NGX_VULKAN_CREATE_DLSSD_EXT1/NGX_VULKAN_EVALUATE_DLSSD_EXT, not through the interposer)- Ray Reconstruction with
DLUnifieddenoise mode, packed roughness, linear depth,IsHDR | MVLowRes, render preset F (the same happens with preset left at default)
What happens
On the first evaluate of a run, the synchronization validation layer reports two hazards, both between commands recorded by NGX on images created and named by NGX:
vkCmdClearColorImage(): WRITE_AFTER_WRITE hazard detected. vkCmdClearColorImage writes to VkImage 0x...[nv.ngx.dlssd.resource], which was previously written during an image layout transition initiated by vkCmdPipelineBarrier[nv.ngx.dlssd.Evaluate].
(two instances, on two different nv.ngx.dlssd.resource images). Later evaluates in the same run report nothing.
Expected
No hazards: the barrier that transitions these internal images presumably needs the transfer-write access/stage of the following clear in its destination scope (or the clear should come before the transition).
Regression
The same application, scene and settings with nvngx_dlssd.dll 310.7.0 (Streamline 2.12.0) report zero validation messages.
Impact
Applications that treat any validation message as a failure (e.g. CI or headless test runs) have to filter these by object name until a fixed DLL ships.
- Dominant language
- C
- Stars
- 1.4k
- Forks
- 174
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from NVIDIA-RTX/Streamline
-
Title: Vulkan: VK_FORMAT_R8_UNORM missing in Vulkan::getFormatPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA-RTX/Streamline#133 ·
-
sl.log folder makes it hard to integrate, as many developer has *.log in the exclude filter for git/p4.Possibly taken @Dragon31337 claimed this 72 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
NVIDIA-RTX/Streamline#121 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NVIDIA-RTX/Streamline#120 ·
-
C++23 issueOpenbug triaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NVIDIA-RTX/Streamline#111 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
NVIDIA-RTX/Streamline#136 · 1 comment · 1 reaction ·
All issues in NVIDIA-RTX/Streamline
Similar issues
-
ecs_ptr_from_json does not free the buffer of a string longer than 256 bytes on two error pathsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SanderMertens/flecs#2444 ·
Maintainers usually reply within 1 day
-
Status: Opened
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
espressif/esp-eth-drivers#201 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
libsdl-org/SDL#16788 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
cisco/ChezScheme#1110 ·
Maintainers usually reply within 1 day