I got the game for free as Wintersale Give Away. Thank you GOG!
So this is in now way a complaint!


The first problem I ran into was already mentioned earlier hier in the forums.
The game doesn't work well with my dual-monitor setup, at least in fullscreen mode.
- I disabled a monitor,
- configured the game to not run in fullscreen,
- gave it a reasonable resolution (my monitor's native),
- and re-enabled the sceond monitor.
Problem 1 solved.

Intro works, menu works, creating a squad works, ...

But when the loading progress bar is at about 80% the game either crashes or hangs.
(Seems to depend on settings, but I'm not sure about it. Lately it always hangs for me.)
After some looking and testing I learned, that the game opens more files than linux (shell) usually allows.
My workaround (command-line): Before starting the game (`start.sh`) I raise the resource limits for that shell by `ulimit -n 4096`. (In the first gameplay minutes I observed around 2000 open file handles, I just guess 4096 should be enough for later gameplay.)
Problem 2 solved. So to say.

The second problem was a little tricky, so I hope the workaround might help someone.
Similar symptoms were already mentioned occasionally since 2016 in game comments. I'm curious if it is still the same cause.

More technical stuff (maybe someone know to read them better):
- Most open file handles are for just 1-2 asset files (i.e. `sharedassets5.resource`)
- Intro uses about a dozen file handles (f.j.1-2 a.f.)
- Main menu uses about 200 file handles (f.j.1-2 a.f.)
- Early gameplay it is about 1900 handles (f.j.1-2 a.f.)
- When the game hangs, `~/.config/unity3d/.../Player.log` continuously grows by errors about file `unity default resources` not being able to be opened (for reading)
- When the game hangs, its process constantly checks if that file exists (`stat` and `access` syscalls)
- When the game hangs, I do not observe any `open` syscalls from the process

That was exactly what I've been searching for, you solved my problem with one post :) Thank you very much, it worked perfectly on my Ubuntu 19.10 :)

Edit: I added the line to start.sh and it also works that way.

I had problem with game crashing (exiting to desktop) after creating squad and pressing play in Linux Mint 19.2.
I added the line "ulimit -n 4096" (without quotes) into start.sh and now the game starts. It works!

I was about to contact GOG about the issue, but you, buddy, saved everyone some time with the simple solution. My thanks!

I had crashes as well when tried to run W2DC from Application menu.
Solved problem by starting game from Terminal.

P. S. There was no such problems with W2.

"ulimit -n 4096" helped me with first crash at new game start after party creation but apparently in my case game still crashes randomly on loading screens after some time in-game. Terminal output says "Segmentation fault (core dumped)".

I think I'll have to give up on this sadly.

I am running Mint 19.1 (Tessa) and whenever I try to save or quicksave I cannot use the esc key, move, or interact with anything other than what is displayed on the screen. Any ideas how to resolve this?

Also, I had the problem of crashing at startup until I changed the settings under permissions to Read and Write for all. I never tried the 'ulimit -n 4096' because I didn't know where to put it in the start.sh file.

I have problem 1 as well, that is two monitors and the game FUBARs it with a game shown moved to the right, but actually clickable areas are at their actual positon. Has anybody an idea how to tell the game via the start.sh script or otherwise to put the game graphics scentred on one screen without jumping through hoops like disabling a monitor for some time?


Other unity games run without a problem right out of the gate on one of two monitors.

Probably I've got once same buggy behavior when was trying to set up graphic settings (don't remember exactly, probably I was trying to run not Fullscreen with FullHD resolution at main 4K monitor). Only Reset in Display options helps me.

Well, when I navigate to the display options by clicking a step to the left of what I can see I was able to switch to windowed mode. Great. now I have an ugly window head at the top and I can see my taskbar. Is there no borderless windowed mode? After the rather long loading time the squad is standing around and cannot talk to Vargas, because it is empty on screen. No text in the dialog box.

what a mess.

Well okay, I started Wasteland 2 now from the console, because the ulimit is slightly higher there at 524288. Works now. I really should edit the start.sh file to automatically raise the limit. Still no borderless windowed mode. :-(

Kind of sad how none of this is included in the basic shell file.

edit : Actually, even after doing all this, after one reboot, the game won't even launch.

Ok I will ask the question that no one else seems to have asked...... where exactly in the sh file should I add ulimit? The bottom?

EDIT: nvm this game is a waste of time on linux, even running ulimit and then sh through terminal I get a bug where I cannot even click on the calibration buttons.

Running the widows version through wine kinda works but there are colour issues and some buttons either not working or completely dissapearing.

If the devs are gonna make this much of a f-up it's best they don't even bother.... it's insulting to be offered this kind of scraps.

As suggested above, increasing ulimit fixed my crash issues. I just played a new game for an hour with no problems.

I'm using Ubuntu 20.04 LTS on a desktop running a Ryzen 3200 and a Radeon 580 with 16GB RAM.

Here's a more detailed fix description for Ubuntu 20.04 (other distributions and versions vary slightly):

1) Navigate to ~/GOG Games/Wasteland 2 Directors Cut
>> Click the folder icon in the upper left to open your file browser.
>> Click the Home shortcut in the upper left
>> Double click these folders: GOG Games > Wasteland 2 Directors Cut

2) Backup start.sh
>> Right click on start.sh, select Copy to..., click Select in the upper right

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

4) Launch the game normally, or launch start.sh from the terminal (some people report using terminal is better, and I've had to launch some apps on 20.04 from terminal to get them to start working properly).

Thanks for the explicit instructions. They worked for me on Linux Mint 20.

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}