Matrix Games Forums

Is server dead?

Due to an issue with screen artifacts i had to close the game. And i was able to load my save without problems. It shows that retry function that game suggests, after error in this report is gone is not functioning properly either.

same issue again

Can we get save function fixed?

Is this something that happens periodically when the server is down or you have bad internet connectivity and are trying to save? IIRC, Pavel did what he could to allow retries, but I don't think there's anything more we can do on our end.

I have no problems with an internet, and server is, most likely also OK, as when i close the game and immediately (like 10-20 sec from the moment i closed the game) try to load the save then it loads just fine.
Problem is that retry function is not actually doing what it is supposed to do. Maybe some authentication or something else is broken there.

When i encountered the issue for the first time then i saw that it says to try again later (next message that is present after "bad allocation, Press any key to continue"). I tried for one hour to save the game and it was always the same issue and error message. After closing the game, i was able to load the save just fine, as i described above. That is why i have this conclusion that these retry function is broken and not doing what it is supposed to do. And it is supposed to actually retry to save the game, as message in the game suggests.

Btw it is game vs Peltonx if you need to test it.
Game vs Fobos is working good, so far.
In case there is any difference.

Is anyone else experiencing this problem? I see Peltonx has at least 4 active games going now. IIRC, the system was not expected to work in all cases, but was intended to at least provide some additional feedback to the players, and to allow them to try saving later if the issue is due to a poor connection or the server being down. You may have some other kind of corruption going on that prevents saving once it has kicked in as you play. Loading the old save clears the corruption, which than may happen again as you play. I'm just speculating on this.

You might be right about some save corruption. However i had no such issues in the past. Also i am playing as i always did. Not trying to abuse any game mechanics or anything in a similar manner.
One way to check if that retry function is working is to ask programmer(s) to find that error message and then run the retry function with some of my saves as a payload and see a result. My result is that it is not doing anything, no matter how long i wait and retry.

Btw i have two games:
vs Peltonx
vs Fobos

I don't recall having this issue in game vs Fobos. And we are almost at the same turn as i am in the game vs Peltonx. Comparing saves from those two games might help spotting something odd in the save where i play vs Peltonx.

Looking at saves, I think Peltonx is running 1.04.12 in the latest turn, as the Soviet event log showed logistics was run with 1.04.12. You and Fobos appear to be both running 1.04.14. Did you just update to 1.04.14? Going back and forth between exes could cause a problem. So if you run 1.04.14 but Pelton then uses 1.04.12, this might be a source of corruption. It would help to know if you are going back and forth with different versions. Either way, I don't have high expectations of it being easy to figure out the issue. It also could just be the limitations of the retry system (but I'm not a programmer, so having the programmer look at your info could help).

Since you say this happened before, I assume you've been able to continue your game, right? I realize I don't understand this sentence of yours:

"Due to an issue with screen artifacts i had to close the game. And i was able to load my save without problems. It shows that retry function that game suggests, after error in this report is gone is not functioning properly either."

Before I pass this on to the programmer could you clarify these things, thanks.

I did not specifically check which version of the game Peltonx is using right now. I believe that we started with 1.04.12 and later on i updated to 1.04.14. I do not downgrade my game version. Once it was updated to 1.04.14 - i have been using it all of the time.

"Due to an issue with screen artifacts i had to close the game. And i was able to load my save without problems. It shows that retry function that game suggests, after error in this report is gone is not functioning properly either."

I think what i meant was that once error, that is shown on the first screenshot in the first post of this topic: "bad allocation Press any key to continue" is gone, there is another message, which i did not capture, but it is something like "retry again later". And this retry function is not working.

I assume you've been able to continue your game, right?

Yes. But progress that i did from the previous successful save is lost. Since retry function is not working and i have to close the game and load it again.

I checked an AAR that i am doing and i had the reported error on 1.04.12 too.

Ok, thanks for the added info. Probably not related to the switching of versions, but in any case, you should encourage Peltonx to upgrade so you are on the same version going forward (if he hasn't already done so). I'll pass the info along. I appreciate that it's a pain to lose a bunch of game time when you can't save and have to revert to the earlier save. Hopefully it will be a rare occurrence, especially if Pavel is unable to improve the situation.

After discussing with Pavel it's clear this isn't something we can improve on. The bad allocation message is coming from non-game code, so he can't tell whether the error is due to an issue with the server, internet connectivity, the local computer, or something caused by the game as it interacts with these things. At most, he may be able to add some clarifying text. The retry system is just meant to provide a chance to save later if it is due to the server or your internet being temporarily down. If some other problem is causing the inability to save, you'd have to go back to your prior save. Hopefully those instances will be rare.

Thanks for looking into it. Not an answer i was hopping for, but i got used to make a save after a couple of battles so i dont lose much progress when this error happens.