Talk:PULSAR: Lost Colony
Contents
Troubleshooting
log file locations in general
Location 1: Player log showing errors and game crash log location
~/.config/unity3d/Leafy Games, LLC/PULSAR_LostColony/
Files appear as Player.log and Player-crash.log or similar
Location 2: Unity analytics
~/.config/unity3d/Leafy Games, LLC/PULSAR_LostColony/Unity/ xxxxx
Location 3: player voice communication / Team Speak
~/.local/share/Steam/steamapps/common/PULSARLostColony/logs/
VOX Audio Player Communication Failure
You have game sounds such as the environment, ship, gun fire, etc however you can not hear the other players when they speak.
The game uses a built in Teamspeak (ts3).
Sound device attachments:
lsof | grep snd
for Pulsar
lsof | grep PULSAR
Location of ts3 Team Speak log
ls ~/.local/share/Steam/steamapps/common/PULSARLostColony/logs/
These logs are separate from the game binary log files and only relate to the voice communication component of the game. They are generated by the Team Speak engine. They are very useful in troubleshooting.
If you see audio devices appear as red in the game audio settings try testing from console
aplay -Dtee:\'plughw:0,0\',/tmp/alsatee.out,raw /usr/share/sounds/alsa/Front_Center.wav
SteamOS Pulsar looking for libsndfile.so.1.0.28 under newroot
You have enabled "compatibility mode" for Pulsar Lost Colony in the Steam Launcher. Right click on the launcher and uncheck "compatibility mode".
SteamOS uses switch_root in compatibility mode, which is useful if you manually wish to configure paths to devices or drivers.
Unity Mono General Crappyness
From Unity 4, Linux is supported target platform for Unity games. Since Unity is based on Mono, only appropriate Linux executable needed. For older Unity 5+ games before Metal, porting from Mac version can alleviate the problems with pink shaders, since instead of DirectX/Direct3D HLSL shaders common OpenGL GLSL shaders were used. OpenGL, OpenGLES or Vulkan rendering is mostly functional.
