Repository navigation
Can't open the game after 0.5.0 update (address for opt_two_redraw) #593
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.5.0-alpha.5 (latest)
Game version
1.9.0
Your PC
Windows 11 26H2, RTX 3050 6Gb Laptop, Intel i5 13450HX, Nvidia v621.01
Where in the game
Opening the launcher
What happened, and how to make it happen again
I tried opening the game after compiling shaders and got this error:
Settings
No response
savagewind.log
Save file (for crashes and problems with the game's mechanics)
No response
Before sending
- This report contains no game files, keys, firmware, generated game code or links to copies of the game.
Activity
travisofficialbr-cyber commentedon Nov 9, 2026
same issue here and same gpu 🥀
Fruscinante commentedon Nov 9, 2026
same here, my gpu is a GTX 1060
SalesDW-git commentedon Nov 9, 2026
Same here, gpu Intel UHD graphics
Revivedx commentedon Nov 9, 2026
Hi,
Will investigate this asap.
Everyone else we need your logs to pin point the actual issue.
brunoam1 commentedon Nov 9, 2026
savagewind.log
same problem with RTX 4090
Swordman14 commentedon Nov 9, 2026
savagewind.log
Same issue, rtx 3080
devall96 commentedon Nov 9, 2026
Note: this is an untested theory from an AI (Claude), not my own analysis, and nobody has confirmed it yet. I’m posting it in case it saves time. Please treat it as a lead, check it against the code, and test it before relying on it.
The theory: the logs all stop in take_sites() (runtime/gamelib.c), before the game version is printed. The generator (tools/game_sites.py) treats the opt_two_* and beast_* sites as optional groups and leaves them out when it can’t find them, but runtime/game_sites.h lists 11 of them as required (opt_two_redraw/text/help/pane_calc and the seven beast_*). A game library built without those groups would then be refused at launch with exactly this error. On game version 1.8.2 that would happen every time, since its KNOWN table has none of those sites but 1.8.2 is still set up as supported.
Not verified:
Whether the people here are actually on 1.8.2: the logs end before the version line.
The proposed fix hasn’t been compiled or run in the game. It was only checked with tools/test_game_sites.py.
A quick check for anyone affected: what does extracted/romfs/System/Version.txt in your Savage Wind folder say? If it’s 1.8.2, updating to 1.9.0 and running Set up game files again might fix it. Please report back either way: that’s what would confirm or rule out this theory.
Possible fix (untested): move those 11 sites to GAME_SITES_OPTIONAL. Both features seem to switch themselves off already when their sites are 0 (two_enabled() in game_options.mm, beast_pointer() in pc_cursor.c). Also add a check to tools/test_game_sites.py so a required runtime site can’t belong to an optional group. I have the patch if a maintainer wants it, but it needs a real build and a human test first.
cyberpunkhub commentedon Nov 9, 2026
Update the game to 1.9.0 and running Set up game files again,it works!
daviembrito commentedon Nov 9, 2026
Tried and worked for me as well. Thought i already was on latest version.
Closing the issue :)
brunoam1 commentedon Nov 9, 2026
I can confirm that this actually works; my game was on version 1.8.2, and after updating to 1.9.0, the issue no longer occurs. Thanks!