Resolved Warband launch option is misconfigured on linux

[xrogaan]

After a recent steam update, warband will no longer launch (while the configurator will work fine). The issue lies with how to game has been set up, as it's calling the binary (mb_warband_linux) directly instead of the bash script (mb_linux.sh). This has for effect that the binary is unable to find a library:

MountBlade Warband/mb_warband_linux: error while loading shared libraries: libfmodex64.so: cannot open shared object file: No such file or directory

This issue is partially being discussed on the steam runtime bug tracker: https://github.com/ValveSoftware/steam-runtime/issues/301

Discussed in the linked thread, the script mb_linux.sh also has one major issue. Mainly it overrides the LD_LIBRARY_PATH variable instead of appending to it.

 

[MArdA TaleWorlds]

Forwarded to the developers. Thanks for reporting!

 

[xrogaan]

The linked issue has been updated (last month, sorry for the delay) to indicate that the issue should be resolved on valve's side.

The changes in the beta client described in #317 should be fixing this for games run without the SteamLinuxRuntime (but only those games, right now).
Resolving https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/issues/46 and updating to a newer Steam client (not yet released) will fix this for games run with the SteamLinuxRuntime.