About the "saved in a previous version' error

[Redpossum]

There is a situation in which the game can generate this error, when in fact there is no problem at all. It just happened to me (spuriously), so let me explain.

OK, I was playing against the AI, and it was April 1943.

I usually save at start of game-turn using a set of saves labeled T1 through T6. At the end of that cycle, I make a save with the name of the month and year, then start over again with T1.

As I said, it was April 1943. So at the start of the turn, I went to the save screen, typed "April 43", and pressed Enter. I selected my first unit, changed my mind and went to select a different unit, but mis-clicked and wound up moving the first unit instead of selecting the second one.

Not a problem, I go to the menu, choose "End Game", wait until the game dumps me back at the Main Menu, then choose "Load Game".

Here's where it gets tricky. My last save was still in the window, so I clicked "OK" to load it, and promptly got the "This save was created with a previous version yadda yadda yadda."

Back at the load window, I looked again and realised that my last save was still in the selection box exactly as I had typed it, meaning there was no ".DATA" on the end. And that was what caused the spurious error. As soon as I gave it the full name of the savefile to load, everything was fine.

[IainMcNeil]

Thanks, interesting find. I'll ask Johan to check it out.

[firepowerjohan]

Thanks, we did not expect ppl to type in the name of a save but instead to click on it

[Redpossum]

Thanks, we did not expect ppl to type in the name of a save but instead to click on it

Of course, Johan, understood. It's just one of those weird things that crops up.

And it wasn't a criticism, just an observation that the game may be reporting spurious errors. So some of those weird error reports of this type, that seem to make no sense, may not in fact be real errors or any problem at all.

[firepowerjohan]

The error message is wrong since it is too specific, for future version the error will be more generic to avoid ppl ripping all their hair out of their roots from a error that is not the real error

[Redpossum]

The error message is wrong since it is too specific, for future version the error will be more generic to avoid ppl ripping all their hair out of their roots from a error that is not the real error

Johan, have you seen the corresponding message in that certain beta test forum?

I notice nobody has replied there at all...

If so, please reply there rather than here, so we don't go saying anything NDA-bending in this public venue