Linux troubleshooting thread

[ai_enabled]

Hello!

Currently VoidExpanse should work fine on Ubuntu, Fedora and SteamOS.

However there are some known issues:
1. visual glitches and artifacts (especially on AMD and Intel GPUs);
2. random crashes;
3. cannot launch the game (especially on old GPUs).

If you have any of these issues, please add this launch option to the game:

-force-gfx-direct

(right click on the game in Steam Client, select Properties, click on button "Set launch options" and paste it there)

If this not helps, please try adding this option as well:

-force-opengl

It will force the Unity engine to use old OpenGL2 renderer (which is in some cases more reliable).

If you still have the issues, please upload your Player.log file from the folder "~/.config/unity3d/AtomicTorchStudio/VoidExpanse/" at http://pastebin.com/ and share the link.

Regards!

[Artanicus]

Didn't help and a gtx 970 isn't really all that old.

Player.log:
http://pastebin.com/ygGcBAEr

Do you want strace output?

[Artanicus]

And just to clarify, this is on Ubuntu 16.04, Nvidia GTX 970 and everything worked fine for me with no tweaking before the latest update and now no number of tweaks makes it work.

[ai_enabled]

Artanicus, thanks for reporting! It seems the problem is not related to the game settings. Could you delete this settings file please? "~/.config/AtomicTorchStudio/VoidExpanse/SettingsClient.xml". The game will start with the fresh new settings file and the issue might be resolved.

Also please remove any tweaks (launch arguments) you've added.

Regards!

[Artanicus]

Actually I was a bit hasty in my testing. I was using the binary directly with the flags and neither VoidExpanse.x86 or VoidExpanse.x86_64 work but running via Steam with just -force-gfx-direct is enough to get the game started again. But as mentioned, didn't need any workaround before the update.

[ai_enabled]

Artanicus, unfortunately with Unity Engine we cannot cover all the Linux players and be sure the game will run fine for everybody - every version they change something, fix it for some Linux players, but usually broke it for many other. That's why we avoid Unity Engine for our upcoming big games and write our custom engine.

With latest version we've switched on new OpenGL renderer version (OpenGL Core) and compatibility has been improved for most players. This launch argument will restore the previous OpenGL renderer (2.1):

-force-opengl

But again, we cannot be sure about anything with Unity Engine on Linux...

Regards!

[noobsBelow]

Just bought the game and I am unable to launch the game on Ubuntu 16.04. I have tried everything in this thread and from google. I do not have Player.log file for this game on my system. I do have it for other games. Here is the output from trying to run from the terminal. http://pastebin.com/a03PPzEp

[flesk]

^ Did you try to run it with the -force-opengl option that was mentioned in the first post? You don't say anything about your specs, but if you're on Intel graphics with the Mesa driver, most Unity 5 games will crash after the Unity launcher without that option.

EDIT: Just noticed that you said you tried everything from this thread, but in your paste, none of those options are set.

[noobsBelow]

Yeah I tried the -force-opengl via terminal and steam.

Intel i5-2500k
16GB Memory
Nvidia GTX 960

[flesk]

Do you get the exact same output to terminal when run with that option? I.e.:

./VoidExpanse.x86_64 -force-opengl

[ai_enabled]

noobsBelow, could you run the game with the "-logFile out.txt" launch argument and upload the "out.txt" file please?

[noobsBelow]

flesk - Yes same output.

ai_enabled - http://pastebin.com/Grc9Ewd9
Not sure what "Player is already running" means in the log. I do have a dedicated server running.

[ai_enabled]

noobsBelow, is that all the content of the out.txt file? That's quite strange, usually it contains much more info.

Regarding the "player is already running" I've found a few topics for Pillars of Eternity (also Unity-based game):
https://www.gog.com/forum/pillars_of_eternity/player_already_running
https://forums.obsidian.net/topic/73867-starting-game-while-chrome-running/
It seems closing Chrome process resolves the issue. Could you try it please?
Also the game process might be keep running in the background (zombie process), you could kill it with System Monitor.

Regards!

[noobsBelow]

Thanks this helped a lot. I closed chrome but it didn't seem to help. I think chrome was still running in the background. With the links you provided it said something about strace.

So after some googling I ran this:
strace ./VoidExpanse.x86_64 | grep "open(\"/proc/)"
This command outputs a bunch of these lines with different PID numbers:
open("/proc/3833/cmdline", O_RDONLY) = 5
open("/proc/3887/cmdline", O_RDONLY) = 5

I then opened System Monitor and killed the last PID it found (3887). It was some process with a long name. Problem solved.