GZDoom 3.5.0 game-breaking issue
Moderators: GZDoom Developers, LZDoom Developers, UZDoom Developers
Forum rules
Please be as descriptive as possible in your posts (list your hardware and operating system, the version of the source port you are using, any mods you are running and how they're being loaded, etc.)
This will help others to give you a solution!
Please be as descriptive as possible in your posts (list your hardware and operating system, the version of the source port you are using, any mods you are running and how they're being loaded, etc.)
This will help others to give you a solution!
-
Guest
GZDoom 3.5.0 game-breaking issue
Every time I change to a new level or sometimes just start the game, it crashes and gives me a message saying something like this:
Code: C0000005 (Access Violation - tried to read address 0000006C)
Address: 6929A6B1
Flags: 00000000
There is some bullsh*t here and I don't know what to do about it.
Code: C0000005 (Access Violation - tried to read address 0000006C)
Address: 6929A6B1
Flags: 00000000
There is some bullsh*t here and I don't know what to do about it.
- Caligari87
- Admin
- Posts: 6241
- Joined: Thu Feb 26, 2004 3:02 pm
- Preferred Pronouns: He/Him
- Contact:
Re: GZDoom 3.5.0 game-breaking issue
We need more information. Operating system? Processor type? GPU? Any mods being run? Are your drivers up to date? Pastebin of the crash log?

-
Guest
Re: GZDoom 3.5.0 game-breaking issue
Caligari87 wrote:
> We need more information. Operating system? Processor type? GPU? Any mods being run?
> Are your drivers up to date? [url=https://pastebin.com/]Pastebin[/url] of the crash
> log?
>
>
Windows Vintage build of GZDoom, No mods, just Doom2.wad for this crash but the issue has happened when i use mods as well.
This is the log. All I did was start a game, then change to map 2 to test(it had crashed for the same reason many times before this)
https://pastebin.com/iKVK43BA
> We need more information. Operating system? Processor type? GPU? Any mods being run?
> Are your drivers up to date? [url=https://pastebin.com/]Pastebin[/url] of the crash
> log?
>
>
Windows Vintage build of GZDoom, No mods, just Doom2.wad for this crash but the issue has happened when i use mods as well.
This is the log. All I did was start a game, then change to map 2 to test(it had crashed for the same reason many times before this)
https://pastebin.com/iKVK43BA
- drfrag
- Vintage GZDoom Developer
- Posts: 3207
- Joined: Fri Apr 23, 2004 3:51 am
- Location: Spain
- Contact:
Re: GZDoom 3.5.0 game-breaking issue
Does it happen only with vid_rendermode 4 (hardware opengl)? Does 3.4.1 crash the same?
Do you see the wipe? If not try changing the screen wipe style. Does it still crash?
Do you see the wipe? If not try changing the screen wipe style. Does it still crash?
-
Guest
Re: GZDoom 3.5.0 game-breaking issue
I changed the render mode to Doom Software Renderer, and it seems to have fixed the problem, but at the cost of sh*tty lighting
- drfrag
- Vintage GZDoom Developer
- Posts: 3207
- Joined: Fri Apr 23, 2004 3:51 am
- Location: Spain
- Contact:
Re: GZDoom 3.5.0 game-breaking issue
This looks like a driver problem. What about changing the wipe to none in opengl accelerated mode? And about 3.4.1?
-
Guest
Re: GZDoom 3.5.0 game-breaking issue
The screen wipe doesn't affect it at all, only the rendermode. As for 3.4.1, I would have to check.
- drfrag
- Vintage GZDoom Developer
- Posts: 3207
- Joined: Fri Apr 23, 2004 3:51 am
- Location: Spain
- Contact:
Re: GZDoom 3.5.0 game-breaking issue
Strange, we'll need a full crash report this time.
-
Guest
Re: GZDoom 3.5.0 game-breaking issue
Okay, I made an account. The post by "Cyril Sedgecherk" was me, and "Velma Cabbleville" was also me.
Re: GZDoom 3.5.0 game-breaking issue
As expected it crashes inside Intel OpenGL driver. Who knows what it doesn’t like. These drivers have a long history of various bugs, so this crash is not a big surprise.
- drfrag
- Vintage GZDoom Developer
- Posts: 3207
- Joined: Fri Apr 23, 2004 3:51 am
- Location: Spain
- Contact:
Re: GZDoom 3.5.0 game-breaking issue
Thanks. Could you try now disabling render buffers? (setting gl_renderbuffers to 0).
