GZDoom 4.4.1 released

News about ZDoom, its child ports, or any closely related projects.
[ZDoom Home] [Documentation (Wiki)] [Official News] [Downloads] [Discord]
[🔎 Google This Site]

[Tap Here for Mobile-Friendly Forums]

Moderator: GZDoom Developers

GZDoom 4.4.1 released

Postby Graf Zahl » Wed Jun 10, 2020 12:29 pm

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)


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
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: GZDoom 4.4.1 released

Postby Cacodemon345 » Wed Jun 10, 2020 1:02 pm

Cacodemon345
 
Joined: 22 Dec 2017
Discord: Cacodemon345#9151
Github ID: Cacodemon345
Operating System: Windows 10/8.1/8/201x 64-bit
Graphics Processor: ATI/AMD (Modern GZDoom)

Re: GZDoom 4.4.1 released

Postby Kamil » Wed Jun 10, 2020 1:02 pm

Wow. New update. I hope that I will no longer have problems with RAM :)
Kamil
 
Joined: 21 Sep 2019
Discord: @Kamil#8122
Operating System: Windows Vista/7/2008 64-bit
Graphics Processor: nVidia with Vulkan support

Re: GZDoom 4.4.1 released

Postby Rachael » Wed Jun 10, 2020 1:04 pm

Kamil wrote: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.
User avatar
Rachael
Webmaster
 
Joined: 13 Jan 2004
Discord: Rachael#3767
Twitch ID: madamerachelle
Github ID: madame-rachelle
Operating System: Windows 10/8.1/8/201x 64-bit
OS Test Version: No (Using Stable Public Version)
Graphics Processor: nVidia with Vulkan support

Re: GZDoom 4.4.1 released

Postby Graf Zahl » Wed Jun 10, 2020 1:06 pm

Except for the memory leak, but that only brings it back to 4.3.3
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: GZDoom 4.4.1 released

Postby Kamil » Wed Jun 10, 2020 1:29 pm

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 :)
Kamil
 
Joined: 21 Sep 2019
Discord: @Kamil#8122
Operating System: Windows Vista/7/2008 64-bit
Graphics Processor: nVidia with Vulkan support

Re: GZDoom 4.4.1 released

Postby Eonfge » Wed Jun 10, 2020 2:05 pm

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.
Eonfge
 
Joined: 10 Sep 2019
Github ID: https://github.com/eonfge
Operating System: RedHat-like Linux (RHEL, Fedora, CentOS, etc) 64-bit
Graphics Processor: nVidia (Modern GZDoom)

Re: GZDoom 4.4.1 released

Postby Graf Zahl » Wed Jun 10, 2020 2:17 pm

The biggest change was a refactor of the texture management. Compiling the rest will take a bit of time, the list is very long. ;)
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: GZDoom 4.4.1 released

Postby Kamil » Wed Jun 10, 2020 2:43 pm

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 :)
Last edited by Kamil on Wed Jun 10, 2020 2:45 pm, edited 1 time in total.
Kamil
 
Joined: 21 Sep 2019
Discord: @Kamil#8122
Operating System: Windows Vista/7/2008 64-bit
Graphics Processor: nVidia with Vulkan support

Re: GZDoom 4.4.1 released

Postby Redneckerz » Wed Jun 10, 2020 2:44 pm

User avatar
Redneckerz
To it's ports i may have seen
Spotlight Team
 
Joined: 25 Nov 2019
Discord: Redneckerz#8399
Operating System: Windows Vista/7/2008 64-bit
Graphics Processor: nVidia (Legacy GZDoom)

Re: GZDoom 4.4.1 released

Postby Mug of Bro » Wed Jun 10, 2020 6:29 pm

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.
User avatar
Mug of Bro
 
Joined: 01 Jun 2020
Operating System: Windows 10/8.1/8/201x 64-bit
OS Test Version: No (Using Stable Public Version)
Graphics Processor: nVidia with Vulkan support

Re: GZDoom 4.4.1 released

Postby Cacodemon345 » Thu Jun 11, 2020 12:10 pm

Mug of Bro wrote: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.
Cacodemon345
 
Joined: 22 Dec 2017
Discord: Cacodemon345#9151
Github ID: Cacodemon345
Operating System: Windows 10/8.1/8/201x 64-bit
Graphics Processor: ATI/AMD (Modern GZDoom)

Re: GZDoom 4.4.1 released

Postby SPZ1 » Fri Jun 12, 2020 10:41 am

:thumb: :thumb: :thumb:

:instagib:
User avatar
SPZ1
 
Joined: 02 Aug 2017
Location: Illinois

Re: GZDoom 4.4.1 released

Postby Remaker » Sat Jun 13, 2020 9:18 pm

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?
User avatar
Remaker
OMG A BARREL WATCH YOUR SHOTS
 
Joined: 01 Apr 2017
Location: Burger land.
Operating System: Mac OS X 10.8 or later
Graphics Processor: Intel (Modern GZDoom)

Re: GZDoom 4.4.1 released

Postby _mental_ » Sun Jun 14, 2020 12:30 am

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.
_mental_
 
 
 
Joined: 07 Aug 2011


Return to ZDoom (and related) News

Who is online

Users browsing this forum: No registered users and 0 guests