docs: where the NVIDIA descriptor-heap faults stand on 615.78.08
The heap acceleration-structure read still needs the rewrite on 615.78.08; the READMEs say so and point at HeapASRead --no-workaround for checking a newer driver. Dynamic descriptor indexing in hit shaders is fixed there, which the README and the Sponza and SponzaBench notes now say, and the VulkanTriangle investigation no longer contradicts itself about llvmpipe, which advertises VK_EXT_descriptor_heap now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
f7cfd53562
commit
449d5da553
4 changed files with 36 additions and 13 deletions
|
|
@ -20,8 +20,8 @@ exits.
|
|||
`Window::Render()`, reporting per-frame wall-clock stats and throughput.
|
||||
|
||||
Unlike the interactive Sponza example — which is single-material on native
|
||||
because of the hit-shader dynamic-`descriptor_heap`-index driver fault
|
||||
(see `examples/Sponza/README.md`) — SponzaBench's closest-hit shades from
|
||||
because of the hit-shader dynamic-`descriptor_heap`-index driver fault, fixed
|
||||
in NVIDIA `615.78.08` (see `examples/Sponza/README.md`) — SponzaBench's closest-hit shades from
|
||||
barycentric coordinates and samples **no** texture, so it can build the
|
||||
**full multi-mesh atrium** (25 mesh groups, ~262 k triangles) as one
|
||||
multi-instance TLAS. The albedo is still decompressed and uploaded during
|
||||
|
|
|
|||
Loading…
Reference in a new issue