hyperion

On Ubuntu you likely use Gnome, then the window manager should be mutter, session type is either X11 or Wayland and sdl version you can get by running "apt show libsdl2" in terminal. I remembered a mutter bug wrt confinement region https://gitlab.gnome.org/GNOME/mutter/-/issues/2740 which is still open, so yes this might be the reason.

What window manager do you use? What session type? What distro? And what version of sdl? I can only say works for me.

Thanks, Going by the video the issue is likely the simulation freezing due to a player not sending his turn end signal within a reasonable amount of time, which is different than the game freezing. For the player causing the issue this might indeed look like a game freeze tho. That would also match @Gurken Khan report which I first thought to be unrelated but actually might be the same. Given that in one video there are still sporadic simulation updates happening it's not a hang but something taking much more time then it should. So of most interest right now are logs / OS / hardware from players causing the issue. Looking at the mainlog of @erictommy there are a few mods which are unlikely to cause the issue but at least in theory could, so keeping an eye on what mods are enabled wont hurt at least. That mainlog also contains warnings for compiling glsl shaders. That is reasonably suspicious as it also happens early in the game. Maybe a problematic GL driver might be the root cause. That could also explain why 0.27.x as there where major changes there to support Vulkan. Players causing the issue might want to try switching to Vulkan if possible to see if it helps. Trying to update the driver is certainly a good idea as well. I'm not yet able to reproduce it so more hints are welcome.

Is it never observers causing this? Does who is hosting matter? What OS are the players on that trigger the issue? Is there a video that could be shared to have a better impression of what the issue looks like for involved players? What versions does this happen with, 0.27.0 and 0.27.1?

Hi everyone, for the 0.28.0 release the plan is to make 0ad available as an AppImage together with the Windows installer and the macOS bundle. That means easier access to a binary for users uncomfortable building 0ad from source when they can't wait for their distribution to update the package. This also means AppImages will be added to the bi-weekly builds used for testing when the support matures a bit. By now you probably already thinking give me the link already, so here the link to where the latest test build is available from: https://jenkins.wildfiregames.com/job/test-appimage/ How to run the AppImage you ask? First you need to install fuse which allows for filesystems in userspace. Maybe the package is called libfuse for you distribution. You will need fuse version 2.x for AppImages. Next download the artifacts and verify the downloads which can be done for example as follows: $ md5sum -c 0ad-0.28.0dev.AppImage.md5sum 0ad-0.28.0dev.AppImage: OK $ sha1sum -c 0ad-0.28.0dev.AppImage.sha1sum 0ad-0.28.0dev.AppImage: OK $ minisign -V -m 0ad-0.28.0dev.AppImage -P RWTWLbO12+ig3lUExIor3xd6DdZaYFEozn8Bu8nIzY3ImuRYQszIQyyy Signature and comment signature verified Trusted comment: timestamp:1752172582 file:0ad-0.28.0dev.AppImage hashed Then make the AppImage executable $ chmod +x 0ad-0.28.0dev.AppImage Then launch 0ad $ ./0ad-0.28.0dev.AppImage Finally report if it works for you or not and what distro you are using. A note here, the basis for the AppImage is Debian 12, oldstable by the time of the 0.28.0 release. If your distribution is substantially older than that it might not work.

No amount of toolkit switching would have helped here, the crash has nothing to do with wx but is a bug in pyrogenesis. Change your gtk theme if you don't like your current one? wx uses native widgets on Windows, how are you gone beat that wrt integration? It's already developed and the maintenance cost for the last 20 years was exceedingly low, you could say qt was rewritten from scratch more then once in the same time frame. Edit: seems wxqt isn't fully dead https://wiki.wxwidgets.org/WxQt

Because you don't like gtk which is used on Linux for wx?

Atlas uses xw toolkit which doesn't support vulkan yet so it's using opengl no matter what you have in your settings. That said this is likely fixed in the 0.27.1 release candidate. Probably a variant of https://gitea.wildfiregames.com/0ad/0ad/issues/7620

@little Guest, suggest to try the 0.27.1 release candidate as it contains some vulkan fixes and is fully compatible with 0.27.0.

There are multiple drivers for amd gpus, this might be a mismatch of components. Suggest to use mesas amdgpu driver with radv. Check your distros documentation, especially keep an eye on selecting icd.

@Itms, congrats on rc1! Packaged for my distro and all went well, the only thing that might need a note is if using system premake5 then it needs to be < beta4 because of the api break.

They are aware: https://bugzilla.redhat.com/show_bug.cgi?id=2345520

The package manager knows which files belong to a package, there surely is a command to list them, check what wx-config-* wxwidgets-gtk3 installed.

it means wx-config-gtk3 no longer exists on your system or is no longer in PATH. You can use an absolute path for WX_CONFIG, but it must point to the wx-config corresponding to your desired wx install.

Lobby games are also just lan games in essence, the only difference is that the needed address gets passed to others via a neat ui. The lobby also adds some mechanisms to allow some additional network setups to work, like firewall puching / stun. As a bonus you get a chat and a ranking bot. I'm pretty sure you don't want to setup your own lobby but you could, the code and instructions is at https://github.com/0ad/lobby-infrastructure If you create a lan game it means 0ad on your computer will listen on the specified port for connections. Everyone around the globe that can connect to you computer will be able to join that game. How to make your computer reachable from the internet typically means adding portforwarding to your router and configuring the firewall. But even then, due to IP4 starvation your ISP might make it virtually impossible to get it working.