Ultrawide crash #1031
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#1031
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.6
What kind of problem
Crash, freeze or black screen
What happened
Started as ultrawide with rtx 5090, inside the Deku tree loads and looks amazing in real 32:9 (not stretched) but crashes after a bit. Tried in Kokiri forest and it crashes as it is loading.
When I revert to 16:9 game is ok.
Could you please have a look at it?
Thank you for your efforts!
Where in the game
Kokiri forest and Deku tree
How often
Every time
Graphics card and driver version
5090 - 621.14
CPU, RAM and operating system
14700k, 64gb, Win11 64bit 25H2
Changes from the defaults
Other software hooked into the game
No, nothing hooked in
hookshot_log.txt
hookshot_log.txt
Screenshots or video
Before you send it
+1 I have the same issue with a windows 11, RTX 4090, and Ryzen 7 7800X3D. I was just about to post as well. I've loaded into lost woods and when I walk back into Kokiri Forest it crashes. It also crashes when I load a save into Kokiri Forest.
hookshot_log.txt
+1 same problem here running on Linux CachyOs. Works fine 16:9, but changing the output resolution from the original always results in crash. Using RTX 4080 and 9800X3D
hookshot_log.txt
+1 Same problem with Cachy OS, cannot go through screen menu with widescreen on
A fix is coming in the next release: the render target pool now scales with the wide picture, so ultrawide and larger output resolutions no longer run out of it. This issue will be closed when that release ships; please retest then.
Fixed in v2.0.8, out now: update from the launcher or download it from Releases. Please reopen with a log if it still happens.