Also, idk how should I think about this issue, technically the game worked for 3 years (that's why #1372 is closed) and it looks like a regression from Proton's side, but there was no template for regressions and this one fit the best I guess...
@Soveu Thank you for the report! Have you tried Proton - Experimental yet? In my testing, experimental-9.0 does not hang, but I am seeing some input issue where there hitching in the background animation and characters that I typed are being skipped. I'm wondering if you are seeing the same thing or if you still see a hang on experimental.
I quickly checked the newest Experimental, the issue with menu has disappeared. I also did training in single-player and it looks ok.
I am experiencing a CTD anywhere from a second after launch to a few seconds after quickly pressing singleplayer > quick game against the computer.
Proton 5.0-10, 5.13-6, 6.3-8 works
Proton 7.0-6 & later crashes
I suspect there might be a regression in Wine but have not been able to find similar complaints elsewhere.
My system configuration is as follows (NVidia 2070, Ryzen 5 5600X):
Operating System: Arch Linux
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.6-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 2070/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd
Product Name: MS-7B86
System Version: 3.0
I do not see this on my laptop with an Intel CPU/iGPU, so it might be useful to know if anyone else is experiencing it.
I have moved to Solus after few years on Linux Mint and want to add few things so maybe someone wiser can figure out what is happening.
Few hardware/software info:
GPU: RX 570 8GB
RAM: 8GB
CPU: i5-3470
OS: Solus 4.7
DE: KDE Plasma 6.2 Wayland
Steam Flatpak (flathub)
Proton 9
Really the only difference that comes to mind is Wayland, but other games like Unity 3D engine work in full 165 fps just like before on Linux Mint and I have absolutely no idea where to start troubleshooting this problem since W:A is the only game I noticed having it.
@Qronikarz perhaps your video options changed from then to now. For me the game ran at 58 fps by default.
If you go to settings > advanced, then "wait for vertical sync" will likely be turned on, if you disable it the game should run as fast as it can on your hardware, if you enable "assisted vertical sync" then it should cap to your monitor's refresh rate (in my case, 180)
I reinstalled this game often on clean OS many times and it always resets settings to default and still worked at 165fps. Never had to change any settings. But I did try it now and it doesn't change anything. I may try to use Gamescope in the future, but it's a weird situation for sure.
EDIT:
Weird situation for sure, but was checking WA with Proton 10 for my language detection issue report and noticed that it now works the same way as on Mint. I reinstalled to game to make sure it resets to default options and the game works at 165fps without changing any options:
Same hardware of course, but the OS is after some updates: KDE Plasma 6.5, Linux 6.16
There is an issue with the game when using SuperFrontendHD mod. I don't know if posting issues with mods is allowed here, but this is a fairly popular mod so it would be nice if it could be resolved.
SuperFrontendHD is a mod that allows for rendering the game menu in higher definitions. If windowed mode is disabled in WA settings, everything works, but when enabling it, the game window keeps being rendered 640x480. Notably SuperFrontendHD still renders the menu at a high resolution but it's being crammed into the small window.
Fullscreen:
Windowed:
This does not happen on windows: there, the window is resized according to what resolution is set in SuperFrontendHD settings (which, by default, is resolution selected in WA settings).
I'm using KDE, so I've tried to force a different window size with window rules, but sadly the issue persists, the rest of the window is just filled with black:
Proton 10, KDE 6.5.4, Wayland.
proton experimentalx1 2024-03WINEFSYNCx1 2024-03WINEFSYNC_FUTEX2=0 %command%x1 2024-03
Compatibility Report
Worms ArmageddonSystem Information
6.7.9-200.fc39.x86_64I confirm:
steam-217200.log
Symptoms
Game hangs in menu when using Proton Experimental or 9.0 Beta, on version 8.0-5 works fine.
Reproduction
Launch the game and do something in the menu, like creating or modifying a team.
This doesn't sound very specific, but I wasn't able to find anything that triggers this consistently. The first time the game was launched, just as I changed the name of the first worm, the game hanged. The second time I created nearly the whole team. The third time I didn't even got to the team editing menu.
I also tried if it somehow isn't a futex2 issue, but
WINEFSYNC_FUTEX2=0 %command%doesn't fix it.