Game: Black screen after opening cutscene or loading a save on Intel Arc A580 #1874

Open
opened 2026-11-20 14:03:23 +00:00 by BeanBot · 2 comments
Member

Reported on Discord

Longshot version and channel

v3.0.0 (source 87cb36aa), release candidate.

What happened and steps

After updating to v3.0.0 release candidate, the game shows a flickering pipeline-loader screen with the FPS counter over itself and may not show the opening cutscene. Audio and menu controls still work. Loading the existing Kakariko Village autosave reaches a black loading screen that does not proceed. On a new game, the Deku Tree intro cutscene plays, then the screen goes black. Lowering settings to the lowest did not change the outcome. The reporter says this happens every time since updating to this release candidate.

The supplied video shows the load menu and then a black loading screen with the loading icon.

Where in the game

After the opening Deku Tree cutscene on a new game, and when loading the Kakariko Village autosave.

GPU and driver

Intel Arc A580 Graphics, 8 GB VRAM; driver 32.0.101.9175.

CPU, RAM and operating system

AMD Ryzen 5 5500, 16 GB RAM, Windows 11 Home.

Logs

The supplied logs identify v3.0.0 (source 87cb36aa), output resolution 1280x720. In the new-game log, the renderer reports a compute program was not translated and substituted with a linear upscale:

[hos host] vk: program 72ba090c70fe2614 does not translate: its dispatch replaced by a linear upscale of 0x100000f0200 640x360 (vk 122) into 0x1001f0ffe00 1280x720 (vk 122)

The log also records very long GPU dispatches during the attempted intro; no crash is reported at the end of the submitted logs.

Still unknown

Exact graphics settings/upscaler, whether the game eventually progresses after waiting at the black screen, and whether the issue occurs in the same way with the existing save and new game beyond the stated attempts.

Attachments

  • New_game_log.txt
  • longshot_log.1.txt
  • longshot_log.2.txt
  • longshot_log.3.txt
  • longshot_log.4.txt

Related but distinct: #1731 tracks an Intel UHD driver crash during the Great Deku Tree intro; this report is an Arc A580 black screen without a reported crash.

Reported on [Discord](https://discord.com/channels/1569849200047427645/1573322036715982909/1573326333025452136) ### Longshot version and channel v3.0.0 (source 87cb36aa), release candidate. ### What happened and steps After updating to v3.0.0 release candidate, the game shows a flickering pipeline-loader screen with the FPS counter over itself and may not show the opening cutscene. Audio and menu controls still work. Loading the existing Kakariko Village autosave reaches a black loading screen that does not proceed. On a new game, the Deku Tree intro cutscene plays, then the screen goes black. Lowering settings to the lowest did not change the outcome. The reporter says this happens every time since updating to this release candidate. The supplied video shows the load menu and then a black loading screen with the loading icon. ### Where in the game After the opening Deku Tree cutscene on a new game, and when loading the Kakariko Village autosave. ### GPU and driver Intel Arc A580 Graphics, 8 GB VRAM; driver 32.0.101.9175. ### CPU, RAM and operating system AMD Ryzen 5 5500, 16 GB RAM, Windows 11 Home. ### Logs The supplied logs identify v3.0.0 (source 87cb36aa), output resolution 1280x720. In the new-game log, the renderer reports a compute program was not translated and substituted with a linear upscale: ```text [hos host] vk: program 72ba090c70fe2614 does not translate: its dispatch replaced by a linear upscale of 0x100000f0200 640x360 (vk 122) into 0x1001f0ffe00 1280x720 (vk 122) ``` The log also records very long GPU dispatches during the attempted intro; no crash is reported at the end of the submitted logs. ### Still unknown Exact graphics settings/upscaler, whether the game eventually progresses after waiting at the black screen, and whether the issue occurs in the same way with the existing save and new game beyond the stated attempts. ### Attachments - New_game_log.txt - longshot_log.1.txt - longshot_log.2.txt - longshot_log.3.txt - longshot_log.4.txt Related but distinct: #1731 tracks an Intel UHD driver crash during the Great Deku Tree intro; this report is an Arc A580 black screen without a reported crash.
Author
Member
Files from the Discord report: - [New_game_log.txt](https://git.magicbean.dev/attachments/3afbe5bf-d2e0-440f-becc-cd6f9a51d245) - [longshot_log.1.txt](https://git.magicbean.dev/attachments/e77be1cb-cd89-4f03-97f7-0c3fc97214c4) - [longshot_log.2.txt](https://git.magicbean.dev/attachments/2e071df9-0fe6-4973-973a-8bfe7c8bce8d) - [longshot_log.3.txt](https://git.magicbean.dev/attachments/4ab8a0c7-114e-4ce9-b274-17b0eaab099f) - [longshot_log.4.txt](https://git.magicbean.dev/attachments/54296cb5-7c66-4a80-9bc2-a2436632e057)
Author
Member

From Discord:

From the reporter's Discord post: on v3.0.0 stable with an AMD Ryzen Z1 Extreme, audio continues but the display goes black when entering Hyrule Castle and the Great Deku Tree. They attached five logs (longshot_log.txt and .1–.4). The main log identifies v3.0.0 (source 87cb36aa), 2048x1152 output, and reaches 30 FPS, but has repeated vk: submit ... failed (-2) lines near the end. GPU model/driver and OS still need confirmation from the reporter; the available description only identifies the Ryzen Z1 Extreme.

From [Discord](https://discord.com/channels/1569849200047427645/1573359365304487977/1573359365304487977): From the reporter's Discord post: on v3.0.0 stable with an AMD Ryzen Z1 Extreme, audio continues but the display goes black when entering Hyrule Castle and the Great Deku Tree. They attached five logs (`longshot_log.txt` and `.1`–`.4`). The main log identifies v3.0.0 (source 87cb36aa), 2048x1152 output, and reaches 30 FPS, but has repeated `vk: submit ... failed (-2)` lines near the end. GPU model/driver and OS still need confirmation from the reporter; the available description only identifies the Ryzen Z1 Extreme.
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#1874
No description provided.