Bay 12 Games Forum

Please login or register.

Login with username, password and session length
Advanced search  

Author Topic: 0.31.25 Save To 0.34.05  (Read 1006 times)

kardofaces

  • Bay Watcher
    • View Profile
0.31.25 Save To 0.34.05
« on: March 20, 2012, 12:41:28 am »
Can anyone tell me if I can get my previous version save to work in 0.34.05 - nothing shows up. Is there a way to make it work or at least use the map? Or are they just incompatible.

Edit: From what I read they are unsalvagable. I'm worried that if I start a fortress now, I wont be able to use my save when Toady fixes clothing and releases that update.
« Last Edit: March 20, 2012, 12:51:22 am by kardofaces »
Logged

Silophant

  • Bay Watcher
    • View Profile
Re: 0.31.25 Save To 0.34.05
« Reply #1 on: March 20, 2012, 01:23:57 am »
Generally, major updates (like .31 to .34) break saves. In addition, I believe the .34.03 update broke previous saves as well, to fix a memory leak. However. you're usually okay with transferring a minor version to a newer one, albeit usually not gaining some or all of the new features. If you start a fortress in the current version, you'll be able to transfer it to .34.06 when it's released, but some of the fixes won't take effect until you generate a new world.
Logged

Telgin

  • Bay Watcher
  • Professional Programmer
    • View Profile
Re: 0.31.25 Save To 0.34.05
« Reply #2 on: March 20, 2012, 11:28:13 am »
The structure of a few things (maybe a lot) changed between .31 and .34, such as the addition of disguises, were creature curses, and secrets.  In theory it would be possible to write a tool that took a .31 save and made it .34 compatible, but I don't think anyone understands the data structures well enough to do this reliably.  It would probably be a crashy, buggy mess.  And a heck of a lot of work.

That said, Toady said that he hopes that minor versions won't break save compatibility for a while now, so you'll probably be fine if you want to go ahead and start a .34 fort and later upgrade to .34.06 with its promising new bug fixes.
Logged
Through pain, I find wisdom.

BigD145

  • Bay Watcher
    • View Profile
Re: 0.31.25 Save To 0.34.05
« Reply #3 on: March 20, 2012, 12:42:24 pm »
I know Toady tries but every new thing he adds, and there are lots more to come, breaks the saves.
Logged

HiEv

  • Bay Watcher
  • Denizen of Counter-Earth
    • View Profile
Re: 0.31.25 Save To 0.34.05
« Reply #4 on: March 20, 2012, 03:23:48 pm »
Quote from: Silophant on March 20, 2012, 01:23:57 am
In addition, I believe the .34.03 update broke previous saves as well, to fix a memory leak.
Mostly right except for this bit I quoted.  It was v0.34.02 that broke compatibility with with v0.34.01, and it was to fix a save corruption problem.

The v0.34.03 to v0.34.05 releases have all been backwards compatible with v0.34.02+, despite the fixes and new features.  The next version will probably be backwards compatible with v0.34.02+ as well.
« Last Edit: March 20, 2012, 03:28:41 pm by HiEv »
Logged
The difference between intelligence and stupidity is that intelligence has its limits.

Silophant

  • Bay Watcher
    • View Profile
Re: 0.31.25 Save To 0.34.05
« Reply #5 on: March 20, 2012, 07:53:22 pm »
That'll teach me to work from memory. Thanks.
Logged

Mungrul

  • Bay Watcher
  • Shambolic
    • View Profile
Re: 0.31.25 Save To 0.34.05
« Reply #6 on: March 22, 2012, 04:28:38 am »
I tried moving from 34.02 to 34.05 last night and it didn't work; whenever I started loading my fortress, I'd get an RCP_eyelids error relating to the body objects raw and the game would CTD.
Even though I've been playing for about 4 years now, this is the first time I've tried to transfer a save between versions, so I'm a complete newb to the method. What should I be copying into my save folder to make it compatible? I tried the obvious one, the body objects raw, but no joy. I'm wondering if I grabbed the right one.
Sorry for the semi-hijack!
Logged

BigD145

  • Bay Watcher
    • View Profile
Re: 0.31.25 Save To 0.34.05
« Reply #7 on: March 22, 2012, 12:16:52 pm »
Search for that exact error. I know there's a fix somewhere.
Logged