It's working fine on Ubuntu 14.04.

Let's try to find out missing libraries:

ldd .steam/steam/steamapps/common/Pixel\ Piracy/linux.x86 | grep not

This command will tell you about missing libraries (if any)

WARNING: Your path to steam games may vary.

P.S. What drivers are you running? Open Source / Propietary?

Hi RTheren,

Thanks for the reply.

I tried running:
ldd .media/user/500GB_SSD/Steam/steamapps/common/Pixel\ Piracy/linux.x86 | grep not
with the result path not found and assumed it should be:
ldd /media/user/500GB_SSD/Steam/steamapps/common/Pixel\ Piracy/linux.x86 | grep not
with nothing returned.
I also tried directly from within the folder with nothing returned, so I guess no libraries are missing?

I am running proprietary drivers CCC states version is 15.20... which I believe is 15.7 (not latest version I know but I have had no issues in other games so never updated)

Thanks again.

OK. Run the game from terminal and post here output from it.
When it crashes, type dmesg to see if something else fails

Running the game, Terminal output:

Quoteuser@Horse /media/user/500GB_SSD/Steam/steamapps/common/Pixel Piracy $ ./linux.x86
Set current directory to /media/user/500GB_SSD/Steam/steamapps/common/Pixel Piracy
Found path: /media/user/500GB_SSD/Steam/steamapps/common/Pixel Piracy/linux.x86
Mono path[0] = '/media/user/500GB_SSD/Steam/steamapps/common/Pixel Piracy/linux_Data/Managed'
Mono path[1] = '/media/user/500GB_SSD/Steam/steamapps/common/Pixel Piracy/linux_Data/Mono'
Mono config path = '/media/user/500GB_SSD/Steam/steamapps/common/Pixel Piracy/linux_Data/Mono/etc'
Aborted
user@Horse /media/user/500GB_SSD/Steam/steamapps/common/Pixel Piracy $

Most of this is displayed before accepting the configuration, the only part that is displayed after launching the game is the part that just says "Aborted".

I'm not sure what I should see from typing dmesg but there is a lot printed out to the terminal, so much I can no longer see the previous commands. Is there anything in particular to look for? As I think there is too much to paste here.

Thanks again.

Try to look for something like segmentation fault.

Also try to move the existing game to other directory and download it again. If it won't work even after this, it's probably drivers

Hi,

I reinstalled the game to the default steam location in the home folder, with the same result.

dmesg shows that ptrace of pid... was attempted by gdb when the output has reported as aborted.
dmesg also has entries that appear to be ethernet related and are of the form [UFW BLOCK] IN=eth0 OUT MAC=... but I am not sure this is related to the game.

However after the numerous times of trying to run the program the message is not always "aborted". I have also had Segmentation Fault and corrupt double linked list, both result with nothing added to dmesg.

One run resulted with this appearing in terminal:

Quote*** Error in `./linux.x86': corrupted double-linked list: 0xe1500568 ***
Aborted

with dmesg having the following added:

Quote[ 303.588145] EXT4-fs (sda1): error count: 21
[ 303.588168] EXT4-fs (sda1): initial error at 1448755648: __ext4_read_dirblock:1922: inode 798443
[ 303.588172] EXT4-fs (sda1): last error at 1455567255: __ext4_read_dirblock:1922: inode 798443

However after receiving this error message a second time there was nothing added to dmesg other than UFW BLOCK.

I am not sure it's driver related as someone on the thread I raised on quadrodelta states they have the same issue but they are using the Nouveau driver.

Thanks.

You can safely ignore the eth0 related stuff.

What catched my eye was

Quote[ 303.588145] EXT4-fs (sda1): error count: 21
[ 303.588168] EXT4-fs (sda1): initial error at 1448755648: __ext4_read_dirblock:1922: inode 798443
[ 303.588172] EXT4-fs (sda1): last error at 1455567255: __ext4_read_dirblock:1922: inode 798443

It may be caused by corrupted sectors on disk.
Try to run fsck from Live-CD/USB, or check with other programs if there are corrupted sectors on HDD

Otherwise it may be driver related, since it's Unity game.
Give FSCK a go and let us know the result

I ran fsck and fixed the issues that came up, a second run resulted in no issues found. Once I rebooted back into the installed OS I ran the game again with absolutely no change, the same sort of error messages came up varying with every run.

Just a curiosity.

Have you tried the open-source AMD drivers?

Not with this game, yet. I had tried out the opensource drivers a while ago, maybe a year ago and had graphical issues with other games so I went back to proprietary ones. I will give them a go when I have time and report back.