It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
Ragmand: I know this topic is 4 years old, but there's a similar problem now. I had this experience with libfmodex64.so.

libGLEW.so is included with the game, as is libfmodex64.so, the problem is that the startup script is badly written. In ~/GOG\ Games/Mount\ Blade\ Warband (or wherever you installed the game), you have to add the line export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:"`pwd`/game" between the #Action and run_game() { in start.sh.

$LD_LIBRARY_PATH is consulted at runtime by ld, the dynamic linker (finds all of your shared libraries (Linux equivalent to Windows' DLLs)). The game includes all of the necessary dynamic libraries, which is the good and correct thing to do, but the script left out this crucial step. I wouldn't expect a new Linux user, or even a semi-experienced one without programming experience, to know this or figure it out.
It said i was missing libGLEW.so.2.1, but thanks to you, it was solved.
Post edited July 08, 2022 by Grzegorz_Baltissen
avatar
Ragmand: I know this topic is 4 years old, but there's a similar problem now. I had this experience with libfmodex64.so.

libGLEW.so is included with the game, as is libfmodex64.so, the problem is that the startup script is badly written. In ~/GOG\ Games/Mount\ Blade\ Warband (or wherever you installed the game), you have to add the line export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:"`pwd`/game" between the #Action and run_game() { in start.sh.

$LD_LIBRARY_PATH is consulted at runtime by ld, the dynamic linker (finds all of your shared libraries (Linux equivalent to Windows' DLLs)). The game includes all of the necessary dynamic libraries, which is the good and correct thing to do, but the script left out this crucial step. I wouldn't expect a new Linux user, or even a semi-experienced one without programming experience, to know this or figure it out.
Hi!

The easiest way to solve that, is to change the "./mb_warband_linux" part in the GOG start.sh script, for '"/mb_warband.sh", which contains all the necessary trick to point to the rigt directory with the DLLs.

Also, I advise to edit mbw_config.sh to explicitly add a
cd "$PROGRAM_DIRECTORY"
before the line calling the "mbw_config_linux" binary. On my side, without this change, the configuration app was not able to see the Modules.

Hope it helps :)

-- Cuines
Post edited July 23, 2022 by cuines
avatar
Ragmand: I know this topic is 4 years old, but there's a similar problem now. I had this experience with libfmodex64.so.

libGLEW.so is included with the game, as is libfmodex64.so, the problem is that the startup script is badly written. In ~/GOG\ Games/Mount\ Blade\ Warband (or wherever you installed the game), you have to add the line export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:"`pwd`/game" between the #Action and run_game() { in start.sh.

$LD_LIBRARY_PATH is consulted at runtime by ld, the dynamic linker (finds all of your shared libraries (Linux equivalent to Windows' DLLs)). The game includes all of the necessary dynamic libraries, which is the good and correct thing to do, but the script left out this crucial step. I wouldn't expect a new Linux user, or even a semi-experienced one without programming experience, to know this or figure it out.
Thank you so much. This fixes all the issues! Runs on Ubuntu Jammy 22.04