Hello!
I was playing City Of The Damned: Apocalypse (http://www.doomworld.com/idgames/index.php?id=16452) some moments
ago. I reached the part where the amusement park gets plunged into another dimension, killed the monsters outside and then proceeded
to grab the hourglass. The game crashes all of a sudden. After loading a saved game I tried again, wherein the game crashed
again after a few seconds. The mod is therefore unplayable at this moment.
I am using Windows 7 Home Edition (NT 6.1) Build 7600.
[1.5.6.1104] COTD: Apocalypse crash
Moderator: Graf Zahl
-
- Posts: 4
- Joined: Sun Jun 26, 2011 19:47
- Location: Sweden
[1.5.6.1104] COTD: Apocalypse crash
Last edited by CarpetolA on Sun Jun 26, 2011 23:52, edited 3 times in total.
- Enjay
- Developer
- Posts: 4748
- Joined: Tue Aug 30, 2005 23:19
- Location: Scotland
- Contact:
Re: [1.5.6.1104] COTD: Apocalypse crash
Did GZdoom not create a CrashReport.zip file? If it did, why did you not attach the whole file?
-
- Posts: 4
- Joined: Sun Jun 26, 2011 19:47
- Location: Sweden
Re: [1.5.6.1104] COTD: Apocalypse crash
Oh, sorry. I have done it now.Enjay wrote:Did GZdoom not create a CrashReport.zip file? If it did, why did you not attach the whole file?
-
- Global Moderator
- Posts: 308
- Joined: Sun Aug 29, 2010 6:09
Re: [1.5.6.1104] COTD: Apocalypse crash
Try the latest GZDoom build and see if it works.
-
- Posts: 4
- Joined: Sun Jun 26, 2011 19:47
- Location: Sweden
Re: [1.5.6.1104] COTD: Apocalypse crash
It didn't crash this time. There was something I found that could have been the cause of the crash. Two lines with the lineBlue Shadow wrote:Try the latest GZDoom build and see if it works.
horizon special had the first argument set to 2, so I set them to 0 and tried again. The official version of GZDoom still
crashed! I'm at a loss as to what the problem might be.

- Graf Zahl
- GZDoom Developer
- Posts: 7148
- Joined: Wed Jul 20, 2005 9:48
- Location: Germany
- Contact:
Re: [1.5.6.1104] COTD: Apocalypse crash
If it crashed with the offficial version but not the latest one it's probably fixed already.