UZDoom 5.0.0

[Boondorl]

Please do not report bugs in this thread! All bugs should be submitted here.
Downloads

• Windows
• Linux
• macOS

Release

After an over year-long development cycle and a truckload of internal reworks, UZDoom 5.0 has finally arrived! Starring bone manipulations for IQM models, significantly improved controller support (including haptic feedback!), the overhauled multiplayer, ZScript debug support, and much more, we knew this version would need a full upgrade. We appreciate everyone being patient since we know it took a while, but we promise it was worth the wait. With the updater being added, we can now make smaller releases more often so long periods of development like this should be an issue of the past. Our focus going forward will be on making releases as big new features are added.

The full changelog can be found here for more details, but some highlights of this update include:

• An improved launcher interface! Its theming now has both light and dark modes and a Multiplayer tab has been added for setting up net games.
• The automatic updater. No longer will you have to remember to check the forums to see if there's any new updates; we've got you covered on that one.
• Significantly improved controller support, haptic feedback included. Aiming has never felt better.
• New accessibility options for controlling lighting alongside a gamma rework to make adjusting it a smoother experience.
• Multiplayer has been rewritten from the ground up to make connecting easier than ever. Alongside this is a smorgasbord of quality of life changes to make games easier to control for hosts.
• New fog modes for mappers to play around with.
• Richer font rendering for improved language support. Languages that traditionally relied on forks like 简体中文 are now native to UZDoom.
• Tooltips for menus. No more need for writing huge blocks of static text as this feature has both standard and dynamic hover tooltips.
• DAP debug server support for ZScript. You can now use a debugger to step through your code instead of a million print statements.
• Bone manipulations for IQM models. Enemies can finally look at their targets as they chase them.
• Lots and lots of bugfixes and other additions.

And this has only scratched the surface of what's been added! We're excited to finally put this out into the world as our first big release since launch, and we'll be keeping this level of ambition as we look ahead. We've already got some big plans for the future, so stay tuned for your more regularly scheduled updates (we'll try not to take two years this time).

UPDATE:

Wanted to mention we're aware of the situation with Windows not liking the new updater executable. This seems to have come from a last minute fix we made, changing its hash and causing it to become untrusted again. We're currently looking into solutions, but this should naturally go away over time as it becomes trusted again. Apologies for the inconvenience.

To give some peace of mind, all of our releases are done directly through GitHub's building interface meaning there's no middle party involved at all. All relevant code and actions are available on the GitHub repo and we include GitHub's logs with releases so they can be audited.

[Unicide]

Congrats on the release!!!
Can't wait to see what will be done with the new features, and any other future features :3

[Enjay]

Fantastic news. Well done and thank you to everyone who has worked so hard to make this happen.

[phinet]

Happy UZDoom day y'all. It's been a long time coming, but I'm really happy it's finally out. My partner requested I mention her in the release speech we give

[AvzinElkein]

I think Windows 11 is deleting the updater before I can launch it. Is it because I set it to run as administrator?

[Jay0]

I think Windows 11 is deleting the updater before I can launch it. Is it because I set it to run as administrator?

i think you use uzdoom in C:/Program Files/ or any other protected folder you can't really use the auto-updater without windows complaining yea

[Ep1cgamerXD]

my computer keeps mistaking it as a virus, is there any explination behind it?

[Enjay]

As you say, it is "mistaking it as a virus". It's a false positive. Sometimes new exe files do take a while to be recognised by the various virus defence programs. So, it should eventually become recognised as a clean file.

I realise that doesn't help in the short term. You may be able to set an exception for your virus program to allow it. You may also be able to report a false positive to your antivirus provider and that might speed up the process of the file being recognised as clean.

[Nash]

Also, to give some additional context (and reassurance): these release binaries are now compiled online, on Github's servers. Long gone are the days where the engine is compiled on someone's computer at home, and then uploaded by hand. We don't do that anymore.

So, if anything, rest assured that the binaries are typically guaranteed to be safe and free from external tampering.

[AvzinElkein]

I think Windows 11 is deleting the updater before I can launch it. Is it because I set it to run as administrator?

i think you use uzdoom in C:/Program Files/ or any other protected folder you can't really use the auto-updater without windows complaining yea

Nope; I am using C:/Windows-UZDoom/.

[phinet]

Also, to give some additional context (and reassurance): these release binaries are now compiled online, on Github's servers. Long gone are the days where the engine is compiled on someone's computer at home, and then uploaded by hand. We don't do that anymore.

So, if anything, rest assured that the binaries are typically guaranteed to be safe and free from external tampering.

Adding on to this: the build process is logged and public, so it's possible to audit if something weird is going on.Logs can be found here (or click the Logs link on the release itself)

The windows defender thing is concerning, and we're actively looking into a way to have windows trust the application. As far as we know, waiting is the best option for now.

[boostaddicted]

Besides deactivating Windows Defender (WD) entirely, I can't get the browser to allow me to download UZDoom 5.0 at all. No matter how many times I seem to click "allow", WD "ML - machine learning" really seems to think that there is something wrong with the new zip package. Is it possible to use code signing certificates? EV code signing certs cost money, but they provide immediate trust levels when used to sign software.

[edward850]

The issue isn't code signing as far as I can tell, it's what the application is and how it acts. Code signing usually affects how SmartScreen acts with Web zone flagging (an exe downloaded from the internet is flagged as not-executable by default, and running such an exe will have smartscreen verify it and inform the user if it's unknown), but this issue is the executable pattern matches the behaviour of a trojan and anti-vrus is instead the thing getting involved.

The updater exe quite specifically takes a package and replaces another executable with the contents of said package. Now this for uzdoom is perfectly safe but under another context is the same thing a trojan does, and anti-virus signatures aren't smart enough to know the difference.

If this behaviour is merged into the main uzdoom executable instead and it replaces itself (you can't delete a running executable but you can rename it, even itself), this should resolve the detection as self-replacement should be less likely to trigger such detection.

To be clear it isn't a trojan and cannot be reliably used as a trojan, so you're safe.

[Blzut3]

EV code signing certs cost money, but they provide immediate trust levels when used to sign software.

EV code signing certificates are not available to individuals, so besides the money for the certificate you'd have to set up a whole non profit org or something. But also apparently the meta has shifted towards Azure code signing and EV certificates aren't all that anymore.

It's hard to say if code signing would solve this. I know the decentralized certificates won't since I know someone who has had a binary that didn't change much that had a similar issue and they resorted to just pulling an old build forward instead of rebuilding every release. However with Azure's code signing Microsoft would have a copy of every binary which presumably they run against anti-virus so something like this would probably flag it for review (since it's either a false positive or the user sohuld be banned and added to the revocation list), but I don't have any personal experience to say if they have such a process in place.

[Deybar_TECH]

Excellent!
Lots of new improvements.

Bone manipulations for IQM models:

"Enemies can finally look at their targets as they chase them"

It seems that will be a common feature
for every 3D model from now!