Sunless Skies: Bug Reports

 

Hello! If you’re reading this, you’ve probably found a bug and want to report it to us. Before you do, please take a moment to scan our Known Issues page so you don’t waste time reporting an already known bug. If you can’t see your bug listed there, please see below for how to report your issue to skies@failbettergames.com.

When submitting a bug, the more information we have, the better! Every email will be looked at, but we’re a small team and very busy with reports since we launched on 31st January. Please be patient with us, and forgive us if you don’t receive a personalised response.

Contents

Core Information
Graphical Issues
Text Issues
Output Logs
Crash Logs
Save Files
Troubleshooting: Common issues

Core information

Current build: 1.2.1.2.b0df8add

One bug per report please!

  • Clearly summarise the bug in one or two sentences. Explain where you were in game and what you were doing when you experienced the issue. Please give reproduction steps if possible.
  • The build you are using (visible on the title screen)
  • Platform and tech specs:
    • OS (Windows, MacOS, Linux)
      • Version (XP, Windows 10, El Capitan, Sierra, Ubuntu, Mint, etc.)
      • 64/32bit
    • RAM
    • CPU
    • GPU
  • Troubleshooting steps you’ve already undertaken
  • Relevant attachments (screenshots/video for text and graphical issues, and output logs, crash logs and save files where applicable – please note that our ticketing system has a 7MB file size limit, so please compress large files such as video clips or zip them up)

 

Below is an example report for an old issue in Sunless Skies.

Bug: The Hold interface does not update automatically after jettisoning cargo

  1. Open the Hold interface
  2. Click on the jettison icon and jettison an item – the jettison interface will update automatically with the correct number of items but the Hold interface does not

Build: 1.2.1.2.b0df8add

Specs: Windows 10, 64bit, 16.0GB RAM, i7-4770 CPU @ 3.40Ghz, AMD Radeon R9 200 series

Troubleshooting: Closing and reopening the Hold interface resolves the issue

Back to top

Graphical Issues

Please include a screenshot where possible. Videos can also be helpful but our ticketing system has a 7MB file size limit, so please compress video files or zip them up. Please also tell us the resolution you are running the game at (to view this from the Title Screen go to Options > Graphics).

Back to top

Text Issues

If you find typos or grammatical errors, please include a screenshot as this often helps us locate the issue in our CMS.

No need to check the Known Issues list for typos as we do not list them. In a break from our one bug per report policy, it can help if you group typos by the areas they are encountered in where you can. So rather than one typo per email or even a list of 50 typos across the entire game, the best thing to do is send all typos found at Magdalene’s, for example, in one email. This makes it much easier for our writing team to deal with.

Back to top

Output Logs

Often, to track down a bug, we need to take a look at your output log. Here’s how to find it on your operating system. Please note: the log file is replaced each time you run the game, so it’s important to submit the file immediately after the session in which you experience the bug.

N.B. As part of the Reach Redesign build we upgraded our Unity version and this has resulted in the output log being generated in a different location on Windows. This is not something we can revert at the moment without significant work, so we have updated the location below. Ensure you are sending the correct output log based on the version of the game you are running.

Windows – after Reach build (v1.1.5.3.aa85c96 – 10th Oct 2018)

STEAM/GOG: C:\Users\[USERNAME]\AppData\LocalLow\Failbetter Games\Sunless Skies\output_log.txt

Windows – prior to Reach build

STEAM: C:\Program Files (x86)\Steam\steamapps\common\Sunless Skies\Sunless Skies_Data\output_log.txt

GOG GALAXY: C:\Program Files (x86)\GOG Galaxy\Games\Sunless Skies\Sunless Skies_Data\output_log.txt

OS X

~/Library/Logs/Unity/Player.log

Linux

~/.config/unity3d/Failbetter Games/Sunless Skies/Player.log

Back to top

Crash Logs

If you experience a crash then crash files are auto-generated and should appear in the install directory (the name of the folder will be the date on which the crash occurred). This is usually found in the following location:

Windows

C:\Program Files (x86)\Steam\SteamApps\common\Sunless Skies (if you’re using Steam)

C:\Program Files (x86)\Sunless Skies (if you are not)

C:\Program Files (x86)\GOG Galaxy\Games\Sunless Skies (if you’re using GOG Galaxy)

OS X

~/Library/Application Support/Steam/steamapps/common/Sunless Skies (if you’re using Steam)

Linux

~/.local/share/Steam/steamapps/common/Sunless Skies (if you’re using Steam)

Back to top

Save Files

Intermittent errors that occur regularly in a particular save game can be difficult for us to identify, so occasionally we may ask you to provide us with your save files. These files, listed below, can be found in one of the Lineage folders in the characterrepository directory.

  • autosave_m.json
  • autosave_s.json
  • saveSnippet.json

The characterrepository directory can be found in the following locations depending on your operating system:

Windows

C:\Users\[USERNAME]\AppData\LocalLow\Failbetter Games\Sunless Skies\storage\characterrepository

OS X

~/Library/Application Support/unity.Failbetter Games.Sunless Skies/storage/characterrepository

Linux

~/.config/unity3d/Failbetter Games/Sunless Skies/storage/characterrepository

Back to top

Troubleshooting: Common Issues

 

 

Black Screen Issues

So far we have seen seven causes of black screens on some machines when trying to launch the game and steps to resolve these issues are given below. If your output log contains a different error to the seven listed below then please send it to us at skies@failbettergames.com along with your save files.

  • If you experience a black screen (or crash) at the point of character creation (when first docking at New Winchester after going through the Opening Game Experience) and see d3d11 errors and/or a ‘Symbol-SearchPath’ crash in your log, then please see our troubleshooting steps here
  • If you see an exception that begins NullReferenceException: Object reference not set to an instance of an object
    at Skyless.Assets.Code.Skyless.Game.Data.CharacterRepository.ReturnAllSnippets () [0x00000] in :0
    at Skyless.Assets.Code.Skyless.Game.Data.CharacterRepository.EnsurePresenceOfSnippets ()
    in your output/player logs then your savesnippet file may have become corrupted. This can happen if the game has shut down unexpectedly and did not save correctly. Email us at skies@failbettergames.com with your three save files and we’ll sort this for you.
  • If you see an exception that begins InvalidOperationException: Operation is not valid due to the current state of the object
    at System.Linq.Enumerable.First[FileInfo] (IEnumerable`1 source) [0x00000] in :0
    at Skyless.Assets.Code.Skyless.Utilities.FileHelper.GetMostRecentlyModifiedFileInPath (System.String path) [0x00000] in :0
    at Skyless.Assets.Code.Skyless.Game.Data.CharacterRepository.EnsurePresenceOfSnippets () [0x00000] in :0
    then this is due to one or more empty Lineage folders within the characterrepository directory. You can resolve this by going through all Lineage folders present and manually deleting any empty ones.
  • If you see (SteamAPI_init() failed) in your output/player logs then the Steam app may not be running correctly. If you see this try the following:
    • Try restarting Steam
    • Try logging in and out of Steam and restarting
    • Check your Antivirus or Firewall settings. Updates have been known to put games in the AV/Firewall sandbox/quarantine
  • If you see 'Initializing Microsoft Media Foundation failed.' in your output/player logs then Microsoft Media Foundation is not installed on your machine or a newer version of Microsoft Media Foundation is required. If you see this please install the Media Feature Pack from https://www.microsoft.com/en-us/search/result.aspx?q=Media+Feature+Pack for your version of Windows. The Media Feature Pack that comes up upon a simple google search is NOT the correct version for Windows 10 after the Creators Update – it’s necessary to look for the newest Media Feature Pack from April 2017 (available here). If you are on Windows 10 N, Sunless Skies may not run even after installing Microsoft Media Foundation pack and re-enabling Windows Media Player. Reinstalling Windows 10 resolves the issue.
  • If you see IndexOutOfRangeException: Array index is out of range.
    at UnityEngine.Display.RecreateDisplayList (System.IntPtr[] nativeDisplay) [0x00000] in :0 in your output/player logs then this is due to a bug that was released in Windows 10 1709 that is causing this issue with a lot of Unity games. There is an excellent thread about it on Steam with lots of advice on how to resolve the issue. Check it out the OP’s trouble shooting steps as it has resolved the issue for a lot of people.
  • If you see WindowsVideoMedia error 0x800700ea while reading
    C:/Program Files (x86)/Steam/steamapps/common/Sunless Skies/Sunless Skies_Data/sharedassets0.resource
    Context: CreateObjectFromByteStream
    Error details: More data is available.
    in your output/player logs then you may be missing a media feature pack or a video codec pack. There is an good thread about it on Steam with advice on how to resolve the issue. One of our players resolved this issue by “going into the K-Lite Codec Tweak Tool, checking under Windows Media Foundation, and manually unchecking all of the boxes”

Back to top

 

Minimised game window

Some players have recently experienced the game opening at a resolution of 0 x 0 pixels and are therefore unable to play (audio can be heard, but nothing is displayed). If this happens to you, please try the following:

Windows

      1. Go to C:\Program Files (x86)\Steam\steamapps\common\Sunless Skies
      2. You’ll see the Sunless Skies app. Please press and hold down Ctrl, then double click on the game. Keep Ctrl pressed down the whole time until the Sunless Skies Configuration window opens (if it doesn’t open first time, just double click again)
      3. Select a resolution from the drop down list
      4. Click play to launch Skies

Linux

    1. Go to ~/.config/unity3d/Failbetter Games/Sunless Skies/
    2. Open the prefs file and scroll right to the bottom
    3. Find <pref name=”Screenmanager Resolution Height” type=”int”>xxx</pref> and change the value of xxx to 720
    4. Find <pref name=”Screenmanager Resolution Width” type=”int”>xxx</pref> and change the value of xxx to 1280
    5. Save the file and close it before launching the game

Back to top

 

Crashes

If you experience a crash please send your crash logs to us at skies@failbettergames.com. Advice for specific crashes is listed below:

Transit Relays

If you experience a crash when using transit relays please take the following steps:

      1. Relaunch the game. On the Title Screen select Options > Graphics
      2. Set the Texture Quality to Low and click Apply
      3. Come out of the menu and then click Continue
      4. Try going through a relay again

If you continue to experience the issue after taking these steps then send us your output log and machine specs.

Character Creation

If you experience a crash (or black screen) at the point of character creation please take the following steps:

      1. Relaunch the game. On the Title Screen select Options > Graphics
      2. Set the Texture Quality to Low and Transparent UI to Off
      3. Change Full Screen to Off
      4. Click Apply and back out of the menu
      5. Click Continue

You should be loaded in at the point of character creation. If you continue to experience the issue after taking these steps then send us your output log and machine specs.

Crash on launch

If you experience a crash when first launching the game and you see an error beginning Crash!!! SymInit: Symbol-SearchPath: in your output log, then it’s possible another application is interfering with the game. Citrix Workstation (formerly Citrix Receiver) causes this issue with a number of Unity games, try uninstalling Citrix, restarting your machine and launching Skies again (we have reports from players that Skies will continue to play without issue once the latest version of Workstation is reinstalled).

Back to top

 

Graphical Corruption on Linux

If you experience graphical corruption on non 16:9 resolution s on Linux then use “-force-glcore42 -force-clamped” as outlined here. Using “-force-vulkan” as a launch option will unfortunately break your headlight.

Back to top

 

Controls not working correctly

If you find that your bat will no longer deploy (even when remapped) and that closing the main menu does not unpause the game then you need to restore the control scheme to defaults. This will clear any previous setting that have become muddled from playing Early Access builds. Even if you experience an issue like this but didn’t play before the launch build on 31st Jan, give the steps below a try first before contacting us.

  1. Relaunch the game. On the Title Screen select Options > Controls
  2. Click Restore Defaults
  3. Come out of the menu and then click Continue

If you continue to experience the issue after taking these steps then send us your output log and machine specs.

Back to top

 

Blue Kingdom Access

Cannot Access Blue Kingdom

If you played before the launch build and your captain died and passed on a legacy, you will be missing a quality that at the time was not persistent on death. Send your save files to us at skies@failbettergames.com and we’ll sort you out. This issue was resolved in the launch build so anyone dying after 31st Jan will not see this issue.

Back to top

 

Gamepad issues

Gamepad bugs

While there are outstanding controller bugs, we’ve had numerous reports of issues with controllers that have been fixed in the live build, some of which we cannot reproduce. We also know about the issue where gamepad controls are not reset when clicking Restore Defaults from the controls menu. We need those who are using gamepads to take the following steps to ensure controls are restored to defaults (especially if you’ve ever played before the launch on 31st Jan, with or without a gamepad). Anything that is seen after following these steps is a genuine bug and should be reported to directly to our ticketing system at at skies@failbettergames.com so we can investigate and fix. As always we appreciate your patience while we fix these problems.

      1. Close Sunless Skies
      2. Type regedit into the Windows search bar
      3. Click on regedit in the results to open the Registry Editor
      4. Navigate to Computer\HKEY_CURRENT_USER\Software\Failbetter Games
      5. Inside you’ll see the Sunless Skies folder – delete it
      6. Relaunch the game

Deleting the Skies regedit file is fine but please do not alter its contents. Doing so can seriously break things if you don’t know what you are doing.

Back to top