It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I was playing on Floor 2 of Mission 3 in Aliens of Gold today when the game crashed suddenly. I thought it was a random DOSBox crash, but when I loaded my save, the game crashed in the same place.
It seems that when ever I try to use a specific push wall hiding a secret area, the game crashes. Can anyone else confirm this? It's not a fatal bug, but it does keep me from getting 100% on Floor 2. I'm attaching a screenshot of the map with the pushwall circled in red.
Thanks in advance. :)
Attachments:
This question / problem has been solved by stonebroimage
tried loadfix ? or temporary disabling the sound ?
avatar
Qbix: tried loadfix ? or temporary disabling the sound ?
Alright, I just tried both of those, but the game still crashed. I changed DOSBox so it wouldn't close out on program exit, and the game gave me seperate error messages depending on if I loaded bstone.bat or bs_aog.exe. I'm thinking it might be a mapping error.
Maybe it's a pushwall attempting to escape off the edge of the map. The game then must crash in order to keep all it's walls for subsequent playthroughs.
Seriously though, does the crash say anything particular? Does it crash to the DosBox prompt (indicating a game crash), or does DosBox itself crash?
It crashed to the dos prompt. The error message was different depending on whether I loaded bstone.bat or bs_aog.exe. With bstone.bat, the dos prompt was filled with a bunch of garbled text and said something like "Jammer.exe has enounctered an error". With bs_aog.exe, a screen with an error code above the prompt appeared. The error code was something like "Error Code 8f".
I can take screenshots if necessary, but I think you're right. I seem to remember Rise of the Triad having a similar problem, ROTT being partially based on Wolf3D from what I understand.
Post edited May 14, 2009 by snarboo
avatar
snarboo: The error code was something like "Error Code 8f".
I can take screenshots if necessary, but I think you're right.

Please give me the exact error code you're getting. If it's something with 8f, it should look like $8F-XX. Give me XX and I can probably tell you what the cause is.
Edit: Well actually, if it's 8F then it's probably due to corrupted data no matter what. Either your savegame is corrupted (try playing from a different save / from scratch and see if you get the same error), or your install itself is corrupted and you should reinstall the game.
If that doesn't work either, try adding the command line parameters noems noxms to the executable (run "bstone noems noxms").
Post edited May 14, 2009 by stonebro
avatar
stonebro: Edit: Well actually, if it's 8F then it's probably due to corrupted data no matter what. Either your savegame is corrupted (try playing from a different save / from scratch and see if you get the same error), or your install itself is corrupted and you should reinstall the game.
Oh, okay. I'll try that and report back. Here's the error code just in case: Unit: 8f Error: 19
avatar
snarboo: Oh, okay. I'll try that and report back. Here's the error code just in case: Unit: 8f Error: 19

8F:19 means that data is being corrupted as it is being loaded from disk into memory. Any of the reasons above could be the cause (i.e. corrupt game files, corrupt save game, or adding the noems noxms command line parameters is what you should check out).
It looks like a corrupted save file. I just tried a fresh run of Mission 3 to the same place on Floor 2 and the push wall worked. Thanks for your help. :)
Post edited May 14, 2009 by snarboo
Wow - such a highly specific and reproducible bug. That exact same secret-wall push just killed the total game for me (DOSBox just closed - no error messages at all).
I guess it indeed had something to do with a game state caused by a corrupted save. I restarted the game and played to that point without saving once, and the wall-push worked fine. Loading/saving seems to work OK after that, but I'm only on Level 3 now - I hope I can finish this mission without a problem!
Hi all,

While it's another clear topic bump, hopefully the following workaround may work.

So yeah, I've also gotten the exact same error (8F:19) after taking care of the *exact* same push wall. I'm not sure about this, but maybe there are less chances of this to occur if you push the wall a short while after entering the map for the first time.

As for the workaround itself: If you don't want to restart play-through of the map, try quickly turning around by ~180 degrees right after pushing the wall. I've at least bypassed the crash this way and later completed the third mission.

I've still had the thought that some hidden memory corruption may be "lingering" through the whole play-through of the mission, but I don't think there should be a reason to worry. There are great chances there's a corruption even if you never get the crash, and that's without using the workaround above.