Warstone TD (562500)

[liberodark]

Distro: Manjaro XFCE 17.1.12 GPU: GTX 1060, Nvidia proprietary driver 396.54 Resolution: 1920x1080 RAM: 8GB Proton 3.7-4 Beta

All is fine

[crabel]

Crashes for me with Radeon Vega 64 and Mesa 18.2.2 Attached are logfiles + a crash dump that is written by the game.

crash.dmp.txt error.log output_log.txt

[kisak-valve]

Hello @crabel, please copy your system information from steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Also, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box and note which version of Proton you are using.

For reference, the attached minidump is an EXCEPTION_ACCESS_VIOLATION_READ in warstone.exe.

[crabel]

Systeminfo: https://gist.github.com/crabel/2a1751eab50f30f35e2376bca3606597#file-gistfile1-txt

When I add PROTON_LOG to the start options, I just see the following line in the logfile and nothing else happens. The game hangs(?) completely and I have to kill it.

---

ERROR: ld.so: object '/home/odie/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

That's all I get.

Sidenote: I can start the game using wine 4.0 RC4 directly. (wine warstone.exe). So, whatever the issue is, it isn't strictly an AMD/Mesa issue.

[crabel]

Oh, my bad. There was still a hanging instance of warstone from a previous run. I have attached a logfile now. AND I got it working using the following launch option:

"PROTON_NO_D3D11=1 %command%"

steam-562500.log

[kisak-valve]

err:vulkan:wine_vk_instance_load_physical_devices Failed to enumerate physical devices, res=-3 and err:vulkan:wine_vkCreateInstance Failed to load physical devices, res=-3 in your log along with your workaround hints that you don't have a sane vulkan driver.

Can you confirm you have mesa-vulkan-drivers:i386 with something like apt policy mesa-vulkan-drivers:i386?

[crabel]

Hmm. Now I am confused.

apt policy mesa-vulkan-drivers:i386 mesa-vulkan-drivers:i386: Installiert: (keine) Installationskandidat: 18.2.2-0ubuntu1 ...

sudo apt-get install mesa-vulkan-drivers Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig mesa-vulkan-drivers ist schon die neueste Version (18.2.2-0ubuntu1).

Sorry for the German, but policy says "Installed: (none)" but install says "already the newest version 18.2.2-0ubuntu1)".

[kisak-valve]

mesa-vulkan-drivers is 64 bit and mesa-vulkan-drivers:i386 is 32 bit. The game is most likely 32 bit.

[crabel]

Did a "dpkg --configure -a", apt-get install -f, apt-get update --fix-missing now and now it shows the driver as installed.

apt policy mesa-vulkan-drivers mesa-vulkan-drivers: Installiert: 18.2.2-0ubuntu1 Installationskandidat: 18.2.2-0ubuntu1

But nothing changed. The logfile still shows these lines: err:vulkan:wine_vk_instance_load_physical_devices Failed to enumerate physical devices, res=-3 err:vulkan:wine_vkCreateInstance Failed to load physical devices, res=-3

[crabel]

Ah! Of course. sudo apt install mesa-vulkan-drivers:i386 did the trick! Thanks alot, game works now. Note/Idea: Maybe some kind of testtool would be helpful to detect things like that? That's probably not an uncommon issue ...

[crabel]

Another issue: The game sometimes stops working/gets unresponsive. Enemies are not attacked anymore and simply run to the end of the level and get stuck there.

The issue seems to be related to the "game server". The game starts an internal server to handle the game mechanics and in some levels it simply crashes(? or at least becomes unavailable) always. There is a workaround though: Deleting the file "socket.dll" in the warstone_Data folder forces the game to connect to a fallback server provided by the developer.

[at46]

As a friend of mine suggested, you can also use WINEDLLOVERRIDES="socket.dll=d" %command% as launch option instead of deleting the socket.dll file.