Game: Graphical artifacts and AMD driver timeouts on RX 580 2048SP #717
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#717
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?
Longshot version
v3.0.0-rc.3 (source cb01b5a3)
Channel
Release
What kind of problem
Graphics (missing, black or wrong-coloured things, lighting, flicker)
What happened
I am experiencing persistent graphical artifacts while playing Longshot v3.0.0-rc.3 on an AMD Radeon RX 580 2048SP.
Pink, green and white dots appear across textures, foliage and even menu text. The issue occurs in a completely new game, particularly in Kokiri Forest and inside the Great Deku Tree.
I tested different graphics settings, including ASTC as RGBA8. Enabling this option caused an AMD driver timeout, forcing the graphics driver to restart. I also experienced a driver timeout when testing the BC7 environment variable.
The issue is not related to my save file, as it also happens in a fresh game.
My GPU does not support Mesh Shaders, so Longshot uses the compute fallback renderer.
I have attached the automatically generated diagnostic report, execution logs and screenshots showing the artifacts.
Could this be a compatibility issue with the AMD Vulkan driver or the compute fallback renderer?
Where in the game
KokiriForest_Child (child)
How often
Every time
Graphics card and driver version
AMD Radeon RX 580 2048SP, AMD proprietary driver 26.1.1 (AMD proprietary shader compiler)
CPU, RAM and operating system
Intel(R) Core(TM) i7-9700F CPU @ 3.00GHz (8 threads), 16 GB, Windows 11 (build 26100)
Changes from the defaults
longshot_log.txt
a
Screenshots or video
a
Before you send it
Update: Issue persists on Longshot v3.0.0-rc.4
I updated from v3.0.0-rc.3 to v3.0.0-rc.4 and tested the game again.
Unfortunately, the graphical artifacts are still present and make gameplay completely unplayable.
Additional observations:
The issue appears to be related to 3D rendering rather than video playback or save files.
I'm attaching a screenshot showing the current behavior.
Update: Tested Longshot v3.0.0-rc.5 — Improved rendering and performance
I updated Longshot from v3.0.0-rc.4 to v3.0.0-rc.5 and tested it again in Kokiri Forest.
There has been a noticeable improvement compared to my previous tests.
Graphics observations
Performance tests
I tested the following configurations:
Test 1 — Very low resolution
Test 2 — Best playable configuration so far
This second configuration provides a considerably better balance between image quality and performance, maintaining approximately 30 FPS during gameplay in Kokiri Forest.
Hardware and system information
A previous Task Manager measurement during gameplay showed:
Related issue
I also found issue #1204, which reports similar graphical artifacts on another Radeon RX 580 in Kokiri Forest while running RC5.
This suggests that the issue may affect multiple RX 580 configurations.
Current status
RC5 has significantly improved the visual output and made it possible to reach approximately 30 FPS with reduced rendering settings. However, graphical artifacts and performance limitations remain.
I would appreciate any further investigation into the RX 580 rendering path, particularly Compute Fallback and AMD-specific texture handling.
I can provide updated screenshots and fresh RC5 diagnostic logs if needed.