Hi Christoph, > > Which version of ALSA is best to use to test this? 0.5 or 0.9? > > Savegame issues are independant of the sfx driver, so this shouldn't > matter. It seems to work after your latest update, BTW- thanks!
Thank goodness for that! I was just wondering which is the 'better' version of ALSA to install ATM, if you know. > > The new save game version is now in (with may even fix the problem), but I > > was unable to determine any substantial difference between your copy of > > sfx_save.c and mine (just a slightly different variable name). Did I miss > > something? > > A differently named variable (in one of the cfsml records) can indeed > break savegames, since the variable name is used as the 'name' part of the > name/value pair stored in the file. Variables that were _not_ set are not > tracked, so restoring a record (foo, bar) after having saved a record > (_foo, bar) would leave 'foo' uninitialized. > (One of these days, this should be improved, of course...) That's certainly something I'm glad to know. Perhaps this should be documented somewhere if it isn't already? Sorry for not explaining myself properly, but what I actually meant was regarding the CVS commit containing the new save game version. CVS picked up a conflict in sfx_save.c but because the version I was submitting was so different, whatever change you previously made to that file may not be in the new copy. Alex.
