Game: Graphical artifacts and AMD driver timeouts on RX 580 2048SP #717

Open
opened 2026-11-15 06:09:51 +00:00 by aleisii · 2 comments

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

  • ASTC as RGBA8 was tested and enabled temporarily, but caused AMD driver timeouts.
  • RX_VK_ASTC_BC7=1 was also tested temporarily and caused an AMD driver timeout.
  • The environment variable file has since been removed.
  • The issue also occurs with a fresh game.

longshot_log.txt

a

Screenshots or video

a

Before you send it

  • The problem is still there on the newest release or nightly.
  • I searched the open issues for it.
  • I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
### 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 - ASTC as RGBA8 was tested and enabled temporarily, but caused AMD driver timeouts. - RX_VK_ASTC_BC7=1 was also tested temporarily and caused an AMD driver timeout. - The environment variable file has since been removed. - The issue also occurs with a fresh game. ### longshot_log.txt a ### Screenshots or video a ### Before you send it - [x] The problem is still there on the newest release or nightly. - [x] I searched the open issues for it. - [x] I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
Author

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 initial intro video renders correctly.
  • As soon as 3D gameplay begins, the image becomes severely corrupted with bright pink, cyan, green, and yellow artifacts.
  • The issue occurs both when loading existing save files and when starting a new game.
  • Enabling ASTC as RGBA8 in the Debug tab makes no difference. The artifacts remain exactly the same.
  • My GPU is an AMD Radeon RX 580 2048SP.

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: 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 initial intro video renders correctly. - As soon as 3D gameplay begins, the image becomes severely corrupted with bright pink, cyan, green, and yellow artifacts. - The issue occurs both when loading existing save files and when starting a new game. - Enabling **ASTC as RGBA8** in the Debug tab makes no difference. The artifacts remain exactly the same. - My GPU is an **AMD Radeon RX 580 2048SP**. 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.
Author

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

  • The severe pink, cyan, green and yellow graphical corruption has improved considerably.
  • The environment is now much more recognizable.
  • Some texture artifacts and visual corruption are still present, particularly around vegetation and parts of the environment.
  • The game is now playable at approximately 30 FPS after significantly reducing the rendering resolution.

Performance tests

I tested the following configurations:

Test 1 — Very low resolution

  • Output resolution: 720x400.
  • Internal resolution: 33%.
  • Performance: approximately 30 FPS, relatively stable.
  • Image quality: extremely blurry.

Test 2 — Best playable configuration so far

  • Output resolution: 1280x720.
  • Internal resolution: 58%.
  • Sharpness: 20%.
  • Anisotropic filtering: 2x.
  • Shadow resolution: In-game.
  • Threaded rendering: Enabled.
  • Frame generation: Disabled.
  • V-Sync: Disabled.

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

  • GPU: AMD Radeon RX 580 2048SP.
  • CPU: Intel Core i7-9700F.
  • RAM: 16 GB.
  • Operating system: Windows 11.
  • AMD driver: 26.1.1.

A previous Task Manager measurement during gameplay showed:

  • GPU utilization: approximately 86%.
  • Dedicated VRAM usage: 6.6 / 8 GB.
  • RAM usage: 15.3 / 15.9 GB.
  • GPU temperature: approximately 55°C.

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.

## 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 - The severe pink, cyan, green and yellow graphical corruption has improved considerably. - The environment is now much more recognizable. - Some texture artifacts and visual corruption are still present, particularly around vegetation and parts of the environment. - The game is now playable at approximately 30 FPS after significantly reducing the rendering resolution. ### Performance tests I tested the following configurations: **Test 1 — Very low resolution** - Output resolution: 720x400. - Internal resolution: 33%. - Performance: approximately 30 FPS, relatively stable. - Image quality: extremely blurry. **Test 2 — Best playable configuration so far** - Output resolution: 1280x720. - Internal resolution: 58%. - Sharpness: 20%. - Anisotropic filtering: 2x. - Shadow resolution: In-game. - Threaded rendering: Enabled. - Frame generation: Disabled. - V-Sync: Disabled. 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 - GPU: AMD Radeon RX 580 2048SP. - CPU: Intel Core i7-9700F. - RAM: 16 GB. - Operating system: Windows 11. - AMD driver: 26.1.1. A previous Task Manager measurement during gameplay showed: - GPU utilization: approximately 86%. - Dedicated VRAM usage: 6.6 / 8 GB. - RAM usage: 15.3 / 15.9 GB. - GPU temperature: approximately 55°C. ### 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.
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#717
No description provided.