DRD Team

I played through DA.WAD (in /newstuff ATM). To get it to work, I had to change "Inventory" to "CustomInventory" and put quotes around 5.56mmcasing in the DECORATE. After that, I played the WAD right through, beat the level, got as far as EndGameC then quit. When I did, a crash report was waiting for me at the desktop. I did have a couple of other programs running at the same time, and it could just be "one of those things" but in case the report is of any use, here it is.

Enjay wrote:I played through DA.WAD (in /newstuff ATM). To get it to work, I had to change "Inventory" to "CustomInventory" and put quotes around 5.56mmcasing in the DECORATE.

Sigh...

Graf Zahl wrote:Sigh...

Yeah, I know. As soon as GZdoom quit with a decorate error I was like "Oh FFS, this standard has been outdated for some time now and this WAD is specifically for GZDoom which did away with this even before official Zdooms".

However, the thing was about 11MB and had taken a few minute to download so I bothered making the changes. Otherwise it would have gone straight to the recycle bin. I don't suppose the DECORATE issues were relevant to the crash anyway as they should have been fixed (by me) before I could get the WAD to load.

OK, I played through again this morning quickly (cheating most of the way) but had no other significant programs running. Again there was a crash message waiting for me when I got to my desktop.

This is the WAD: http://www.doomworld.com/idgames/?id=14520

And again with 1.0.18. This time I only played about half way through then quit. Before I did though, I typed "kill monsters". Not sure if that is relevant. Just doing it at the start of the level doesn't seem to cause the crash, so probably not.

Happens to me too, all the time. Quit = crash report.

Too bad that the map is close to unplayable due to the extreme darkness. The crash address suggests a node problem but since I feel no desire to run this map for the time needed to find it I doubt that this will get fixed - if it is indeed an engine issue and not just some broken map data.

Yeah, it is dark. I wouldn't have kept playing it over and over if I wasn't tryng to see if the bug was repeatable. I just turn up the brightness on my monitor when I play it.

Graf Zahl wrote:Too bad that the map is close to unplayable due to the extreme darkness. The crash address suggests a node problem but since I feel no desire to run this map for the time needed to find it I doubt that this will get fixed - if it is indeed an engine issue and not just some broken map data.

If you think that's bad, you should see the Maulotaur fight. That part alone make the rest of the map seem very playable indeed.