All Preview save files are incompatible now? This is a horrible idea

[Maffen on Linux]

Just making old saves incompatible is a horrible way to go about this. I would have assumed the devs would adjust the saves to fix anything that is "messed up", but since this was an unstable branch I can understand that you don't want to put too much time into legacy code and such.
HOWEVER ... obviously you wouldn't simply lock out players. You should, when the player wants to load an 'incompatible' save file, quite simply display a warning in bold letters that loading an old game can lead to game-breaking bugs. Ignore all bug reports from players playing old save games, but just let them load it anyways. If it breaks, it breaks. I would assume it won't though. Why do I have a feeling that editing the save file will result in a perfectly playable game? There's no way the last Preview 27 and current Patch 1 are that different.
You're pissing off your players for no good reason.

[[XIII]Opsec]

Everyone who opted into playing the beta knew they were helping to test the game and find bugs, not start a game long career.

[WhjiteWolf]

jUST START A NEW GAME!!
My God, the internet age certainly brings them out.

[nZ RaifalM3n]

Oh, the humanity.

Dude , i lost some ♥♥♥♥ too. Grow up and restart. Its a game.

You need more clowns.

[Maffen on Linux]

What a wonderful community... Utterly incapable of reading a couple of sentences.
I come from a game dev and coding perspective. This is quite simply bad design. A flag has been set and thus people are losing all their progress for no reason at all. I didn't even lose that much myself tbh. But thinking of losing tens, maybe hundreds of hours of campaign progress just because the save game has been flagged as incompatible without that being necessary at all. Well as I said ... pissing off players for no reason. But I'm sure this has been too many sentences again... Not sure why I'm even trying tbh

[[XIII]Opsec]

Originally posted by Maffen:

What a wonderful community... Utterly incapable of reading a couple of sentences.
I come from a game dev and coding perspective. This is quite simply bad design. A flag has been set and thus people are losing all their progress for no reason at all. I didn't even lose that much myself tbh. But thinking of losing tens, maybe hundreds of hours of campaign progress just because the save game has been flagged as incompatible without that being necessary at all. Well as I said ... pissing off players for no reason. But I'm sure this has been too many sentences again... Not sure why I'm even trying tbh

Why chase after bugs that may be caused from incompatible versions when you are going to be flooded with hundreds of new players and their bug reports ranging from not understanding the game to actual bugs.

[SpaceBikerV]

They've stated this since the early stages of the unstable release:
https://steamcommunity.com/app/494840/discussions/0/4327475407178230637/#c4327475407178239801

I'm personally not angry that i have to start over. That means more time to sink (pun not intended) into this game!

[Deerool]

Originally posted by Maffen:

What a wonderful community... Utterly incapable of reading a couple of sentences.
I come from a game dev and coding perspective. This is quite simply bad design. A flag has been set and thus people are losing all their progress for no reason at all. I didn't even lose that much myself tbh. But thinking of losing tens, maybe hundreds of hours of campaign progress just because the save game has been flagged as incompatible without that being necessary at all. Well as I said ... pissing off players for no reason. But I'm sure this has been too many sentences again... Not sure why I'm even trying tbh

I have a lot of sentence for you as well. Not sure if you read this.

Those who play the beta didn't lose any game or campaign progress. Cause they didn't play a full game. They tested a work in progress product that can change at any time during that process.

And you don't know nothing about it was neccessary or not to set the save games as incompatible cause you're not involved in the development process. You got no idea what the devs have changed from the last beta update to the full release version. It is not only those things that were written in the patch notes. There were many changes and adjusments besides these patchnotes.

The devs always said again and again and again that the beta version was an unstable and not reliable version. Every single update can break your old saves and they always highly recommended to start a new game after every single update. So whoever plays this beta knows this. If anybody was surprised now that his save games won't work anymore didn't read those developer statements very carefully.

There is no reason for complaing about losing time in a beta and that the beta version is not compatible with the full version.

[kimdownunder]

Originally posted by Maffen:

What a wonderful community... Utterly incapable of reading a couple of sentences.
(Snip) Not sure why I'm even trying tbh

Maffen, you are the one seemingly incapable of reading a couple of sentences, those being the VERY CLEAR WARNINGS that old game saves are not going to work. FFS, stop being a cry baby, read the notices and warnings, and just suck it up. From the reactions to your OP I don’t think you are going to get much sympathy hear, sunshine.

[Red_Seven_]

Personally I didn't have a single savegame in the beta that I played across more than 2 preview versions. The whole concept of the beta was to support with feedback and bug reports.

If you wanted to play a continuous career you should have played the latest stable (2022.1) version instead of the beta. Otherwise if you really intended to keep on playing the old career you could just stay with the latest beta patch and keep going. As you mentioned the updates with the full release weren't major changes so there's not even much you'd miss out on in that case.

[tequilatibbs]

Originally posted by Red_Seven_:

Personally I didn't have a single savegame in the beta that I played across more than 2 preview versions. The whole concept of the beta was to support with feedback and bug reports.

If you wanted to play a continuous career you should have played the latest stable (2022.1) version instead of the beta. Otherwise if you really intended to keep on playing the old career you could just stay with the latest beta patch and keep going. As you mentioned the updates with the full release weren't major changes so there's not even much you'd miss out on in that case.

+1

[Lord Haart]

Originally posted by XIIIOpsec:

Everyone who opted into playing the beta knew they were helping to test the game and find bugs, not start a game long career.

This.

[Maffen on Linux]

Originally posted by Deerool:

And you don't know nothing about it was neccessary or not to set the save games as incompatible cause you're not involved in the development process. You got no idea what the devs have changed from the last beta update to the full release version. It is not only those things that were written in the patch notes. There were many changes and adjusments besides these patchnotes.

Nonsense. You seem to have no idea how this stuff works. Let me try and explain. Preview version 27 was released on 31st of July. 2 days later they simply switched the version tag to "release Patch 1". Nothing substantial is happening in those types of situations for a very good reason. You release "alpha" revisions so you can make sure they are stable. Then you tag a release candidate and make sure that it is as stable as possible by waiting for reports to come in. Afterwards you literally don't wanna touch it anymore. At the very max only a couple of minor tweaks that don't risk stability. All that is happening afterwards is that you release that stable release candidate. The save files are absolutely compatible. Especially Preview 27 to Patch 1.

The ignorance in this thread is just as breath-taking as the toxicity.

Originally posted by Red_Seven_:

Personally I didn't have a single savegame in the beta that I played across more than 2 preview versions. The whole concept of the beta was to support with feedback and bug reports.

If you wanted to play a continuous career you should have played the latest stable (2022.1) version instead of the beta. Otherwise if you really intended to keep on playing the old career you could just stay with the latest beta patch and keep going. As you mentioned the updates with the full release weren't major changes so there's not even much you'd miss out on in that case.

Yeah that's actually what I did. I downgraded via download_depot to the last beta version. I wasn't expecting the game to force-switch me to another branch basically. That's why I left automatic updates on.

[The cursed Jäger]

Originally posted by Maffen:

I wasn't expecting the game to force-switch me to another branch basically. That's why I left automatic updates on.

That's how Steam works. It will auto-update you to the latest version, always, unless told not too. Welcome to Steam.

[maru]

Originally posted by Maffen:

The ignorance in this thread is just as breath-taking as the toxicity.

You are projecting your own inadequacies here.

Expecting savegame compatibility when it was specifically stated by the devs this would not be the case, is insane. This has already been pointed out to you in this thread, and when you respond to those factual comments with vitriol you aren't winning anyone over to your point of view.

If you really had any actual experience in the game dev industry, you would understand these basic realities. Seriously, stop lying to yourself, grow up, and move on.

[Noctover]

Originally posted by Maffen:

Just making old saves incompatible is a horrible way to go about this. I would have assumed the devs would adjust the saves to fix anything that is "messed up", but since this was an unstable branch I can understand that you don't want to put too much time into legacy code and such.
HOWEVER ... obviously you wouldn't simply lock out players. You should, when the player wants to load an 'incompatible' save file, quite simply display a warning in bold letters that loading an old game can lead to game-breaking bugs. Ignore all bug reports from players playing old save games, but just let them load it anyways. If it breaks, it breaks. I would assume it won't though. Why do I have a feeling that editing the save file will result in a perfectly playable game? There's no way the last Preview 27 and current Patch 1 are that different.
You're pissing off your players for no good reason.

Didn't piss me off. It was early access, beta etc. I paid less early on to be part of a buggy testing process. I don't think anyone with sense expected their saves to work upon full release.