GZDoom 4.11.1

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

Moderator: GZDoom Developers

User avatar
Rachael
Posts: 13523
Joined: Tue Jan 13, 2004 1:31 pm
Preferred Pronouns: She/Her

GZDoom 4.11.1

Post by Rachael »

User avatar
Rachael
Posts: 13523
Joined: Tue Jan 13, 2004 1:31 pm
Preferred Pronouns: She/Her

Re: GZDoom 4.11.1

Post by Rachael »

Oops, I published debug symbols in the Linux portable build. I went ahead and stripped them out and named the new build 4.11.1a (for those who prefer smaller downloads), but the old build is still on the Github release just named as -debug instead.
brick
Posts: 47
Joined: Fri Apr 30, 2021 10:22 am
Graphics Processor: nVidia (Modern GZDoom)

Re: GZDoom 4.11.1

Post by brick »

From seeing this changelog, and other things posted in the past (especially by Graf), it seems the goal is to ultimately get rid of OpenGL entirely. I understand the rationale, and personally I use Vulkan and even on my almost decade old hardware it runs so much better. However I wanted to warn you that some wads require OpenGL to run. I played Umbra of Fate not long ago (on GZDoom 4.10) and it crashes almost immediately after loading the map in Vulkan, I assume because of some of its custom shaders. I don't know how feasible it is to have an auto-translator for shader commands, or if it's worth it. For what it's worth, that initial crash didn't happen in ES, but I don't know if there are other problems later, and what the plans are for keeping/removing ES.

As always thank you for the new version and for the bugfixes.
User avatar
Rachael
Posts: 13523
Joined: Tue Jan 13, 2004 1:31 pm
Preferred Pronouns: She/Her

Re: GZDoom 4.11.1

Post by Rachael »

I intend to keep OpenGL around as an option, one way or another, in an unofficial fork if necessary. But it won't get any new features when the decision is made to move forward with Vulkan.

Nevertheless, you should try those wads with VkDoom and see if they run any better.
User avatar
theleo_ua
Posts: 162
Joined: Sun Feb 07, 2016 11:38 am
Operating System Version (Optional): Windows 10
Graphics Processor: ATI/AMD with Vulkan/Metal Support
Location: Ukraine

Re: GZDoom 4.11.1

Post by theleo_ua »

Previously, when I used vulkan, it had artifacts or crashes gzdoom when video memory is full - this is the reason I'm using opengl for now. This is fixed? This is a known issue so I never reported it, but if reports are required, I can report it
User avatar
Rachael
Posts: 13523
Joined: Tue Jan 13, 2004 1:31 pm
Preferred Pronouns: She/Her

Re: GZDoom 4.11.1

Post by Rachael »

Please report it.

Make sure to include your hardware info and what mods/maps you are using.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
Posts: 49053
Joined: Sat Jul 19, 2003 10:19 am
Location: Germany

Re: GZDoom 4.11.1

Post by Graf Zahl »

I never said I'd discontinue OpenGL right now. What I said is that we have to split this into two separate builds because OpenGL's mere presence stands in the way of refactoring the Vulkan backend.
User avatar
Phredreeke
Posts: 292
Joined: Tue Apr 10, 2018 8:14 am

Re: GZDoom 4.11.1

Post by Phredreeke »

brick wrote: Sat Oct 14, 2023 8:37 am I played Umbra of Fate not long ago (on GZDoom 4.10) and it crashes almost immediately after loading the map in Vulkan, I assume because of some of its custom shaders. I don't know how feasible it is to have an auto-translator for shader commands, or if it's worth it. For what it's worth, that initial crash didn't happen in ES, but I don't know if there are other problems later, and what the plans are for keeping/removing ES.
I didn't think GLES supported custom shaders?
User avatar
phantombeta
Posts: 2076
Joined: Thu May 02, 2013 1:27 am
Operating System Version (Optional): Windows 10
Graphics Processor: nVidia with Vulkan support
Location: Brazil

Re: GZDoom 4.11.1

Post by phantombeta »

brick wrote: Sat Oct 14, 2023 8:37 amI don't know how feasible it is to have an auto-translator for shader commands, or if it's worth it.
There already is one. If it's because of a shader, GZDoom will tell you what the error in the shader was, and if it didn't do that, chances are it wasn't the shader.
If something's broken in Vulkan but not OpenGL, and it isn't caused by bad user shaders, you should report it.

FYI, the only reason a shader might work on OpenGL but not on Vulkan is if the shader is relying on GPU vendor quirks.
One of those is that some vendors (*cough*AMD and Nvidia*cough*) love to implement non-extension-gated features over the base shader language spec, and shaders that use those then fail to compile in Vulkan. (they also usually fail on Intel!)
The other big quirk a lot of user shaders accidentally rely on is uninitialized variables. Intel, Nvidia and AMD all initialize those to 0, but the specs specify using uninitialized variables is undefined behaviour. The Vulkan shader compiler GZDoom uses instead leaves those variables uninitialized (which the specs allow), so you end with random, flickering patterns of garbage all over where the shader is being used.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
Posts: 49053
Joined: Sat Jul 19, 2003 10:19 am
Location: Germany

Re: GZDoom 4.11.1

Post by Graf Zahl »

The shader in Umbra of Fate is known to be bugged:

viewtopic.php?t=75731
User avatar
theleo_ua
Posts: 162
Joined: Sun Feb 07, 2016 11:38 am
Operating System Version (Optional): Windows 10
Graphics Processor: ATI/AMD with Vulkan/Metal Support
Location: Ukraine

Re: GZDoom 4.11.1

Post by theleo_ua »

Rachael wrote: Sat Oct 14, 2023 9:21 am Please report it.

Make sure to include your hardware info and what mods/maps you are using.
done, please check when have time: viewtopic.php?t=78344
User avatar
Rachael
Posts: 13523
Joined: Tue Jan 13, 2004 1:31 pm
Preferred Pronouns: She/Her

Re: GZDoom 4.11.1

Post by Rachael »

Thank you.

Return to “ZDoom (and related) News”