andy5995

I didn't see much there about Intel, what I have on my laptop. But as I mentioned, the drivers I have installed seem to be ok. The game runs with Vulkan enabled if I use a self-built binary instead of the Ubuntu 1804 AppImage. I'll post your suggestion on the ticket though. Thanks @hyperion

I chatted with @sternstaub in the matrix channel and ze didn't ask me to include it.

@hyperionThe problem has been consistent with all of them so far. So far the reports have been from people (including me) on Arch-based systems. If they are using an Intel or AMD GPU, the Vulkan backend is disabled. More details on the GitHub ticket I linked above. I'm glad to hear it's working for you though! Which distro are you using?

@vladislavbelov@Stan` @hyperionRegarding the appimage problem with the Vulkan backend disabled, I got this reply from one of the AppImage maintainers So... no surprise there. I was able to bundle libvulkan.so into the appimage, and had the same problem. I then ran `ldd pyrogenesis | grep vulkan` and found no reference to libvulkan. How is libvulkan being referenced normally when pyrogenesis is run?

If Vulkan is enabled in the config, but the 0ad-spirv mod is not enabled, the game crashes. I've noticed since I first started testing with the Vulkan backend, and last checked at r27513. I have to edit user.cfg to change the backend to opengl, then enable the mod, then set the backend to Vulkan again. Sound: AlcInit success, using OpenAL Soft FILES| UserReport written to '/home/andy/.config/0ad/logs/userreport_hwdetect.txt' TIMER| RunHardwareDetection: 4.66227 ms FILES| Hardware details written to '/home/andy/.config/0ad/logs/system_info.txt' TIMER| write_sys_info: 16.2635 ms Assertion failed: "0 && (L"Can't find a usable technique")" Location: ShaderManager.cpp:269 (LoadTechnique) Call stack: (0x56156f637a5e) /tmp/.mount_0ad-0.GI6udT/usr/bin/pyrogenesis(+0x637a5e) [0x56156f637a5e] (0x56156f5ec261) /tmp/.mount_0ad-0.GI6udT/usr/bin/pyrogenesis(+0x5ec261) [0x56156f5ec261] (0x56156f5ed7eb) /tmp/.mount_0ad-0.GI6udT/usr/bin/pyrogenesis(+0x5ed7eb) [0x56156f5ed7eb] (0x56156f5ee064) /tmp/.mount_0ad-0.GI6udT/usr/bin/pyrogenesis(+0x5ee064) [0x56156f5ee064] (0x56156f3b8641) /tmp/.mount_0ad-0.GI6udT/usr/bin/pyrogenesis(+0x3b8641) [0x56156f3b8641] (0x56156f3ba5a8) /tmp/.mount_0ad-0.GI6udT/usr/bin/pyrogenesis(+0x3ba5a8) [0x56156f3ba5a8] (0x56156f3ba81c) /tmp/.mount_0ad-0.GI6udT/usr/bin/pyrogenesis(+0x3ba81c) [0x56156f3ba81c] (0x56156f3e7659) /tmp/.mount_0ad-0.GI6udT/usr/bin/pyrogenesis(+0x3e7659) [0x56156f3e7659] (0x56156f3e7914) /tmp/.mount_0ad-0.GI6udT/usr/bin/pyrogenesis(+0x3e7914) [0x56156f3e7914] (0x56156f3ed68c) /tmp/.mount_0ad-0.GI6udT/usr/bin/pyrogenesis(+0x3ed68c) [0x56156f3ed68c] (0x56156f2af1cd) /tmp/.mount_0ad-0.GI6udT/usr/bin/pyrogenesis(+0x2af1cd) [0x56156f2af1cd] (0x56156f0ad5f8) /tmp/.mount_0ad-0.GI6udT/usr/bin/pyrogenesis(+0xad5f8) [0x56156f0ad5f8] (0x56156f099478) /tmp/.mount_0ad-0.GI6udT/usr/bin/pyrogenesis(+0x99478) [0x56156f099478] (0x7f3ccf43c290) /usr/lib/libc.so.6(+0x23290) [0x7f3ccf43c290] (0x7f3ccf43c34a) /usr/lib/libc.so.6(__libc_start_main+0x8a) [0x7f3ccf43c34a] (0x56156f0aae4a) /tmp/.mount_0ad-0.GI6udT/usr/bin/pyrogenesis(+0xaae4a) [0x56156f0aae4a] errno = 0 (No error reported here) OS error = ? (C)ontinue, (S)uppress, (B)reak, Launch (D)ebugger, or (E)xit? e Redirecting call to abort() to mozalloc_abort Segmentation fault (core dumped)

I installed Ubuntu Focal on my Laptop (with the Intel GPU). I built 0ad from svn and Vulkan was detected. The AppImage I built with Focal didn't detect Vulkan on that laptop. So that tells me this issue is an AppImage problem, not a 0ad problem. It's a safe bet that the same would hold true for builds on Bionic.

An AppImage I made in an Ubuntu Jammy container worked on my Laptop with the Intel video. An AppImage I made in a Focal container did not. I opened a ticket on the AppImage repo and posted a summary. @Stan`@vladislavbelov@Jammyjamjamman

Oh, I was talking about using a build environment in a docker container to create the AppImage. I don't know anything about running graphical apps from a docker container. I think the image would be pretty huge. It would contain a base OS, plus the deps, plus the game. Also, escalated privileges are needed to run docker (which may not be a problem because escalated privileges are need to install the game). Although... might be worth someone's time to try it sometime and see the results. That would be another forum thread though. Maybe split this into a separate topic@Stan`?

Without. I just now applied the patch and it worked on Manjaro. I left a comment on D3127. Thanks.

@vladislavbelov I made an AppImage in a Manjaro build environment and that ran (on my laptop with the Intel) with Vulkan enabled (Yay!). Maybe the vulkan libraries from Ubuntu bionic aren't playing correctly with the drivers on newer distros? Or the vulkan drivers on Manjaro can't play well with a program (inside the AppImage) linking to different versions of vulkan? I think the next logical step would be for me to build an AppImage in an Ubuntu Focal, or Jammy (or Debian Bullseye) environment, and see how that runs on my Manjaro laptop. That would definitively answer the question of whether the vulkan drivers on one system can interact with a binary built with other libs (which in this case are included inside the AppImage). What do you think? cc @Jammyjamjamman@Stan` I haven't tried the test yet. Do you still need me to?

Ok. I had js91 installed. I tried recompiling but got the same errors @Stan`mentioned above.

@hyperionsm? What library is that and where are the sources? I can't find it available in Manjaro or the AUR.

On both systems I was running 0ad from an AppImage. On the desktop it worked. @Jammyjamjammanhad a similar problem. His graphics card has an AMD chipset. He was able to use Vulkan with the Refresh2025 program I mentioned. But it didn't work with the 0ad AppImage. He may report here later himself with his details.

I don't see that package is available for Manjaro. I have vulkan-intel installed on my Laptop, nvidia-dkms on my desktop. @vladislavbelovI was on my laptop when I gave you those logs yesterday. On my desktop, Vulkan with the 0ad AppImage worked. Laptop: 0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) (prog-if 00 [VGA controller]) Desktop: 01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050] (rev a1) (prog-if 00 [VGA controller]) The distro on both systems is Manjaro. I didn't have to install anything extra yet. Same output on both systems when I run: I ran Refresh 2025_Linux (Binary will attempt to run in Vulkan), on my Laptop and it worked (images attached) For the config, I set the res to 1920x1080 and quality to Ultra.

@vladislavbelov I rebuilt after adding 'LOGWARNING("%s", SDL_GetError());' and this was the new message in the console: WARNING: Installed Vulkan doesn't implement the VK_KHR_surface extension That was built in Ubuntu bionic with the available libvulkan-dev package from the bionic repo.

I got this from running the AppImage I made. More detailed logs attached. vulkan_andy5995_r27455_appimage.zip

Done.

Thanks. I checked and saw that core.h wasn't even included in the 4.0.0 upstream version of fmtlib.

I filed a bug report

Chatting with @Stan`helped me figure out the problem core.h isn't in the bionic libfmt-dev package (though it must have been at some point because I'm using the same build environment as I was using for the a26 appimage) https://packages.ubuntu.com/bionic/amd64/libfmt-dev/filelist It's in the corresponding Debian buster package though https://packages.debian.org/buster/amd64/libfmt-dev/filelist

On Ubuntu bionic, the build fails. These are the packages I'm installing https://github.com/0ad-matters/0ad-appimage/blob/trunk/Dockerfile

I'll see if I can get an AppImage for a dev build available within a few days. https://github.com/0ad-matters/0ad-appimage/pull/18

This is the first time I tried compiling with system mozjs. On Manjaro LInux, I've installed the js78 package. js78 --version reports 78.15.0 In the 0ad workspaces directory, I ran ./update-workspaces.sh --with-system-mozjs -j5 It completed: But when I ran make -C gcc -j5 I got a failure very quickly:

Could someone please confirm this bug so it doesn't get incorrectly closed again: https://trac.wildfiregames.com/ticket/6617#comment:3 cc @Freagarach@wowgetoffyourcellphone@Stan`

Also tried with an a26 self-build, which actually links to the SDL2 library installed on Manjaro. I still can't reproduce the issues mentioned above.