Game: DLSS Frame Generation causes artifacts in HUD #1075

Open
opened 2026-11-16 06:32:19 +00:00 by BeanIssues · 2 comments
Collaborator

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.

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.

Reported by [Flanned on Discord](https://discord.com/channels/1569849200047427645/1569849200617726065/1571751934363439125) ### 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](https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/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.
Author
Collaborator

Files from the Discord report:

Files from the Discord report: - [image.png](https://git.magicbean.dev/attachments/abbfcf15-0af7-4794-b3ad-1226132ee7f2) - [longshot_log.txt](https://git.magicbean.dev/attachments/a7928831-7d35-4a35-8072-b2bd7010236d)
Author
Collaborator

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.

Updated with more from [Flanned on Discord](https://discord.com/channels/1569849200047427645/1571751934363439125/1571775542850494516): 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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot#1075
No description provided.