GZDoom Freezing

[Furyspark]

Issue: The game freezes at times. So far I've only encountered it during combat, and has never occurred when just walking around looking where to go, for example. When the game freezes this way, I have to force close it, since it doesn't respond to anything anymore.

GZDoom Version: g4.10.0-m (on Linux), v4.10.0 (on Windows)

Mods used: Project Brutality (downloaded from their master branch on GitHub a few days ago) and Golden Souls 2. Not simultaneously. Rather, it happens in both. Not tried any other mod or just a base Doom 2 WAD since this issue popped up, though.

Generic things I've tried: I've tried switching between the OpenGL and Vulkan renderer. This doesn't seem to matter.

OS: This seems to happen both on Arch Linux and Windows 11 (dual boot, no VMs).

Hardware:
GPU: AMD Radeon 6700 XT
CPU: Intel i7 8700k
RAM: 64 GB

Video: https://youtu.be/Fq3aPnrIeD4
The video is from a save game where I seem to be able to trigger the freeze relatively frequently, both on Windows and Linux. I've included the attempts to get it to freeze as well. Maybe it'll help grant some insight into what's happening.

[Rachael]

Moving to technical issues, as this is likely a hardware issue.

To rule out software issues, please post your .ini files from both Linux and Windows. (Feel free to edit out your name if it appears in either of them)

Unfortunately though, this is a classic symptom of hardware overheating. If it's not that, the drivers could be bad, but that's way less likely since AMD does not fully develop the Linux drivers like they do with Windows - that's handled by the Linux community.

[Graf Zahl]

First thing to check is your fans. If they are clogged up with dust the system cannot be cooled anymore.

[Furyspark]

Here's both INIs in question: https://pastebin.com/1A1azxQd (Linux) and https://pastebin.com/6KBnG6xH (Windows)

I'm fairly sure I cleaned out the fans about 6 months ago, though. Might have been slightly longer ago than that, admittedly.

Just to be certain, I kept up a temperature monitor for my CPU and GPU on my other screen while triggering the freeze again. The CPU didn't go above 40 degrees celcius, and the GPU didn't go above 50 degrees celcius. Not that they really had much of a chance to become all that hot anyway, since I can trigger it within 30 seconds in that save.

It might be a hardware issue, but I don't really have any issues while playing other games, like Final Fantasy 14, Rogue Legacy 2, OpenRA and EDuke32.

Let me know if there's any other information I can provide.

[Rachael]

Played Golden Souls 2 on your INI on my system and did not get a lockup.

For reference, that is this: Ryzen 7 3800X (8-core 3.9 GHz) / 32 GB RAM / NVidia RTX 3060 / Win11 Pro

If you are getting lockups only on GZDoom and not other games, the problem may be on your CPU. Either it's overheating, or could also be pulling too much power from your PSU. The only way to rule them out is to swap out the components if you have extras. It could also be your motherboard - if a capacitor is bad, random weird things tend to occur, also.

[drfrag]

Looks like a mod bug, another infinite loop?

[Rachael]

Yeah we haven't ruled that out, yet. I doubt PB authors would knowingly publish code that does that, but anything can slip past their radar.

(But then, why would GS2 have these problems too? - It's a simpler and more polished mod, and is in release stages, so it should not have issues like that)

[Furyspark]

Unfortunately, I don't have a spare CPU or motherboard to try out. That said, those two components are the oldest in my computer, and I've been eyeing an AMD Ryzen of some sorts for a while now. Might be time to bite the bullet and get to spending, I guess.

Might be a couple of weeks before I get them, though, and since I'm seemingly the only one with this issue, I suppose it's best to close this thread. At least unless someone else pipes up about it.

Ah well, thanks anyway.

In regards to it being a mod issue, I don't think that's the case. Like Rachael said, it happens in 2 mods. But also, I have a friend who also plays Project Brutality (who also downloaded the mod very recently) who doesn't seem to have this issue.

This issue seems to have popped up somewhere in the past 2 or 3 months for me. I remember doing 2 playthroughs of Golden Souls 2 before then just fine. And since no one else has reported anything of this nature, it seems that it's an issue specifically with GZDoom, on my computer specifically, for some reason.

Just to add: I've tried resetting my motherboard settings a few hours ago, but that also did not solve the issue.

Anyway, I'll see about acquiring that new hardware. Hopefully it'll solve it. If not, I will probably reopen this thread, or open a new thread and reference to this one. But that'll be a while off, most likely. Or, if someone has any other ideas I could try in the meantime, please let me know.

[Kappes Buur]

That's odd, I have a totally different experience when playing GoldenSouls2_1.4 with Project_Brutality_Final.

I cannot get past the first level because I cannot jump the full height up any cliff, I'm bound to the bottom floor. All I can do is teleport between start, house and shop, and that's it.

GoldenSouls2_1.4 by itself works great.

[Furyspark]

That's something completely different, though. That just happens when you combine 2 gameplay altering mods. Not really unexpected, imo.

I was actually talking about Golden Souls 2 and Project Brutality both having this issue, separately. Other mods will probably have this issue too, but I just haven't played any other mods since this became an issue for me. I suppose just playing base Doom 2 in GZDoom might trigger it as well over here, but I'm not sure I could go back to that after having played mods long enough to get it to trigger.

[Furyspark]

It also freezes on my laptop. That said, though, it's very likely a mod issue after all: https://github.com/pa1nki113r/Project_B ... issues/990

I do vividly remember a similar freeze in Golden Souls 2 in the last map of the 3rd world, though. Since it happened in 2 mods, I figured it was likely a general issue with GZDoom. But it's probably an issue with both mods, then.

My apologies for this wild goose chase.