Confused on Steam Play and Proton? Be sure to check out our guide.
We do often include affiliate links to earn us some pennies. See more here.

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.

Article taken from GamingOnLinux.com.
8 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. Find me on Mastodon.
See more from me
The comments on this article are closed.
21 comments
Page: «3/3
  Go to:

F.Ultra Oct 3, 2018
View PC info
  • Supporter
Quoting: tuubi
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.

And you can be on a filesystem or HDD where fsync() does not do what was intended.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.