Vah Ruta transition crash / Infinite loading screen before entering the dungeon
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 43/100
Research direction
Start by reading the attached savagewind.log and checking the Vah Ruta transition path it points to; the payload does not name source files or tests. Reproduce the hang from a save before entering the dungeon, then trace the transition and loading behavior. Done when the interior loads after the cutscene and the reported reproduction no longer hangs.
Written by the indexing model from the issue text.
Description
Before you start
- I'm on the latest release, and the bug still happens there.
- I searched the existing issues and this one isn't reported yet.
Savage Wind version
0.4.1-alpha.4 (latest)
Game version
1.9.0
Your PC
Windows 10, NVIDIA GeForce GTX 1650 621.14, Intel Core i3 12100f
Where in the game
Lanayru region, East Reservoir Lake, entering Divine Beast Vah Ruta dungeon
What happened, and how to make it happen again
What I expected: The game should load the interior of the Divine Beast Vah Ruta after the arrow-shooting phase and the cutscene.
What I saw instead: The game plays the cutscene but then gets stuck on an infinite loading screen. The loading bar stays at 0% and does not advance.
Steps to reproduce: Load a save file before entering Vah Ruta, shoot the four pink targets on the beast, watch or skip the cutscene, and the loading screen will hang forever.
Settings
30 fps, 1280x720 windowed (tested multiple configurations, all hang)
savagewind.log
Before sending
- This report contains no game files, keys, firmware, generated game code, save files or links to copies of the game.
- Dominant language
- C
- Stars
- 811
- Forks
- 37
- Avg merge
- 17m
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Revivedx/SavageWindRecomp
-
Surround soundOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Revivedx/SavageWindRecomp#573 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Revivedx/SavageWindRecomp#569 · 1 comment · 2 reactions ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Revivedx/SavageWindRecomp#568 ·
Maintainers usually reply within 1 day
-
Fatal:svcBreakOpenbug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Revivedx/SavageWindRecomp#567 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 44/100
Revivedx/SavageWindRecomp#561 · 2 comments ·
Maintainers usually reply within 1 day
All issues in Revivedx/SavageWindRecomp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
要トリアージ 辞書
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
yksr-melt/Meltype#1625 · 1 reaction ·
Maintainers usually reply within 1 day
-
kind/bug priority/medium qa_automation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yugabyte/yugabyte-db#37324 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
tree-sitter/tree-sitter#6111 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
joncampbell123/dosbox-x#6797 ·
Maintainers usually reply within 1 day