In this case I'd say Vulkan is Babylon 5 because it's better written, goes deeper, and it performs better...

Vulkan is a modern cross-platform 3D graphics API

open source graphics api, said to be more rounded and efficient than gl.

Vulkan runs very bad on my Windows PC.
Vulkan does not perform better on my Windows PC. Always fluctuates between 40FPS, 60FPS, 20FPS up and down, while DirectX 12 I can always run at 180FPS.

But also harder to develop for.

They always say "What is Vulkan?" They never ask "How is Vulkan?"

opengl's younger brother

That's a bit over the top because your eyes can only see 640kB.

Haha, love the throwback joke at the emd. But yeah, Vulkan's performance can be hit or miss depending on the setup.

i'm working on a lil thing called mVulcanium
so micro controllers have a much more real gpu like extensions.
thus microcontrollers can render ps2 - 3 level visuals on a tiny chipset.

gona be epic and i hope it gets more people making fantasy consoles on Arduino, esp32 ect.
:)

Thanks everyone for the answers. That's some really interesting stuff. Really impressed by the way software development can make hardware work better, even older ones. Makes you think about how little effort companies put nowadays on gaming optimization...

An update anyway:

I tried everything I could, and I mean it. Everything I could from console commands to mods to drivers reinstalls to one by one graphical settings experimentation, everything. But the glitches and visual artefacts continue to happen, unfortunately.
Its interesting: I can run the game at 60 fps, but there are always some kind of shadow and particle artefacts on the screen, no matter what I changed in the settings. On Linux through Heroic, Lutris, Wine and Proton, the issue wasn't present. There were no graphical artefacts, but weirdly, no matter what setting I changed, FPS never went above 20.

So my theory is that Mesa/Vulkan updates on Linux work well for rendering, but my system has no strength enough to brute force the compatibility layer performance hit. while on Windows, the game is so well optimized that ther'es not that much hit to brute force it, but my CPU is so old that its 6th gen technology cannot render graphics correctly and there's no support for Vulkan on this specific cpu in Windows.

By further researching I also learned that there's one setting that only works correctly with 4K resolutions and up on some CPUs/GPUs, after the latest updates, which seems to be the ones from which GOG's version is based of.
If you're curious, its the 'Directional Occlusion' advanced graphical setting, which has some in-engine problems rendering in lower resolutions. Even though I deactivate it though, the glitches still happened.
It seems the driver updates that made this game compatible were only present on 7th Gen and up Intel CPUs, but mine is a 2017 6th gen, so no matter what I tried, I couldn't make it work well enough.

I also discovered that it seems the latest GOG's DOOM 2016 version is somehow different from the latest Steam version because some mods that allow a user to activate Developer Console don't work on GOG's DOOM, but do on Steams, apparently, through what I was able to research when trying to activate developer's console using mods and community tools.

(DOOMLegacy, DOOMExtractor and the likes.)

Anyway... that's it, I will report this to GOG and request a refund.
Thanks again for the answers.

Lame as HELL.

Stop buying games you know your hardware can’t run... so you can save up and buy a ‘second hand’ potato pc that can run more games than your current one can.

Stop hurting this store normalizing abuse with fellow freeloaders backing you up.
I want more new releases here.

Show you support this release and donate the Key to someone who can’t buy it but can play the game (your support only costs $4), or the next time have the decency to omit things that I guarantee you, take away nothing from your evening lullaby.

Tried this: https://www.reddit.com/r/lowspecgamer/comments/v2ewfz/how_to_run_doom_2016_on_any_old_intel_hd_graphics/

Also, and unless I've read it wrong, Devmode seems to work just as the Steam one (I have both versions).

Yup, this was the first post I found when initially researching.
By what I tested this file can't be permanently modified without the engine resetting the important Shadow values when launching the game. (Because Shadows are some of the commonly known most demanding graphics rendering setting.)
If files are modified to be "Read Only" after modifying said shadow values, the game doesn't even open.

The only value that I manage to change in this file and in game through Console Commands is the "r_AtlasShadowWidth", which can be changed to 0 for some pretty amazing results performance wise, the other values though crashes the game instantly when changed using Console Commands.

And Im sorry, I might not have been clear when talking about the Devmode console command.

GOG's version does indeed allow for the use of the Console ('~' key) and does list some of the commands.
But, as it is with Steam apparently for what I researched, but can't confirm because I never owned DOOM 2016 there, there are many Console Commands that are blocked from being used or even listed when pressing TAB for autocompletion in the Console Command in game, that is, the full list of Developer Commands used in the engine to test and modify whatever you want on the go are blocked from being shown or used without "Developer Permissions" lets say.

Community, therefore, created this mod (3 different links for some of the places I found and versions I've tested):

https://www.reddit.com/r/DOOM2016Mods/comments/ahfv2q/doomlegacymod_v201901_updated_for_the_latest_doom/
https://www.moddb.com/downloads/doomlegacymod-v201901
https://github.com/brunoanc/DOOMLegacyMod

If I understood its wizarding correctly, what this mod does is it searches for the Steam Stub section of the binary to then find where a specific region blocks all the Developer Commands from being used in the Console Command and allow it to be activated with 'devmode_enable 1', allowing for all engine commands to be used, not only the common "God Mod", "Cheats list", "FOV" and other basic commands which wouldn't help to modify graphics rendering.

Anyway, my point is:
This modification could/can be used to give the player access to all the engine commands allowing for results like this: (Delisted video because some of these commands no longer work, as explained by the owner of the channel in comments.)
https://www.youtube.com/watch?v=iFQIbD1FZHc

When I tried to install this mod (DOOMLegacyMod, both 2019 and 2024 versions) in GOG's galaxy build (because I downloaded the game using Heroic and lgogdownloader which uses Galaxy API) the game doesn't open. It just crashes.
Reading the log files it seemed to me to be exactly what I initially understood:
The program checks for the Steam Stub section of the binary, which well, isn't present on GOG's version and it crashes.

At least that's what I understood from it all with my tests. So yeah... I tried everything I think I could to make it work without glitches and graphical artefacts.
My idea was to use Developer Mode Console with all its 'secret developer only' engine commands to try to remove some rendering effects one by one to discover which one was causing the floating shadowy artefacts on screen.

This idea might have worked because on some other games I've done this before.
For example, deactivating glitched rain effects because they don't render well on lower resolutions.
Some games render textures in high values, so when lowering resolutions, these textures would still render with its default values, so rain droplets would render taking up the whole screen. Deactivating some rain effects would make these glitched rain effects disappear, therefore, allowing for clean view of the map and screen.
(This is a real example by the way that I've done to play a game before.)

Why should I buy games here when I can look for your detailed feedback first? What will be the next game you’ll try everything you could to make it run on hardware that is not supported on?

Then you wonder why the biggest sharks in the ocean continue to DRM their games. No shit you don’t own this game on Steam, you’d think long and hard before buying this game there. This is called being an opportunist.

Three words for you to end this fable: MINIMUM SYSTEM REQUIREMENTS

that or gift this Key to someone in the community, they’ll thank you for it. This would show your support for this new entry but apparently you couldn’t care less about that.