White Screen After Deku Tree's Triforce story #1919
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#1919
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?
Hookshot version
v2.0.14
What kind of problem
Crash, freeze or black screen
What happened
after i beat gomah, take the portal, and talk to deku tree, the godesses scene launches, but lags for a few seconds, and then turns into a white screen, gameplay is impossible after it. Only white screen.
Where in the game
Kokiri Forest, while Deku tree's Godesses cinematic
How often
Every time
Graphics card and driver version
RTX 4070, NVIDIA 621.14
CPU, RAM and operating system
Ryzen 5 7600x, 32 GB RAM, Windows 11 26H2
Changes from the defaults
No response
Other software hooked into the game
No, nothing hooked in
hookshot_log.txt
hookshot_log.1.txt
hookshot_log.2.txt
hookshot_log.3.txt
hookshot_log.4.txt
hookshot_log.txt
Screenshots or video
No response
Before you send it
Thanks. A white screen at the goddesses' story was reported before and got past it after waiting a few minutes; does it get past for you if you wait? Also, what's your Frame rate cap? Above 60, cutscenes and the Gohma fight misbehave (#1742); does it happen with the cap at 60?
Okay, so I tested it again, and the white screen loop occurs when you're trying to watch the cinematic. A couple of seconds later, the cinematic starts lagging and then turns into a white screen that cannot be removed until you relaunch the game.
However, if you skip the cinematic as soon as possible, the white screen loop doesn't occur, and the game continues normally.
I tried with 60fps cap and 165. Same results for both.
Thanks for the report. Reports of the same problem are now collected in #998, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #998 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.