[Tracking] Black screen with audio after the intro / at the Deku Tree cutscene #998
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#998
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?
This issue collects every open report of a black screen with audio after the intro, so there is one place to follow it. The individual reports were closed pointing here; their logs, screenshots and discussion stay in each linked issue.
Summary
After the opening, often when the Deku Tree talks to Navi, the 3D picture goes black while the audio and HUD keep going, or the picture freezes with the audio still playing. There are several causes:
Intel GPUs, GPUs without mesh shaders and AMD handhelds have their own trackers.
Affected GPUs and versions
Evidence from the logs
HOS_NO_RENDERER_WAIT=1, normal with it (RX 7600, driver 32.0.32015.7029, v2.0.2).Workarounds
HOS_NO_RENDERER_WAIT=1(#120).mesh shaders no, see the GPUs-without-mesh-shaders tracker.Reports merged here (9 issues, about 25 people)
Adding a report
Please update to v2.0.6 first (https://github.com/NotRexed/Hookshot/releases/tag/v2.0.6; Update next to Play in the launcher). Please add: GPU, driver, version, and
hookshot_log.txtfrom a run that went black.All tracking issues
I hit two crashes just after the opening cutscene on Hookshot v2.0.14, built with the official Windows Builder. I'm on Windows 11 with an RTX 4060 Ti, NVIDIA driver 610.88, and 32 GB of RAM.
Windows logged a resource exhaustion event (ID 2004) just before each crash, with about 45.6 GiB committed out of a 45.8 GiB limit. The game log showed
std::bad_allocduring shader translation, followed by a crash on the Vulkan presentation thread.I closed my other apps and retried. This time I got past the cutscene. I'm sharing this in case it helps narrow down which intro crashes are related to system memory pressure.
More reports of this, collected here: