Game: DLSS Frame Generation causes artifacts in HUD #1075
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1075
Loading…
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?
Reported by Flanned on Discord
Longshot version
nightly-325-e4d035e9
Channel
Nightly
What kind of problem
Graphics artifacts
What happened
With DLSS Frame Generation enabled, artifacts appear around most HUD elements, as shown in the attached screenshot. The built-in frame generation does not show this issue. The game was paused during the reported period with FG set to Auto, so it automatically switched to built-in frame generation. The attached log's lack of DLSS-generated frames during its last 600 presents is therefore consistent with this switch, but does not capture the artifacts while DLSS FG was active.
Where in the game
Exact location not specified; screenshot shows an outdoor area.
How often
Spinning the camera around reproduces it most easily; exact frequency not specified.
Graphics card and driver version
NVIDIA GeForce RTX 5060 Ti 16 GB, driver 621.24
System
Windows 11. CPU and RAM not specified.
Log
Attached longshot_log.txt. The log identifies nightly-325-e4d035e9, output resolution 2560x1440, and reports that none of the last 600 presents were made by DLSS-G. A log captured while DLSS FG is active and the artifacts occur would help investigate.
Still needed
Exact game location, reproduction frequency, CPU and RAM, and (if possible) a log captured while the artifacts occur with DLSS FG active.
Related work
Open Longshot PR #1041 addresses frame-generation selection and behavior when DLSS FG cannot run (such as paused/menu screens); it is not a merged fix for the reported HUD artifacts.
Files from the Discord report:
Updated with more from Flanned on Discord: Added the paused/Auto FG explanation for the log and noted related open PR #1041, which is not yet a fix for the HUD artifact report.