Black screen with audio on AMD Ryzen Z1 Extreme (Lenovo Legion Go) #426
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot#426
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?
Builder version
sha256:b90d57ffdcb563c1cb2376422fbf3fcfdff90c5af6a8aa380d37351db31f0ded
How you built
Hookshot Builder app (Windows)
Game files given to it
A .nup
The error
Visual Studio or Build Tools version, and Windows SDK version
No response
Operating system and free space on the output drive
Windows 11 100 Gb
Before you send it
hookshot_log.txt
Release https://github.com/NotRexed/Hookshot/releases/tag/ultrawide should fix this: compute shaders now compile in the background instead of freezing the game (AMD took 15-23 s for one, with a black screen meanwhile), twice as many shaders are prepared before the first start, and on AMD the foliage culling shaders are built without the driver optimizer that hung RX 6600-class cards. Please update (run HookshotBuilder.exe, or accept the game's update offer) and tell me if it still happens, with hookshot_log.txt (and hookshot_log.1.txt if you restarted after a crash).
On 2.02. I have same specs and device. Black screen and then device restart after cinematic intro.
hookshot_log.1.txt
hookshot_log.txt
Hi NotRexed,
I'm still experiencing the black screen issue on my Lenovo Legion Go (AMD Ryzen Z1 Extreme), running Hookshot v2.0.5 (source cd9cebb6).
The opening sequence plays perfectly, but when the scene transitions to the Great Deku Tree speaking with Navi, the screen freezes and turns black.
Interestingly, the audio also seems to stall temporarily. It takes approximately 2–3 minutes before I can hear the dialogue/music again, but the screen remains black and frozen.
I've attached my latest
hookshot_log.txt.The log appears to show continued Vulkan activity and frame presentation without an explicit device-lost error.
Could this be related to shader compilation, rendering synchronization, or an AMD-specific issue during scene transitions?
Thank you for your continued work!
hookshot_log.1.txt
hookshot_log.txt
Tracked in #997, follow there. That issue collects every report of AMD handhelds and APUs: black screen, device lost or reboot, and this one is linked from it with its GPU, version and log details. If it still happens on v2.0.6 (https://github.com/NotRexed/Hookshot/releases/tag/v2.0.6; Update next to Play in the launcher), please add a comment there with your
hookshot_log.txt.