Page 1 of 1
2.3.2 not compatible with older versions' saves?
Posted: Wed Feb 01, 2017 8:30
by MagicWazard
Before I wrote up a formal bug on Mantis, I just wanted to ask if it was intentional behavior that GZDoom 2.3.2 wasn't compatible with saves from older versions (such as 2.1.0).
Re: 2.3.2 not compatible with older versions' saves?
Posted: Wed Feb 01, 2017 9:52
by Rachael
Correct. The savegame code was rewritten recently, so old saves will not work.
Re: 2.3.2 not compatible with older versions' saves?
Posted: Wed Feb 01, 2017 12:05
by Graf Zahl
For the record, 2.4 will also break savegame compatibility, because there have been many changes already which move some saved values to different places. I won't bump savegame versions for the devbuilds, though, only for the final release. Although most savegames MIGHT still work I'm not going to risk it for an official version that all these changes may result in bugs.
Re: 2.3.2 not compatible with older versions' saves?
Posted: Wed Feb 01, 2017 12:34
by Enjay
Given that there have been a lot of quite important changes*, does this have an impact on the release schedule? i.e. do all the changes mean that 2.4 will be released sooner than originally anticipated, later or pretty much as you intended? I'm not nagging in any way; I'm just interested to find out what the impact on changes of this type are likely to have.
*Although I don't claim to understand the detail of all the changes, it's clear that there is a lot going on and that a lot of areas of the code are being made more logical and robust. It's interesting stuff to watch.
Re: 2.3.2 not compatible with older versions' saves?
Posted: Wed Feb 01, 2017 14:52
by Graf Zahl
2.4 will be released when I consider the amount of new features sufficient and the engine has gone through a testin period with no new critical bugs being reported. I wish it could be sooner but I am a bit busy with work right now so I haven't even started with the statusbar stuff I'd really want to have ready for 2.4.
Re: 2.3.2 not compatible with older versions' saves?
Posted: Wed Feb 01, 2017 18:39
by Rachael
Speaking of version bumps - with QZDoom releases, up until recently I have been bumping NETGAMEVERSION. Mostly because of what it says here: (version.h)
Code: Select all
// Version identifier for network games.
// Bump it every time you do a release unless you're certain you
// didn't change anything that will affect sync.
#define NETGAMEVERSION 235
Re: 2.3.2 not compatible with older versions' saves?
Posted: Sun Feb 05, 2017 4:19
by Nash
Graf Zahl wrote:For the record, 2.4 will also break savegame compatibility, because there have been many changes already which move some saved values to different places
What does it mean when you "move saved values to different places"? The deserializer can't handle new serialized variables being added into the save file?
Re: 2.3.2 not compatible with older versions' saves?
Posted: Sun Feb 05, 2017 10:16
by Graf Zahl
For scripting some variables have been moved into the script code, using the automatic serializer which saves them under different names. For my internal testing I can live with that but in an official release it'd only generate bug reports, especially if I also do this for a large quantity of Actor's own serializable properties, which I eventually plan. Implicit serializazion is a lot less susceptible to errors than explicit one.