Page 1 of 1

KQ3 Crash on Restart

Posted: Sat Feb 26, 2011 9:38 am
by mcnewby
KQ3 failed when I pressed the restart button after dying. The screenshot of the error and the crash dump file are attached. Awesome game otherwise, so much nostalgia..

Re: KQ3 Crash on Restart

Posted: Sat Feb 26, 2011 3:09 pm
by navynuke04
Thanks for reporting this. There seems to be an issue with the Restart command within the AGS engine. Funny that it didn't show up during development or beta testing. Still this, is an issue with the engine and not something we can directly fix ourselves. We'll work with the creator of AGS for a resolution.

Re: KQ3 Crash on Restart

Posted: Sat Feb 26, 2011 4:36 pm
by MattinPhilly
I want to "buzz up" this same issue as well, AND it also occurs for me when trying to restore a game. So at the moment I have to start at the beginning each time I want to play, so I would prefer to give it a real go when a fix is in place for it. Is there a place I can go to check on the status of this issue as time passes?

Re: KQ3 Crash on Restart

Posted: Sun Feb 27, 2011 4:47 am
by deonast
Yes I get the same issue, just died 14 mins in and went to restart. I'm on XP SP3 with DEP enabled if that helps at all.
"An exception 0xC0000005 occurred in ACWIN.EXE at EIP = 0x0043B2AA ; program pointer is +25, ACI version 3.20.1110, gtags (3,8)"

I've attached the dump, more dumps might help narrow it down. Note you have some fussy attachment options, doesn't like the extension .dmp or .txt so I zipped it.

Re: KQ3 Crash on Restart

Posted: Sun Feb 27, 2011 5:28 am
by bechtd
Experienced same exact error performing a restart after dying (specifically Manannan losing patience with me for the last time).

Re: KQ3 Crash on Restart

Posted: Fri Apr 22, 2011 8:36 am
by whitehelm
Same problem, restart crashes the game.

Re: KQ3 Crash on Restart

Posted: Fri Apr 22, 2011 9:02 am
by Anonymous Game Creator 2
The crash is apparently due to a glitch caused when the engine loads/restarts a game while the music is in the process of crossfading. It should be fixed in v1.1 which we hope to release soon.