ZDoom

Title is all. gzdoom 2.4 and more version crash with brutal doom when shooting.
But gzdoom 2.2 works well.

Does 3.0.1 work? What version of Brutal Doom? Any other mods being loaded with it? Operating system, computer hardware, etc?

Crash log?

Sorry my simple briefing.

brutal doom version : brutalv20b.pk3 (<---I patched bug in blood.txt. So this is not the cause.)

OS : windows7 64bit

IWAD : freedoom2.wad

gzdoom 3.01 doesn't work too.

This is the crash report. Click view raw to download the crashreport.zip.

https://github.com/kkmin1/kkmin/blob/ma ... Report.zip

If I haven't misread the files, it looks like the crash happened in ig4icd64.dll which looks like something related to an Intel HD Graphics driver?

Yes, my notebook has internal intel HD Graphics card.

Any other PCs are OK? If so, this is my problem.

Is there any solution to this intel HD Graphics card problem?

Anyway, thank wildweasel for your address.

Indeed it crashed inside Intel graphics drivers. If they are up-to-date your only option is to run GZDoom with -glversion 2 command line parameters.

This is probably directly related to this being some old first generation GL 3 hardware with an old and no longer updated driver.
Does this only happen with 2.4 and up and not with 2.2 or 2.3?

gzdoom 2.3 , 2.4 not works. I only tested gzdoom2.2.and above. For below version, I don't know.

Try the attached PK3.
Summon "ModelCrashTest" in the console to test it.
Also try it with the latest GZDoom dev build.

I attached a crash log of my own from 3.1, just so someone can check against it or something. Just posting this because I had a crash that could be the same as this, maybe.

On my nVidia graphics machine, no problem with GZD 3.1.0 and a git build downloaded today.

Could be an Intel issue.
All I know is that it doesn't crash for me on the latest dev build, only on 3.1 and earlier.
I asked Zanieon to see if it happens for him too, since he said Hunter's Moon (his mod) crashes for him in the latest stable GZDoom build IIRC. If it crashes for him too, then it's not an Intel issue.

If it doesn't crash in the latest devbuild then the underlying problem is likely already fixed. Nothing can be done here, in that case.

If it doesn't crash for the OP and it's the same problem they encountered in BD, (It probably is, since BD uses models for tracers and blood) this can be closed, which is why I posted it.
Would be kinda bad if Graf and co. wasted time trying to fix an already fixed bug because the OP didn't test the latest dev build.

Yet another crash inside Intel graphics drivers. There's nothing can be done without having actual hardware to be able to debug it at least. Adding -glversion 2 command line option will probably help.