Seeking information about a problem in AO. This is a crash that occurs in late-game. The screen goes black and I get a typical "Starcraft has encountered an error and must close" ect.
Doesn't seem to be related to what's on the screen. Doesn't produce a log file.
This is the first time I've ever encountered a crash like this.
If anyone's encountered a crash that happens exactly like this, please list all potential causes.
The crash occurs for all players regardless of what they are doing.
Show them your butt, and when you do, slap it so it creates a sound akin to a chorus of screaming spider monkeys flogging a chime with cacti. Only then can you find your destiny at the tip of the shaft.
The game is trying to read the wrong size variable.
Some type of code is being run that isn't correct.
Okay. What might be the cause of that? Iscript? dat entry?
Show them your butt, and when you do, slap it so it creates a sound akin to a chorus of screaming spider monkeys flogging a chime with cacti. Only then can you find your destiny at the tip of the shaft.
Oh, great! That makes me feel a lot better, since now you can't even finish a game in AO before it fucking crashes.
/edit
Okay I think I know what it is.
Post has been edited 1 time(s), last time on Apr 21 2009, 5:14 am by IskatuMesk.
Show them your butt, and when you do, slap it so it creates a sound akin to a chorus of screaming spider monkeys flogging a chime with cacti. Only then can you find your destiny at the tip of the shaft.
Isolating crashes can be a pain. One thing you might try is write a very simple Ai script that attacks with a bunch of the same units over and over and use one of the ZvZ replays. If this unit in question is found to be stable over the course of a few heated battles, move up the tech tree with the script until hopefully one set of units crash the game.
That's about all I can suggest. otherwise it's just a stab in the dark. Seek DofA as well. He's been known to be able to interpret the error report that gets logged in your cache.
None.
Well the thing is, is that it doesn't MAKE an error report at all. It doesn't make an exception report either.
I think I know what it is; if this isn't it I am seriously screwed and will have to go through a ridiculous time-consuming process like the one you mentioned.
I'm sure this one is the cause, though. I knew about it before and never applied a bandaid fix... and now it's biting me in the ass.
Show them your butt, and when you do, slap it so it creates a sound akin to a chorus of screaming spider monkeys flogging a chime with cacti. Only then can you find your destiny at the tip of the shaft.
well good luck. My last crash was a building that still had it's old damage overlay enabled even tho there were more frames added to the .grp. Took me a while to find that overlook.
None.
Well, it just crashed again. This ain't good.
Show them your butt, and when you do, slap it so it creates a sound akin to a chorus of screaming spider monkeys flogging a chime with cacti. Only then can you find your destiny at the tip of the shaft.
I've discerned that the crash has to be related to a unit. However, when AO builds all of its units and idles there is no crash at all. So, it must be related to an attack sequence, a projectile, or potentially a damage overlay I forgot to get rid of.
However, I've verified all of my data and cannot reproduce this crash conventionally.
Show them your butt, and when you do, slap it so it creates a sound akin to a chorus of screaming spider monkeys flogging a chime with cacti. Only then can you find your destiny at the tip of the shaft.
You should try checking all nobrkcodestart and nobrkcodeend opcodes, especially recently added ones/recently modded iscripts. Make sure that all codeblocks that begin with nobrkcodestart's OR nobrkcodeend's have a "wait 1" before themselves. You can also try temporarily commenting out all recently added nobrkcodestart/end's and see if that prevents the crash.
Also: You should try having the AI build one unit at a time. Watch the units that are being built and finished. If a game crashes the moment a particular unit is built, then something is up with that particular unit (unless a different unit was built at the same time).
AI had all of its units up and didn't crash. Had 3's out and they didn't crash (but they did cause the limit expander to freak out and weapon sprites never to exist ever again).
I think it might have been a broken nobrkcode in Syrius' teleport script, but only time will tell if my corrections to it will solve the crash.
Show them your butt, and when you do, slap it so it creates a sound akin to a chorus of screaming spider monkeys flogging a chime with cacti. Only then can you find your destiny at the tip of the shaft.
