Bugs that have been investigated and resolved somehow.
Moderator: GZDoom Developers
Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead,
make a new thread here .
Captain Red
Posts: 14Joined: Sat Jan 03, 2004 3:14 am
Post by Captain Red Sat Jan 03, 2004 3:25 am
This might have already been solved but I couldnt find a relevant thread...
Random and constant crashes
Operating system: windows 98 (not 98SE)
DirectX: 8.0
Graphics card: GeForce MX400
Speed: 533mhz
RAM: 256mb
Wad file: All of them!
Zdoom version 60.cab
It doesnt seem to make a difference what wad Im using or what I'm doing, or even witch version of zdoom Im using, Zdoom will at some point drop out and give me the following message:
Code: ACCESS_VIOLATION
I suspect that it might be my PC more then Zdoom in this case, ether way, why is this happening?
Virgil
Posts: 154Joined: Sun Sep 28, 2003 10:01 pm
Post by Virgil Sat Jan 03, 2004 4:52 am
Do you always run it using 800*600 with 16bpp and the -nommx command? Have you tried fiddling with those 3 args?
Hirogen2
Posts: 2033Joined: Sat Jul 19, 2003 6:15 amOperating System Version (Optional): Tumbleweed x64Graphics Processor: Intel with Vulkan/Metal SupportLocation: Central Germany
Post by Hirogen2 Sat Jan 03, 2004 5:29 am
dwforums2 worked fine for me. Apart from that ZDoom doesnot support 16 bpp and disabling MMX is something I never even remotely tried. Try launching ZDoom from the command line, without any funky launcher, and w/o some of these args.
Captain Red
Posts: 14Joined: Sat Jan 03, 2004 3:14 am
Post by Captain Red Sat Jan 03, 2004 5:48 am
Ok, I've used all the cabs from 40.cab to 60.cab (and I mean every last one of them ) and it still happened. As for launchers well, yes I do use the old ZDLaunch.exe. Generally I have the resolution at 800x600 at 16bpp (witch is set using the launcher), I have MMX enabled.
Captain Red
Posts: 14Joined: Sat Jan 03, 2004 3:14 am
Post by Captain Red Sat Jan 03, 2004 6:00 am
different wad, different resolution, no launcher:
Same thing:
Code: ACCESS_VIOLATION
randi
Site Admin
Posts: 7749Joined: Wed Jul 09, 2003 10:30 pm
Post by randi Thu Jan 08, 2004 4:54 pm
What if you set r_columnmethod to 0?
Captain Red
Posts: 14Joined: Sat Jan 03, 2004 3:14 am
Post by Captain Red Fri Jan 09, 2004 4:09 am
I'd say that did the trick! I've been mucking around with it for a while, and it's been going fine! thanks boss!
Captain Red
Posts: 14Joined: Sat Jan 03, 2004 3:14 am
Post by Captain Red Fri Jan 09, 2004 4:55 am
spoke to soon, though it did last longer...
Code: ACCESS_VIOLATION
randi
Site Admin
Posts: 7749Joined: Wed Jul 09, 2003 10:30 pm
Post by randi Thu Jan 29, 2004 7:56 pm
Captain Red wrote: so what was it doing?
The first one happened while drawing a sprite. The other two appear to have happened while making a monster walk. Alas, this seems to be unique to you, so off to vexing bugs this goes. My suspicion is memory corruption.
