search

ZDoom / gzdoom

GZDoom is a feature centric port for all Doom engine games, based on ZDoom, adding an OpenGL renderer and powerful scripting capabilities
http://zdoom.org
GNU General Public License v3.0
2.33k stars 526 forks source link

[BUG] CTD on Linux/Haskell/NVidia-Quadro mobile with only Doom2 loaded #2586

Open MartinHowe426 opened 1 month ago

MartinHowe426 commented 1 month ago

GZDoom version

4.12.2

Which game are you running with GZDoom?

Doom 2

What Operating System are you using?

Linux x86_64

Please describe your specific OS version

Linux Mint 21.3

Relevant hardware info

i7-4800MQ, NVidia Quadro K2100M

Have you checked that no other similar issue already exists?

A clear and concise description of what the bug is.

GZDoom crashed to the crash reporter window after starting the engine with Doom2 and no other wads loaded. Rebuilt from source immediately afterwards, same result.

Steps to reproduce the behaviour.

Explain how to reproduce

  1. Start gzdoom from Linux terminal
  2. Select DOOM2.WAD from dialogue
  3. Click Play Game

Your configuration

[gzdoom-ini.txt](https://github.com/ZDoom/gzdoom/files/15500160/gzdoom-ini.txt)

Provide a Log

gzdoom.log gzdoom-crash.log

MartinHowe426 commented 1 month ago

Happens with .deb packaged version from zdoom.org AND if I self build. Happens even if no gzdoom.ini file exists.

madame-rachelle commented 1 month ago

Can you compile as RelWithDebInfo and try again? Without symbols we can't see what's happening.

cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo --build .

MartinHowe426 commented 1 month ago

OK will do; will update this evening as have to go back to work now Happens with RAZE also, BTW. BTW, other game engines (e.g, Ironwail, EDuke32) not affected.

MartinHowe426 commented 1 month ago

Hello again; please find attached the GZDoom, and because it may well be the same bug in some shared code, Raze logs:

gzdoom.log gzdoom-crash.log gzdoom-ini.txt

raze.log raze-crash.log raze-ini.txt grpcrccache.txt

(both compiled with RelWithDebInfo)

madame-rachelle commented 1 month ago

The information there is a great deal more useful, though I don't have much understanding what is going on because that is code that I do not often tinker with. My best guess is the device is running out of VRAM, try lowering the screen resolution to see if it helps any, and ensure that you are not using texture scaling.

MartinHowe426 commented 1 month ago

Sure, well turning the resolution down to 320x240 doesn't help.

For texture scaling, I can see several options and config file items with those words; please can you specify what that means and the setting name in the config file that needs changing?

MartinHowe426 commented 1 month ago

PS: FWIW, The Quadro K2100M has 2GB of VRAM, same as my old desktop GT1030 card, and that ran GZDoom with Vulkan just fine.

Also, run GZDoom on the same machine with Windows, fresh GZdoom install, no config file, NVidia WHQL drivers (not studio), it works fine, runs in fullscreen FHD no issues.

Sadly, I suspect this will be an NVidia Linux driver problem; Quadros have always been a bit ropey for games anyway :(

madame-rachelle commented 1 month ago

Well then VRAM might not be the issue. This will require taking a look at by someone else.

Texture scaling I am only referring to things like XBRz, Normal2x/3x/4x, Scale2x/3x/4x, etc.

MartinHowe426 commented 1 month ago

Thanks for looking into it. Let's hope someone is able to have a look; in the meantime it should be possible to fallback on OpenGL.

As to scaling, if that means high resolution texture packs, then no this is with just plain old 1994 DOOM2.WAD :)