Try to load Phocas2.wad and get this errors, this are the first lines of the report.txt:
Code: C0000005 (Access Violation - tried to read address 02C8A003)
Address: 005BF6CF
Flags: 00000000
Windows NT 5.1 Build 2600 Service Pack 3
I also tried to play Remain III, and at the moment I came in the first greater area, gzdoom crashed without any report.
Any ideas, hints?
Re: Problems with some gzdoom specific wads
Posted: Mon May 04, 2009 22:52
by wildweasel
Is this a blue screen of death, or is GZDoom producing a proper crash dialogue with a "Save Report to Disk" button?
Re: Problems with some gzdoom specific wads
Posted: Tue May 05, 2009 0:01
by NeoHippo
doomfanatic wrote:... Any ideas, hints?
You did not specify which version of GZDoom you are playing with.
Perhaps, try an earlier version.
Did GZDoom load everything required? To find out, use this command line gzdoom.exe -logfile startup.txt
or make an autoexec.cfg file with logfile startup.txt in your gzdoom folder and point to it in the ini file, ie:
No need to make an autoexec. You can add +logfile log.txt to the command line.
Re: Problems with some gzdoom specific wads
Posted: Tue May 05, 2009 1:41
by NeoHippo
Enjay wrote:No need to make an autoexec. You can add +logfile log.txt to the command line.
I am almost certain, that was one of the options I mentioned.
Re: Problems with some gzdoom specific wads
Posted: Tue May 05, 2009 14:36
by doomfanatic
I tried to play it with GZDoom 1.2.1 (r309M) started by ZDL 3.1 or now by ZDL 3.1a
@wildweasel
No blue screen no crash report. Gzdoom closed and I came back to the desktop (only Remain III). A proper crash report produced gzdoom only by the Phocas2.wad
Today I also tried Austerity. GZdoom crashed unfortunately also with crash report, at the moment I opened the yellow door in map01
If it should be helpful I could reproduce the crahes and post the full report text ...
edit:
okay, I didn't loaded lights.pk3, brightsmap.pk3 and gzdoom.pk3. But with the last gzdoom won't start anyway:
Execution could not continue.
Script error, "gzdoom.pk3:actors/actor.txt" line 25:
variables can only be imported by internal class and actor definitions!
Re: Problems with some gzdoom specific wads
Posted: Tue May 05, 2009 16:12
by Graf Zahl
How did you get that one?
Can you post the entire command line GZDoom is started with?
Re: Problems with some gzdoom specific wads
Posted: Tue May 05, 2009 16:58
by doomfanatic
Command line? As I wrote I launch it with ZDL 3.1a.
I loaded gzoom.pk3 twice It will be automatically loaded by gzdoom, isn't it?
I added lights.pk3 and brightmaps.pk3 in as externel files to load and also gzdoom.pk3...
And here is what ZDL added:
adding E:/doom/gzdoom/gzdoom.pk3
adding E:/Doomsday/data/jdoom/DOOM2.WAD (2919 lumps)
adding E:/Doom/gzdoom/brightmaps.pk3
adding E:/Doom/gzdoom/lights.pk3
adding E:/Doom/gzdoom/gzdoom.pk3
So I removed gzdoom.pk3 from ZDLs external files list, but no changes with external wads...
