Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
Try using the Steam facility to verify the integrity of your game files.
But frankly the problem you describe looks like faulty memory, or some other hardware fault.
So either your PC is not meeting the system requirements, or, as Pesky said, something in your hardware is faulty.
a) The game's error handling is inadequate.
b) The problem I already knew the cause of before I posted (which has nothing to do with the integrity of the files or faulty hardware).
So I installed HWInfo and started launching it before I started gaming. Turns out the SSD on that PC, NVMe M.2 was past its prime, and was overheating due to all the re-writes. So I replaced it and everything became fine once again.
As for error log files, not all games have them, so you'll just have to decide if you can bring yourself to tolerate such a rude oversight by the 2 young, new devs who are building this game all by themselves, as a labor of love. And if it really matters that much to you, hit F8 and give them an earful.
Or you could forgive them this oversight and figure out the root cause of your problem on your own, with the help of the Steam Hardware forum.
The game does have logs.
The problem is either that the game ignores errors, fails to handle error appropriately, and/or doesn't use time-outs to detect when something (e.g. GPU) has locked up; and this forces the user to terminate the game and prevents that game from putting anything useful in its log.
In other words; the problem is that the game has inadequate error handling.
For a very silly example, imagine something like "do { status = something(); } while(status != OK)". It's trivial to see that this is silly and will lock a game up; and every sane software developer would consider this a bug (and that it'd work for all of the "I don't get any errors so the error handling is fine" people).
So it sounds to me like your GPU is freezing, and because your GPU is freezing, which the game code has not way of knowing about because it's a hardware or driver issue that does not send any information back to the DX API, you think that the GAME is ignoring errors.... Well, no, that's not how it works.
The game doesn't have inadequate error handling if the thing that's going wrong couldn't possibly be handled in game. The game is being terminated as someone else said, because your OS cannot assign the hardware to the task it's being asked to do, and so the application attempting to use that hardware is killed.
The last bit is just the usual complaint from someone that's been told by an engineer how something works and you didn't like it.
There's been very few people on here complaining about crashes and they fall in to 1 of a few categories.
They have a hardware fault.
Their system is below the minimum specifications.
They're trying to play on an unsupported OS (Windows XP / Linux etc...)
They have incompatible hardware.
They have a driver issue.
In all of these cases the problem is the users setup and the game itself never errors because the error is not in the game, it's in the hardware, driver, or OS.
It seems to me like you have fallen in to this same category, but rather than trying to find the root cause of the problem and fixing that, you're blaming the game.
A bad video driver could cause it, but it really sounds more like H/W.
The fact that no one else is mentioning issues like that implies it is a problem local to you/your system.
What are the specs of your computer?
Nonsense. A game must (when working normally) know when the GPU is ready for the next frame, and therefore (at an absolute minimum) it must be possible to have a time-out (e.g. if it takes more than 5 seconds for the GPU to be ready for the next frame).
However that's not really how DirectX works. Windows has a built-in time-out and will restart the video driver; and after that the game is told "device disconnected" for every API call and the game is supposed to handle this by reinitializing the graphics (possibly after using something like "ID3D10Device::GetDeviceRemovedReason()" and logging the problem).
There literally isn't a single API call in Windows that any application can use to request any kind of resources that doesn't return an error code if the requested resources aren't available.
Please understand that I am not complaining about crashes (my test machine is slightly below the minimum specs - see note); I'm complaining that the game fails to handle the crashes adequately.
Note: I do this deliberately (and especially for early access games and games written in Unity). Far too many colony/building/factory games have game breaking performance issues in late game that aren't apparent in early game; so to avoid spending 200+ hours just to find out that the game sucks I test them on a "potato" to weed out all the poor quality games early. Ironically; the performance of Planet Crafters is fine, up until it crashes.
Most people with similar issues will just say "LOL, this developer sucks and I'll never buy anything from them" without ever making a single comment. Someone actually bothering to mention it is an isolated incident; but that doesn't mean people having software issues (including the "game is bad at handling hardware issues" software issue) is isolated.
No. Years of experience has taught me that "below minimum" almost always means that the developers couldn't be bothered determining what the real minimum is (and that it'll probably still run, likely with worse FPS) but you might get a "Computer isn't supported" error message when you try to start the game (e.g. because something like DirectX12 isn't supported). I'm perfectly fine with all of that (including a nice "Not supported" error at startup).
Never in my life have I seen software actually crash (and/or lock up the computer) because the minimum isn't met - it takes a lot of incompetence for a developer to suck that badly.
Right. People that don't have issues don't complain, and people that do have issues rarely complain.
Honestly; I'm not even sure it crashes because I'm below minimum. Given that it works fine for a while and then crashes when nothing changed it's more likely to be some kind of resource leak.
I guarantee that sooner or later there will be a bug somewhere, and all of the people that failed to understand "the error handling is bad" because they don't have problems yet will be come face to face with the problem I'm warning about (hard crashes, no error handling, no clues in logs). I wouldn't be too surprised if the developers abandon the game at this point (how do you fix bugs when there's no clue what the bug is when 90% of the customers are screaming at you? Better to take the early access $$ and disappear).
There are plenty of people who have complained about issues with this game, but no one has complained about your issue. So as others have stated it seems to be a you issue, not a game issue. Cause if it was a game issue, I'm sure we would have plenty of posts complaining about it crashing for no known reason, and requiring not just a restart of the game, but a hard restart of the computer it is being played on. As an example, many of us have complained about clipping issues, myself included, I was flying around looking for where the icon for the key was (this was when they were first added) and suddenly was stuck in a mountain that wasnt there moments before hand. Now I did have a rare issue of F4 not working for me in that instance. But if you search, there are tons of us complaining about the clipping issues, suddenly appearing mountains, ect. But if you search for the game crashing you find very few (that are actually about the game crashing) and some of those are from the dev branch which isnt fully flushed out yet anyway. So most of us that play this game have posted when we have a problem, so saying that people who have issues rarely complain, isnt exactly accurate when it comes to this game.