[viewer] Low FPS with RT Shadows #1085
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#1085
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Source: in-viewer report (Help > Report Bug)
Reporter (avatar name as given; not verified):
System
Description
Steps to reproduce
not given
Log excerpt
Full scrubbed excerpt: slipstream-log-excerpt.txt
Last 40 lines
Screenshot
Filed by the Slipstream report relay. The reporter's identity is not verified; system details are as sent by the reporter.
Thanks for the report and the performance capture -- it's very useful.
What it shows: the frame is limited by the graphics card (about 35 ms per frame), and the ray-traced shadows alone take about 10 ms per frame on your RX 9070 XT, even at half resolution and low quality; ray-traced volumetric light (god rays) adds about 5 ms more. That is far more than we see on NVIDIA cards, so we're looking at how our shadow rays behave on AMD's ray tracing hardware specifically.
Two more captures would help a lot (Help > Report Bug after each, or attach the performance capture), in the same spot:
RenderVKAsyncCompute= 0 (Advanced > Debug Settings), everything else unchanged. This gives exact per-pass timings (with it on, some passes' timings include time spent waiting for the ray tracing).If you know whether the place you tested has a lot of alpha-masked objects (foliage, fences, hair, lace), that's helpful too.