Everything posted by sunfish62
I am running Astroneer 1.4.15 on an XBox One, and I have noticed that Astroneer takes a lo-o-o-o-ong time to load at start up--on order of minutes. I could perhaps live with this, even though it is an interminable wait, watching the little planets circling the mini sun over and over, except for the fact that it appears that Astroneer takes many minutes to load the solar system, brings up the opening menu, where the user must select the game they wish to play, and then... sit through YET ANOTHER solar system load. I do not know what is going on in each of these stages of startup, but if they are both loading solar systems, couldn't the first load be eliminated, cutting load time in half? If the two phases are loading different things, then I'll live with it--although maybe a change of the system message would be in order--like "Initializing Astroneer" in the first case...
OK. I know this is an ongoing issue because I have seen messages on the Internet for over eight months on this: Astroneer has the evil habit of crashing on save every third or fourth save. This has been true for several versions now, and is still a problem. For the record, my system just updated two days ago, but I don't have that version right at hand because in my frustration, I TURNED OFF ASTRONEER. Developers, TAKE NOTE: Not fixing a Crash on Save bug IS A BIG DEAL, AND WILL LIKELY LOSE YOU ALL YOUR CUSTOMERS, NOW AND IN THE FUTURE. It doesn't help your cause when it takes FIVE MINUTES to get the game up and running again. Talk about a buzzkill! BTW: For those who will send me references to existing bugs, or existing discussions, I say this: "As a paying customer, I should not have to search some website for long discussions about the intricacies of programming, etc. I expect to play a game and NOT HAVE IT CRASH WHEN I TRY TO SAVE. Astroneer is NOT FOSS."
sunfish62 replied to Buster Drift's topic in Bug Reports, CrashesI've encountered the same problem. Appreciate Jim's suggestion (which I have yet to try), but it does seem to be a bug.