DRD Team

hi. i was hoping you could help with this. when i use the wad 'neodoom', at certain points in the game gzdoom crashes. it happens everytime, at level 29 after around a minute of play, or sometimes when i use the bfg type weapon (keyboard #9, the weapon that has a little counter on it and shoots a yellow ball that explodes.), or at times when being attacked by that giant bondage woman. (weird i know).

i'm using version 1.0.3.0

also, after gzdoom crashes, i get the error report, but it wont let me send it, i can only save it. it also wont let me copy the text, otherwise i would have pasted it here. maybe this is because im doing something wrong, i just don't know what it is.

i got the wad from this page:
http://www.brdoom.com/daniel/

its the download under 'neodoom nightmare'. according to the readme, gzdoom is the recommended source port.

thanx in advance,
-dan k


*edit* i can use the bfg weapon thingie more now, but it still crashes at level 29 and other various points. when i dl gzdoom it says its version 1.0.04, but when i have my mouse over it it comes up as 1.0.3.0 . maybe theres no diff, i dunno.

the error message that comes up has this on it:

Summary
Code: C0000005 (Access Violation - Tried to read address 0000008C)
Address: 004669B4

thanx again.

The crash you mention has been fixed for the next version.

Heh, this NeoDoom crash is becoming GZDoom's face bug

Too bad that I need at least 2 more days to release a new version...

heh, i guess i was too stupid too realize i need to save the error info and attach it here. if you still want it i could do it.

did other people have this problem? i did a search and looked all over and didnt see anything similar.

anyway i can't wait for the next version. gzdoom is bar far the best source port, ive had all kinds of troubles with doomlegacy and prboom.
its a notch better than zdoom.

thanks for all of your effort in developing and and updating gzdoom. it is very much appreciated by many people.

yup.

Hi there, I can confirm that the neodoom bug seems to be fixed. That bug was really killing me - many, many, many thanks for fixing that!