I've rolled back the default branch to v2.0.4 for now as we're not quite sure how wide spread this is. The issue didn't show up on our tests but we want don't want to leave a potentially faulty build out by default. So you should be able to opt back into the Default branch and get 2.0.4 now. If you still want to try v2.0.5 it is now on a Linux Beta branch.

Sorry once again we'll take a deeper look tomorrow.

Hi Folks,

Sorry to hear you're having this problem. We've had a few reports come in regarding this now and it seems something has gone wrong with the build on Linux.

Thanks for submitting the report here, we will be investigating first thing in the morning.

In the meantime please could you confirm that you have the additional requirements listed under the Linux section in System Requirements. The issue seems very similar to an issue we had previously where a key dependency for our UI Middleware was missing, as this has been updated in this patch this might be an explanation.

Once you've confirmed whether looking into any of those has an affect for you and if you're still not able to get into the game then I've move v2.0.4 onto the Previous Build Branch on Steam so you can opt into that in the meantime and play the previous version until we can investigate further.

Deeply sorry for the inconvenience.

Lee

Hi Cat Cheshire,

Thanks for submitting your report here. It seems this is an issue that is affecting other Linux users. I will be merging your ticket with another ticket to put everything in one place.

Once we're back in the office tomorrow morning we'll investigate.

Sorry for the inconvenience!

We have managed to successfully replicate this issue internally and resolved it for our test case. We are confident that this issue will be resolved with the v2.0.5 release early next week.

I'm sorry that it has taken us so long to address this issue and that it was previously marked as complete (the investigation was still ongoing). It was a extremely peculiar issue that affected specifically the installer versions of the game under very, very particular circumstances and until more information came forward we were not able to identify what could possible be the cause.

My apologies once again and I hope that the release of 2.0.5 next week will finally fix this for you and those affected. If you have successfully redeemed a refund on we would love to gift you copy for testing purposes by way of apology once the update is deployed.