Package Details: vkdoom-git v25.6.0+581+gca2db6204-1

Git Clone URL: https://aur.archlinux.org/vkdoom-git.git (read-only, click to copy)
Package Base: vkdoom-git
Description: Feature centric port for all Doom engine games, with a focus on Vulkan and modern computers (git version)
Upstream URL: https://vkdoom.org/
Keywords: doom
Licenses: GPL3, BSD, LGPL3
Conflicts: vkdoom, vkdoom-bin-nightly
Provides: vkdoom, vkdoom-bin-nightly
Submitter: MaddieMewmews
Maintainer: MaddieMewmews
Last Packager: MaddieMewmews
Votes: 4
Popularity: 0.44
First Submitted: 2023-09-16 18:59 (UTC)
Last Updated: 2025-10-15 20:23 (UTC)

Dependencies (32)

Required by (0)

Sources (3)

Latest Comments

1 2 3 Next › Last »

MaddieMewmews commented on 2025-10-15 20:23 (UTC)

Rebased to vkdoom_m fork since VKDoom upstream is no longer publicly maintained

MarisaDOOM commented on 2025-08-04 10:08 (UTC) (edited on 2025-08-08 11:04 (UTC) by MarisaDOOM)

Heads up: ZMusic as a submodule may be pulled into this as well.

Might come in handy considering that at the moment upstream GZDoom and VKDoom have major discrepancies in which version of that library they need (which I guess will only last until GZDoom 4.15 comes out and VKDoom merges all of its changes, but there's no telling when that will come to happen).

Edit: Never mind, a merge with upstream GZDoom just happened.

MarisaDOOM commented on 2025-05-29 19:24 (UTC)

VKDoom started bundling its own launcher files as of 7df36af, so the desktop and svg files in the package could be removed, I guess.

kinker31 commented on 2025-04-19 22:06 (UTC)

Mesa and VKDoom really don't seem to be getting along with each other recently. Attempting to launch the program anywhere but the terminal gives me a segfault, with an "address not mapped to object" error given as the reason. Running VKDoom through gdb gives me the following:

Thread 7 "vkdoom" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffddffd6c0 (LWP 257375)]
Downloading 238.82 K source file /usr/src/debug/mesa/build/../mesa-25.0.4/src/compiler/nir/nir.h
0x00007fffee862ce3 in nir_src_is_const () at ../mesa-25.0.4/src/compiler/nir/nir.h:1214
1214       return src.ssa->parent_instr->type == nir_instr_type_load_const;
(gdb) backtrace
#0  0x00007fffee862ce3 in nir_src_is_const () at ../mesa-25.0.4/src/compiler/nir/nir.h:1214
#1  lower_rq_proceed () at ../mesa-25.0.4/src/amd/vulkan/nir/radv_nir_lower_ray_queries.c:558
#2  radv_nir_lower_ray_queries () at ../mesa-25.0.4/src/amd/vulkan/nir/radv_nir_lower_ray_queries.c:703
#3  0x00007fffee90446c in radv_shader_spirv_to_nir () at ../mesa-25.0.4/src/amd/vulkan/radv_shader.c:506
#4  0x00007fffee8eac34 in radv_graphics_shaders_compile () at ../mesa-25.0.4/src/amd/vulkan/radv_pipeline_graphics.c:2621
#5  0x00007fffee8edafd in radv_graphics_pipeline_compile () at ../mesa-25.0.4/src/amd/vulkan/radv_pipeline_graphics.c:3020
#6  0x00007fffee8ef818 in radv_graphics_pipeline_init () at ../mesa-25.0.4/src/amd/vulkan/radv_pipeline_graphics.c:3408
#7  0x00007fffee8f0462 in radv_graphics_pipeline_create () at ../mesa-25.0.4/src/amd/vulkan/radv_pipeline_graphics.c:3469
#8  radv_CreateGraphicsPipelines () at ../mesa-25.0.4/src/amd/vulkan/radv_pipeline_graphics.c:3620
#9  0x0000555555ef5c52 in ??? ()
#10 0x000055555588e23a in ??? ()
#11 0x000055555588e022 in ??? ()
#12 0x00007ffff62e1f74 in std::execute_native_thread_routine (__p=0x555557d7a130)
    at /usr/src/debug/gcc/gcc/libstdc++-v3/src/c++11/thread.cc:104
#13 0x00007ffff60a370a in start_thread (arg=<optimized out>) at pthread_create.c:448
#14 0x00007ffff6127aac in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

(As a side note, the compilation problems I had previously was either already solved, or solved with an updated PKGBUILD. Also, I wasn't able to get all the seperate debug info downloaded, as some of them time out before the download completes.)

MaddieMewmews commented on 2025-04-04 00:19 (UTC)

VKTool's symlink issue seems to have already been fixed upstream, it built as a standalone executable on my end. If this still isn't the case for you, please let me know.

MrSoup678 commented on 2025-04-03 09:43 (UTC)

It seems that VKDoom now has also VKTool executable.

In the package it is built as a symlink to build directory, which is unusable.

MarisaDOOM commented on 2025-03-12 23:01 (UTC)

Yeah, so, about that printf patch, 4.14.1 stuff got merged now and it's no longer needed.

MarisaDOOM commented on 2024-12-19 08:09 (UTC) (edited on 2024-12-19 11:37 (UTC) by MarisaDOOM)

GZDoom 4.14 changes have been merged, so this package will also need -Wno-error=format-security added to the compiler flags to bypass a printf misuse.

Edit: Seems like the gzdoom aur package just adds a patch to correct the misuse instead, so there's that as an option.

MaddieMewmews commented on 2024-10-21 21:56 (UTC)

ZMusic has been updated, so that's no longer an issue. Your vulkan-1.2 issue is likely a conflict with the upstream VkDoom project, not this package. Test to see if the prebuilt binaries (from the github) work first, otherwise it's likely an incompatibility with the program itself and your hardware.

1 2 3 Next › Last »