This was originally going to be an article detailing all the improvements to Planet Nomads, sadly I've had to rewrite this due to the fact of the Linux version being mostly broken.
The Linux version has sadly seen a rather big lack of attention for some time now. On August 29th, I reported to the developer that the game was freezing on the loading screen. It's now October and the situation hasn't really changed at all, with seemingly no progress being made and a lack of feedback from the developer on the issue.
They haven't replied in the Steam post since September 3rd, although they did tell us on Twitter on September 18th "Dang! We are going to examine this. Thanks for the headsup!". I seem to be able to load it once, after that it either freezes while loading or quits to the desktop. A good 90% of the time I have to manually kill the process due to it freezing.
I'm sad about this, because the game has seen so many improvements across many updates since we last covered it, that excited me to talk about it again. Things like an actual tutorial to properly walk you through the basics, massively improved performance and so much more but this has been marred by the issues.
For now, I would urge you to give it a miss until they give the Linux version the attention it needs.
Seems to happen across Ubuntu, Mint, Arch and possibly others. I found their working database file for saved games, seems to get malformed at somepoint, which seems to be the issue. The root cause though...no idea unless I saw what queries they're doing.
Last edited by Liam Dawe on 1 October 2018 at 8:03 pm UTC
Game uses system libraries that are incompatible on newer systems
You *COULD* try overriding, but there are simply to many libraries for me to bother
Quoting: DuncThere's a weird flickering/glitching on the menu screen that I've been meaning to report for weeks (it looks for all the world like a hardware fault, except I don't have any other problems), but the game runs well enough.
I saw that too. Only on fullscreen though, when I set it to windowed it went away. Even my "G-SYNC" indicator was flickering, meaning it must be doing something pretty crazy.
Quoting: GryxxDelete wine-mono and mono packagesDidn't have wino-mono, did have system mono installed. Removed it and re-tested.
Game uses system libraries that are incompatible on newer systems
You *COULD* try overriding, but there are simply to many libraries for me to bother
Initially it loaded more often (about 8 successes), then it froze on one attempt and the very next attempt crashed it to the desktop. So I don't think that's the root cause of the issue.
Quoting: liamdaweInteresting. So you get literally no issues if you load it, quit to menu, start an entirely new world in survival on a new seed. Repeat that twice to see what happens (just to see if we can trigger it).Nope. Tried it three times, just to be sure.
Since I can reproduce it so often (with reports from others too) it's definitely a bug.
Like gurv, I have a faint recollection of it possibly crashing during loading once, but only once. And I'm not even sure about that.
If it's corruption of a common database rather than one generated for each save, it's possible I haven't played it enough recently to trigger it. That said, I'd forgotten that I did lose one save to some kind of corruption: whenever I load it, I'm in my base, but the tutorial triggers (which obviously can't be completed, because I'm not in the ship), and there's no planet.
Last edited by Dunc on 1 October 2018 at 11:25 pm UTC
I bought the game when it said it was multiplayer so kinda got conned. No doubt it will just get a forced broken alpha release at some stage just like starforge did... terrible, wish I could get my money back!
Last edited by TheRiddick on 2 October 2018 at 1:10 am UTC
Quoting: liamdaweTurned the graphical preset to Low, so everything was down. Tried another new survival game - crashed to the desktop. This time, stuff like this was being spammed into the log:I had the same error in the logs. After repairing the SQLite database, the game worked again. I have repaired the database _working.db with the help of this page: http://www.froebe.net/blog/2015/05/27/error-sqlite-database-is-malformed-solved/
QuoteException Mono.Data.SqliteClient.SqliteSyntaxException - database disk image is malformed during BulkExecute: INSERT INTO [active_blocks]([id], [type_id], [data], [container_id]) VALUES (?, ?, ?, ?)
StackTrace:
Quoting: liamdaweUpdate: It seems I've found others also having the same issue: https://forum.planet-nomads.com/threads/2777-EXTREME-PRIORITY-Crash-the-game-when-you-start-a-new-game-or-try-to-start-saving
Seems to happen across Ubuntu, Mint, Arch and possibly others. I found their working database file for saved games, seems to get malformed at somepoint, which seems to be the issue. The root cause though...no idea unless I saw what queries they're doing.
The database is probably not corrupted due to queries (sqlite is a very robust engine) but when the game crashes in the middle of a write. So the first crash is not due to sqlite but every one after that is since the first crash corrupts the database.
Quoting: F.UltraThe database is probably not corrupted due to queries (sqlite is a very robust engine) but when the game crashes in the middle of a write. So the first crash is not due to sqlite but every one after that is since the first crash corrupts the database.An sqlite database can usually survive even a crash, as all transactions are basically atomic under the hood with automatic recovery from the journal. But of course there are other ways to corrupt the db if you really try, like messing with the file directly, or messing up directory access so that sqlite can't create its journal and then crashing.
Quoting: liamdaweQuoting: gurvHey Liam, sorry to hear you can't run the game.I tried your suggestion, turning terrain texture quality to Low. It crashed to the desktop twice, got me in the third time. Then I tried turning the terrain view distance down to low, first time it froze on the loading screen.
I've been pretty busy myself diving into this really good game lately (already 50 hours in and counting) and I don't have that many problems. It's actually very decent for an early access game.
I think your problem could come from the "ground texture quality" or the "ground display distance" (or whatever these settings are named: my UI is in French, so I'm not sure).
On my computer, anything higher than "low" for these settings rapidly freezes the game (though it does load).
I'm currently running everything on low/off except :
- grass density (very high)
- anisotropic filtering (on)
- shadow quality (medium)
- texture quality (very high)
- camera effects (shining on & sunshaft on)
With these settings, the game runs great most of the time.
I only have two big complaints so far:
- performance slows to a crawl (60fps -> 17fps) sometimes seemingly randomly (tough it happens mostly when traveling in vehicle). It's very strange because reloading the game fixes it... for a while. It seems Windows users are also experiencing this issue.
- In 3rd person view, when loading a game, the camera starts zoomed out even more than the max zoom out. This oftens leads to seeing nothing because the camera is actually inside the groung. Zooming out once and then painfully slowly zooming in fixes it though.
Edit: I recall now having the game freeze during the loading of the map! But it happened just once in so many times. And I'm not sure it was frozen: it may have taken what looked like forever to generate the world.
This gets spammed to the log a lot (and I really do mean A LOT):
QuoteSQL logic error
at Mono.Data.SqliteClient.SqliteCommand.ExecuteStatement (IntPtr pStmt, System.Int32& cols, System.IntPtr& pazValue, System.IntPtr& pazColName) [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) Mono.Data.SqliteClient.SqliteCommand:ExecuteStatement (intptr,int&,intptr&,intptr&)
at Mono.Data.SqliteClient.SqliteDataReader.ReadpVm (IntPtr pVm, Int32 version, Mono.Data.SqliteClient.SqliteCommand cmd) [0x00000] in <filename unknown>:0
at Mono.Data.SqliteClient.SqliteDataReader..ctor (Mono.Data.SqliteClient.SqliteCommand cmd, IntPtr pVm, Int32 version) [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) Mono.Data.SqliteClient.SqliteDataReader:.ctor (Mono.Data.SqliteClient.SqliteCommand,intptr,int)
at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader (CommandBehavior behavior, Boolean want_results, System.Int32& rows_affected) [0x00000] in <filename unknown>:0
at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader (CommandBehavior behavior) [0x00000] in <filename unknown>:0
at Mono.Data.SqliteClient.SqliteCommand.ExecuteDbDataReader (CommandBehavior behavior) [0x00000] in <filename unknown>:0
at System.Data.Common.DbCommand.ExecuteReader () [0x00000] in <filename unknown>:0
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader () [0x00000] in <filename unknown>:0
at Database.SQLite+Command.ExecuteReader () [0x00000] in <filename unknown>:0
Turned the graphical preset to Low, so everything was down. Tried another new survival game - crashed to the desktop. This time, stuff like this was being spammed into the log:
QuoteException Mono.Data.SqliteClient.SqliteSyntaxException - database disk image is malformed during BulkExecute: INSERT INTO [active_blocks]([id], [type_id], [data], [container_id]) VALUES (?, ?, ?, ?)
StackTrace:
at Mono.Data.SqliteClient.SqliteCommand.GetNextStatement (IntPtr pzStart, System.IntPtr& pzTail, System.IntPtr& pStmt) [0x00000] in <filename unknown>:0
at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader (CommandBehavior behavior, Boolean want_results, System.Int32& rows_affected) [0x00000] in <filename unknown>:0
at Mono.Data.SqliteClient.SqliteCommand.ExecuteNonQuery () [0x00000] in <filename unknown>:0
at Database.SQLite+Command.BulkExecute (System.Object[,] parameters) [0x00000] in <filename unknown>:0
(Filename: ./Runtime/Export/Debug.bindings.h Line: 43)
#3 0x007ffea1175e90 in operator new[](unsigned long, std::nothrow_t const&)
#4 0x007ffea1176000 in operator new[](unsigned long, std::nothrow_t const&)
#5 0x007ffea1176170 in operator new[](unsigned long, std::nothrow_t const&)
#6 0x007ffea11761f0 in oc_frag_recon_inter2_c
#7 0x007ffea11767e0 in __libc_start_main
#8 0x007ffea11768a0 in oc_frag_recon_inter2_c
If i dont go back and forth between new worlds I NEVER get a crash with nvidia and every thing looks normal using the closed drivers. If i use ati or nvidia with open source drivers i get some texture issues but it is very playable.
they have also been working on the various bugs that I have verified my self while going through their forum not steam. i believe 9.4 and above are on new version of unity but not sure. since i got it it has been making progress.
See more from me