Some research into Unity or Steamworks issues with the alsa-lib crash in your log comes up with a number of things. It appears it could be a graphics driver issue. Can you please try a few different versions of the mesa graphics drivers? http://www.mesa3d.org/

Hi N3ph,

Can you provide a description of what happens visually? Does the game load then instantly crash or does it sit there doing nothing forever?

Can you please make sure your graphics drivers are up to date, and consider looking at some of the steps here to help Steam launch properly: https://wiki.archlinux.org/index.php/Steam

That's great news! Steam must not have properly downloaded the hotfix the first time. Hopefully this experience wasn't too painful for you, and thanks for helping us resolve it.

As an FYI - When v1.4 comes out, you will automatically be pushed off of the beta channel and into the default channel where Steam will automatically download and update your game. So no further action is required by you.

Hey Marten,

Would you mind uploading the log after trying to launch the beta game again? Seems the one above is cut off and doesn't have the entire log text in it.

That is odd. It is launching on our test Linux machines. Could you please try the following:

1. Perform a game data scan to ensure you've got all the update files. In Steam for the game, go to its Properties -> Local Files and then click on Verify Integrity of Game Cache.

2. In the game directory browse to the WFTOGame_Data directory and open the Settings.ini file for editing. Find and change the following properties like so:

Width=1920
Height=1080
Fullscreen=False

Try launching the game. If it succeeds, proceed to change the settings as you wish in the game settings menu.

If this fails, perform step 2 again. But unplug one of your monitors and tell us what happens.

Thanks for your patience so far Marten.

Hey Marten,

I have made a special build of the game for you that hopefully fixes part or all of your issue. You can access this build by opting into our beta branch as instructed below.

Right click the game in Steam and go to Properties. In the Betas tab, type in the password 'publicpassword' and hit Check Code. Select the 'publictestbranch' in the dropdown box above and then close the window. Steam should perform an update.

Hi Marten,

Just today I managed to find and resolve a couple of bugs relating to setting the correct monitor and resolution. We had not intended to push a patch until v1.4 in a months' time, but I'll see about pushing out a hotfix for you tomorrow. No body likes a buggy game! ;)

Hi Nathan,

I just wanted to let you know that we're still investigating the issue and that you should not feel you need to stay out of the game - There is no risk to your steam account getting locked or banned by this issue.

Thanks for reporting the problem and please enjoy the game. :)

Well this at least confirms that the issue isn't with our code nor is it with Icey's graphics drivers or GPU - It never gets that far into initialization.

Icey - Do you have any kind of anti-virus or security software installed at all? If so, could you try disabling it temporarily and trying to play the game?