GZDoom 4.4.1 released

[Graf Zahl]

Notice: The survey is currently closed. GZDoom 4.4.0 does not include the survey code that 4.2.0 did.
Important: 4.4.x will be the last GZDoom release to feature a 32 bit build. Starting with 4.5.0 there will only be 64 bit versions.

Download (OpenGL 3.3 and higher for hardware rendering, Direct3D 9 or later for software rendering)

• Windows 64-bit
• Windows 32-bit
• Linux 64-bit
• Linux 32-bit
• macOS
• Source

Highlights
4.4.1 is a bugfix release addressing a few issues that were reported for 4.4.0

Details

• added a CCMD that lists all CVARS which don't have a description.
• mapped "Smooth mouse" back to m_filter CVAR and removed smooth_mouse.
• Fix compilation on DragonFly BSD
• fixed code that deternines when to upscale a texture.
• fixed fallback lookup for multipatch textures referencing themselves as patch.
• fixed the burn shader.
• do not allow playing sounds during PlayerFinishLevel.
• added 3 more texture samplers to the shaders to compensate for the now always occupied slots for brightmap, glow and detail.
• fixed calculation of allocated memory for garbage collection
• since we already got lots of CVAR descriptions from the menu's content, let's use that as CVAR description if none is explicitly provided.
• fixed bad bit operations when calculating the base palette remap.
• fixed: The mutipatch texture builder did not set the source lump.
• fixed: When reopening a lump, the full file name must be used.
• fixed crash with texture upscaling in the truecolor software renderer.
• Fixed crash rendering 3D floors without ceiling or floor textures in software.
• Fixed wrong MINDEMOVERSION which was committed in https://github.com/coelckers/gzdoom/pul ... 9012890a33
• Fix Bag of Holding not increasing Firemace ammo capacity
• fixed compilation of non-x86 targets

[Cacodemon345]

https://drive.google.com/file/d/1NmCBus ... sp=sharing
Information from this post still mostly applies: viewtopic.php?f=1&t=68860#p1154636

[Kamil]

Wow. New update. I hope that I will no longer have problems with RAM

[Rachael]

Wow. New update. I hope that I will no longer have problems with RAM

Doesn't seem a lot changed with memory management. You may just have to upgrade your system.

[Graf Zahl]

Except for the memory leak, but that only brings it back to 4.3.3

[Kamil]

Wow. I have not seen a problem with RAM yet. I just finished level 1 from After Doom + PB 3.0
Oh yeah. I completed all 3 levels in After Doom + PB 3.0 and did not encounter a memory leak

[Eonfge]

Linux builds on their way again.

@Graf, what are the major changes in 4.4.0 actually? I'm a bit interested because there are some other projects using this engine and sooner or later I'll have to update those too.

[Graf Zahl]

The biggest change was a refactor of the texture management. Compiling the rest will take a bit of time, the list is very long.

[Kamil]

I finished all 3 levels again in After Doom + PB 3.0, but this time with Vulkan. There were no problems with memory leak
This is a really great GZDoom update for me

[Redneckerz]

DoomWiki page updated.

[Mug of Bro]

Update seems pretty solid aside from a new issue I encountered.

Midi playback will be far too loud, not reflecting how the slider is set in the options. My current workaround is to lower the master volume down, and then back up again.

I should specify that this wasn't happening for me in v4.3.3, and I am using OmniMIDI for the MIDI device.

Edit:
Scratch that, this seems to be an issue with my operating system's MIDI device drivers in general. Windows seems to be unregistering OmniMIDI after reboot consistently.
This seems to also have cropped up due to a Windows 10 update. No surprises there.

[Cacodemon345]

Edit:
Scratch that, this seems to be an issue with my operating system's MIDI device drivers in general. Windows seems to be unregistering OmniMIDI after reboot consistently.
This seems to also have cropped up due to a Windows 10 update. No surprises there.

The same has been happening to CoolSoft MIDI drivers too. It seems to be related to the Audio Endpoint Builder service removing the driver registry files, due to the usage of unsupported methods.

[SPZ1]

[Zemakat]

Coming in to report that the bug mentioned in this thread viewtopic.php?f=104&t=68623 still remains even with the updated ALSOFT 1.20.1 version.

Chris suggested that it may be the version of "zmusic" or "libsndfile" on Mac. I don't really know what these are. Is this an issue exclusive to the GZDoom Mac version? Or is it something regarding my own Mac's specs?

[_mental_]

Try to find the last version of GZDoom that doesn’t have this problem.
Also, this is not bug reporting topic. Please continue discussion in the initial one.