New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mac M1 and x86_64 crash during gameplay when dying or loading saved game #137
Comments
Save games are architecture specific. In other words, you can't use saves from M1 on x86_64 or vice versa. |
Maybe I wasn't clear, but I tested each architecture with their own saves, created on a new game. |
What is the error? Are you referring to quick saves? I'm not understanding what you are describing. |
I'm referring to loading previously saved games, both manual saved games or quicksaves. Loading a previously saved game during gameplay crashes the game. Also, during gameplay, if you die, the game also crashes after the screen finishes fading to black (probably because it tries to load the last saved game.) The engine quietly crashes, closing the app and returning to the desktop. I've included the output from the terminal in case that helps. My machine is a MacBookAir10,1 16gb ram |
I've just recompiled again and the issue stopped (at least on M1, didn't test on x86_64). |
I'm not sure what's going on...I'm not able to reproduce it. |
I think it happened because I originally changed the app bundle name from iowolfsp.app to Wolfenstein.app |
Good to know. Glad you got it working |
Thanks for the help! |
I had exactly same issue as I also changed the .app bundle from |
Same issue here. Renaming back / re-downloading & using new executables does not solve. Any other tips perhaps? Thanks |
Same here |
In both architectures, I can load a saved game in the main menu, but only if I've not already started a game.
If I'm already playing, the game crashes when I die or when I try to load a saved game.
Happens both in the provided x86_64 binary and also in a freshly compiled M1 binary, without having made any alterations to wolfconfig.cfg
The text was updated successfully, but these errors were encountered: