Welcome to the ZDoom Forums!

Where can I find early UZDOOM builds, particularly between 4.14.3 stable and 5.0.0-pre1? I'm trying to catch a nasty bug in the Brutal Doom mod that does not exist in 4.14.3 (and in GZDOOM), but is already present in 5.0.0-pre1 and in all later builds up to 5.0.0-pre163.


We don't have ...

Ok actually the game started working all of a sudden on gzdoom but i just had to reinstall my hard drive and I’ve run into the same issue again with gzdoom not spawning particle effect. It wouldn’t work for a few days and then it started working do you think it has something to do with Microsoft ...

That's a fair concern. While we do review every change to CI, we respect your decision.

Blzut3 wrote: Tue Dec 09, 2025 1:12 am Not necessarily comfortable turning over my private key for CI to do it.

Would you be comfortable directly adding the keys to the UZD github org? They're write-only, so we have no way of seeing the values. If you're comfortable with that, we can add you to the org.

CherubCorps wrote: Sun Sep 28, 2025 5:38 am Did you adjust the screen size with the "+", "-" keys? Go into scaling options and make sure it is set to 11.

Yes, that was it. I have no idea why I didn't think to try that. Thank you very much.

Okay, so I don't see anything strange in you config file (other than running gzdoom 4.14 , the latest is 4.14.2 ). Loading it with my copy of psxdoomce everything works perfectly.

You say that you are using 3.11.1.2 ? The version I have (the latest afaik) is 3.11.1 . Where are you getting the mod ...

Hello, cool mod!

I've been completely unable to use the hud from the mod. I've tried dev builds, 4.14.2, 4.13.2, both on windows and linux. I've double checked alternative hud is disabled as in the help screen says. It's always the classic bar at the bottom, but red -- not the hud as shown in the ...

This is intentional. The upcoming release of gzdoom will release with a refreshed theme in order to differentiate itself from other ports using the same launcher. A plurality of current developers agree that the default theme will be a light one. There are talks about adding theme switching, but ...

Okay, some testing your fix works perfectly on all of my systems, including the pi that started this all. Gonna open a PR, but I'd like to credit you. What name + email can I put into the commit metadata? Feel free to dm.

Edit:
If you're not comfortable sharing stuff like that, I can also credit as ...

Maybe AMD/Mesa vs nVidia? lemming mentioned having nVidia using the proprietary driver, I have AMD with Mesa 25.0.7 (latest in Debian unstable). What do you have?


AMD on both of my computers. Need to get an nvidia card for testing at some point...


Device: AMD Radeon 780M Graphics (radeonsi ...

Thank you for testing that! I'm sorry I can't be of more help. I'm still completely incapable of reproducing this. I think this might be an issue specific to your machine, but I'll keep an eye out for similar reports.

I'm not sure if it's in the debian repos, but you might try switching from sdl2 ...

Okay, this is interesting. Unfortunately, I'm still unable to replicate the issue you're having. Thankfully, native wayland with sdl2 (non compat) is not the default, so I don't think this will end up being an issue (though I might be wrong).

I'm wondering if this has something to do with your ...

> It's actually working fine for me in both X11 and Wayland native output windows

Awesome! Glad to hear. I'll send the fix upstream soon. Sorry for breaking things in the first place.

> which still freezes after script parsing ... without the game/window showing

I think this is a different issue ...

Thank you for the information.

I believe I have a fix. Would you be able to test if this fixes the issue for you?

https://github.com/the-phinet/gzdoom/tr ... um-t-80790

(branch fix-forum-t-80790, commit 26f147c2b8)

Edit: added fix for missing loading screen in commit affbcb5034

I have finally been able to re-create this with debian 13.

It seems the only difference between my working systems and my non-working system is the sdl version. All of my working systems are using `sdl3 (3.2.x)` with `sd2-compat (2.32.x)`, and my non-working system is using `sdl2 (2.32.4)` directly ...