Savage Wind Configuration window stays black (0.4.1-alpha.4, RX 5700 XT, Vulkan init OK)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Start by reviewing the linked savagewind.log and the configuration window’s rendering and Vulkan initialization entry points; the issue does not name source files or tests. Reproduce on the reported Windows 11 and RX 5700 XT setup, then trace why rendering stops after "[vk] presents on the calling thread". Done means the configuration screen renders its Play, Settings, and game files options.
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 11 (10.0.26300.9711), AMD Radeon RX 5700 XT 8GB (AMD driver 26.10.1, Vulkan 1.4.315), Ryzen 5 2600, 16GB RAM
Where in the game
Savage Wind Configuration screen (before the game starts)
What happened, and how to make it happen again
Expected: the Savage Wind Configuration screen (Play / Settings / game files).
Actual: the window opens but is completely black (only the title bar draws). Nothing is ever rendered. The log shows Vulkan initialising normally and then stops after "[vk] presents on the calling thread", with no further lines.
Steps:
- Run "Savage Wind Configuration.exe" (also tried from a terminal).
- The window opens at 1280x720 and stays black.
Tried, no change:
- Waiting, clicking in the window, resizing/maximizing
- SAVAGEWIND_GPU_OVERLAP=0
- Running from a terminal
Game files:
Running savagewind.exe directly: <write what happens: also black / game starts / crash>
Settings
Never reached the game. Default settings; window 1280x720, 1920x1080 144Hz display, present mode immediate
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
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Revivedx/SavageWindRecomp#532 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Revivedx/SavageWindRecomp#530 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Revivedx/SavageWindRecomp#528 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Revivedx/SavageWindRecomp#527 ·
Maintainers usually reply within 1 day
-
RAM usage is highOpenbug needs-info
Difficulty 5/5 Over a week Newbie friendliness 25/100
Revivedx/SavageWindRecomp#525 · 2 comments ·
Maintainers usually reply within 1 day
All issues in Revivedx/SavageWindRecomp
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 10 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sk3llo/ffmpeg_kit_flutter#176 ·
-
Synth suite fails unless run from the repo root: signal_flow's default machine path is cwd-relativeOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Nimblesite/osprey#370 ·
Maintainers usually reply within 1 day