Texture failed to loading after long time #2434
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#2434
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.1.0
What kind of problem
Graphics (missing, black or wrong-coloured things, lighting, flicker)
What happened
After playing for an hour, certain textures glitch—as shown in the image—but when I restart the game, this graphical bug disappears.
Where in the game
Lon Lon Ranch
How often
Sometimes
Graphics card and driver version
RTX 4060 ti 8Gb, NVIDIA 580.178.04
CPU, RAM and operating system
Ryzen 9 5950X Gb, Linux Ubuntu 24.04.5
Changes from the defaults
No response
Other software hooked into the game
No, nothing hooked in
hookshot_log.txt
hookshot_log.txt
Screenshots or video
Before you send it
Same issue, for me, it doesn't even take an hour, in less time the ground textures (like the soil in Hyrule Field or the rocks on the floor of Dodongo's Cave) end up looking like they do in the image above. Reloading the save file (without restarting the launcher) fixes it, there’s no specific timeframe, it might happen, or it might not
Same issue here too. It happened with the ground textures in Hyrule Field after about 15 minutes of roaming around there. It got fixed after I reloaded the save but I haven't played enough to see if it happens again.
Same issue too
Thanks for the report. Reports of the same problem are now collected in #993, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #993 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.