YouTube videos require cookies, you must accept their cookies to view. View cookie preferences.
Direct Link
Direct Link
Those were my two main complaints about the game, so it makes it a lot more playable for me personally. No longer do I need to squint to read anything, so I am now actually looking forward to giving the game a full run.
About the game (Official)
LOSE YOUR MIND. EAT YOUR CREW. DIE.
Take the helm of your steamship and set sail for the unknown! Sunless Sea is a game of discovery, loneliness and frequent death, set in the award-winning Victorian Gothic universe of Fallen London.
If the giant crabs, sentient icebergs and swarms of bats don’t get you, madness and cannibalism certainly will. But that old black ocean beckons, and there’s loot for the brave souls who dare to sail her.
Betray your crew, sell your soul to a Devil, marry your sweetheart. Survive long enough and you’ll achieve your life’s ambition.
You will die, but your legacy will live on…
Some you may have missed, popular articles from the last month:
7 comments
Great news! UI-scaling is something I miss in far to many game-titles and they *finaly* added the steamOS icon to the store page as well. Now the only question is wether to buy immediatly, or to wait for the "Zubmariner" update/expansion that comes out in 17 days
0 Likes
At last!
I could barely read the texts.
Yeah, too many hours in front of a screen.
I could barely read the texts.
Yeah, too many hours in front of a screen.
0 Likes
I tried the game once, but the small text instantly stopped me to continue playing. Now that it is updated, I can't play because the game crashes. This part of the log messages:
Anyone with my same problem?
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
Sunless Sea.x86_64: xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Stacktrace:
Native stacktrace:
/media/procolo/SteamLibrary/steamapps/common/SunlessSea/Sunless Sea_Data/Mono/x86_64/libmono.so(+0x91772) [0x7fa01dae5772]
/usr/lib/libpthread.so.0(+0x11080) [0x7fa0232a5080]
/usr/lib/libc.so.6(gsignal+0xcf) [0x7fa021a9704f]
/usr/lib/libc.so.6(abort+0x16a) [0x7fa021a9847a]
/usr/lib/libc.so.6(+0x2bea7) [0x7fa021a8fea7]
/usr/lib/libc.so.6(+0x2bf52) [0x7fa021a8ff52]
/usr/lib/libX11.so.6(+0x41e79) [0x7fa022b0de79]
/usr/lib/libX11.so.6(+0x41f2b) [0x7fa022b0df2b]
/usr/lib/libX11.so.6(_XEventsQueued+0x5d) [0x7fa022b0e23d]
/usr/lib/libX11.so.6(_XGetRequest+0x55) [0x7fa022b10fa5]
/usr/lib/libX11.so.6(+0x450bf) [0x7fa022b110bf]
/usr/lib/libX11.so.6(_XError+0x131) [0x7fa022b10891]
/usr/lib/libGL.so.1(+0x1d352) [0x7fa022e31352]
/usr/lib/libGL.so.1(+0x19464) [0x7fa022e2d464]
/media/procolo/SteamLibrary/steamapps/common/SunlessSea/Sunless Sea.x86_64() [0xe9ffcf]
/media/procolo/SteamLibrary/steamapps/common/SunlessSea/Sunless Sea.x86_64() [0xea0cb2]
/media/procolo/SteamLibrary/steamapps/common/SunlessSea/Sunless Sea.x86_64() [0xe9d247]
/media/procolo/SteamLibrary/steamapps/common/SunlessSea/Sunless Sea.x86_64() [0xe9e5d9]
/media/procolo/SteamLibrary/steamapps/common/SunlessSea/Sunless Sea.x86_64() [0x78bfa1]
/media/procolo/SteamLibrary/steamapps/common/SunlessSea/Sunless Sea.x86_64() [0x46524a]
/usr/lib/libc.so.6(__libc_start_main+0xf1) [0x7fa021a84291]
/media/procolo/SteamLibrary/steamapps/common/SunlessSea/Sunless Sea.x86_64() [0x46e6c9]
Anyone with my same problem?
0 Likes
And my copy has had 3 updates just this afternoon, a fix for the fix that fixed the original fix, hopefully it'll work after all that.
0 Likes
I've just gave the game another opportunity.
But now I'm experiencing a graphical glitch, I don't know it's game's or driver's fault.
It's the map.
I can't see the terrain forms in the map. It is just blank with the names of the locations on it.
Sometimes I can see both the ports and locations texts; some others I only could see the ports.
Is there anyone experiencing this?
PS : nVidia nouveau free driver over Mesa 12.
Last edited by Ivancillo on 24 September 2016 at 5:54 pm UTC
But now I'm experiencing a graphical glitch, I don't know it's game's or driver's fault.
It's the map.
I can't see the terrain forms in the map. It is just blank with the names of the locations on it.
Sometimes I can see both the ports and locations texts; some others I only could see the ports.
Is there anyone experiencing this?
PS : nVidia nouveau free driver over Mesa 12.
Last edited by Ivancillo on 24 September 2016 at 5:54 pm UTC
0 Likes
Quoting: IvancilloI've just gave the game another opportunity.
But now I'm experiencing a graphical glitch, I don't know it's game's or driver's fault.
It's the map.
I can't see the terrain forms in the map. It is just blank with the names of the locations on it.
Sometimes I can see both the ports and locations texts; some others I only could see the ports.
Is there anyone experiencing this?
PS : nVidia nouveau free driver over Mesa 12.
I had the same problem (nvidia / HD Intel). The map was all white, no update, no landmass. I turned the BETA to ON in Steam (zmbeta) and all was fine from there.
I hope it helps
0 Likes
Quoting: ziabiceI tried the game once, but the small text instantly stopped me to continue playing. Now that it is updated, I can't play because the game crashes. This part of the log messages:
[code]
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
Sunless Sea.x86_64: xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Anyone with my same problem?
Yeah. This seems to be a Unity3d bug - a bunch of games have started dying on me under Linux with this error.
Various fixes involving switching graphics output libraries are floating around. What worked for me was turning DRI3 off in the Xserver, to force the use of the (older) DRI2 API.
If you're running a stable Ubuntu release, a Unity3d game will probably work. Anything that tracks the bleeding edge a little more (Fedora, Arch, Debian Testing etc etc) is likely to have problems occasionally.
0 Likes
See more from me