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
Ardemus: 1) Navigate to ~/GOG Games/Wasteland 2 Directors Cut

<snip>

3) Add "ulimit -n 4096" to start.sh
Thanks! I migrated my save games to a new laptop a while ago, then forgot about it. After a several month hiatus, I was trying to figure out why the game kept glitching whenever I saved.

Zero chance of me remembering this fix from when I first installed W2:DC on my older laptop several years back. Can confirm though, that 2/2 installs of W2:DC require this fix.
avatar
Ardemus: 3) Add "ulimit -n 4096" to start.sh
>> Right click on start.sh and choose to open with Text Editor or whatever editor you prefer
>> Paste "ulimit -n 4096" (no quotes) on a new line to the initialization section of start.sh
>> Save and close the file
Thank you so much friend !!! Now I can play! [wl2dc] Kubuntu 14.04 esm

ps
However, earlier, for Wasteland 2 in Steam (not DC), I did not do anything. Everything was played without any magic. :)

THX!
avatar
Perturabo.235: When trying to play Wasteland 2 Director's Cut on Linux Mint 19 it crashes when loading and I get the following error in terminal:
support/gog_com.shlib: line 94: 3079 Aborted (core dumped) ./"${bin_64}
Got the same. Any known fixes?
Doesn't seem to have anything to do with the ulimit noted.

player log has the following stacktrace:

terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct NULL not valid
Stacktrace:


Native stacktrace:

/home/birkirb/GOG Games/Wasteland 2/game/WL2_Data/Mono/x86/libmono.so(+0x8b5ac) [0xf72c05ac]
linux-gate.so.1(__kernel_rt_sigreturn+0) [0xf7f06570]
./WL2() [0x8fdb685]
./WL2() [0x8fdb6c2]
./WL2() [0x8fdaf01]
./WL2(_ZSt19__throw_logic_errorPKc+0x68) [0x8f8d548]
./WL2() [0x8965571]
./WL2() [0x895bfef]
./WL2() [0x827ba2d]
./WL2() [0x891ed08]
/lib/i386-linux-gnu/libc.so.6(+0x21519) [0xf794d519]

Debug info from gdb:

I refuse to debug myself!
No threads.

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
dfgth
Post edited January 22, 2024 by AHD73