Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Yes and it makes me sad

81 (39.7%)

Yes and it makes me mad/angry/frusrated

29 (14.2%)

Yes and it's okay because there are other versions now

94 (46.1%)

Total Members Voted: 204

[Bohemian Ear Spoon]

Thanks for answering my question about using stonesense with LNP 34.02.  I havent been able to get dfhack working with LNP.  In the past I have always just used vanilla LNP but I really need to visualize this 34.02 fort

[RabblerouserGT]

@RabblerouserGT You will have to continue typing and clicking.

Okies.



And what all has changed since .02? Sorry, I'm fairly new to the game.

[HiEv]

And what all has changed since .02? Sorry, I'm fairly new to the game.

You can see the changes to Dwarf Fortress in the change log page at the bug tracker or just read the "release notes.txt" and "file changes.txt" files that come with the game.

If you're asking about changes to the Lazy Newb Pack, it's hidden in a spoiler in the first post in this thread.

[WCG]

why someone would use 34.02 instead of 34.03 or 34.04, which do work with the latest dfhack is beyond me

edit: oh right, playing a 34.02 generated fort is only possible in 34.02

Oops! Is that true? If so, I misunderstood things and might have screwed up my game.

While waiting for the next LNP, I'm playing DF bundled with the Phoebus tileset. I was warned not to update my saved games when using 34.05, but I thought it was OK for 34.04 and earlier.

At any rate, my fort was started in 34.02.  Yesterday, I installed 34.04 and updated my saved games. Then, I installed 34.05 and copied my saved games to that, without updating them.

That seemed to work. I mean, I played for a few hours yesterday, without any problems. Is that going to give me problems later, though?

Note that, for me, the instructions with these things aren't always easy to understand. "Updating the raws," for example, might be perfectly obvious for most of you, but might not be as obvious to some of us who don't play the game as often. And I don't pay such close attention to every update.

I don't have as much time as I'd like to play the game, so I don't want to keep starting over with a new fort, if I don't have to. I'm hoping that I don't have to. 

[HiEv]

why someone would use 34.02 instead of 34.03 or 34.04, which do work with the latest dfhack is beyond me

edit: oh right, playing a 34.02 generated fort is only possible in 34.02

Oops! Is that true? If so, I misunderstood things and might have screwed up my game.

No, that's not true.  He's mixing up v0.34.01 with v0.34.02.

v0.34.01 saves can only be played with v0.34.01.

v0.34.02+ saves can be played with the latest Dwarf Fortress v0.34.x.  However, it should be noted that the worlds you generate in earlier versions may have some problems (for example, creatures that should be benign causing dwarves to panic, ghost vampires/necromancers/werecreatures, conflicting civilization memberships which can lead to bizarre riots in adventure mode, etc.) that are fixed in the latest version.  Also, a problem with save corruption was fixed in v0.34.03, so earlier saves may suffer from various oddities due to that problem (cave-ins on embark, etc.).

[MoloMowChow]

why someone would use 34.02 instead of 34.03 or 34.04, which do work with the latest dfhack is beyond me

edit: oh right, playing a 34.02 generated fort is only possible in 34.02

Oops! Is that true? If so, I misunderstood things and might have screwed up my game.

No, that's not true.  He's mixing up v0.34.01 with v0.34.02.

v0.34.01 saves can only be played with v0.34.01.

v0.34.02+ saves can be played with the latest Dwarf Fortress v0.34.x.  However, it should be noted that the worlds you generate in earlier versions may have some problems (for example, creatures that should be benign causing dwarves to panic, ghost vampires/necromancers/werecreatures, conflicting civilization memberships which can lead to bizarre riots in adventure mode, etc.) that are fixed in the latest version.  Also, a problem with save corruption was fixed in v0.34.03, so earlier saves may suffer from various oddities due to that problem (cave-ins on embark, etc.).

That's a shame. I kind of want to stick with one world and see how far I can take it until it becomes an Age of Emptiness or something.

[RabblerouserGT]

So playing a 34.02 world in 34.05 will be buggy.

What if I reclaim my 32.02 fort? Will it still have the same issues?

[Ghizz]

yay update for 34.05 coming soon

[TolyK]

So playing a 34.02 world in 34.05 will be buggy.

What if I reclaim my 32.02 fort? Will it still have the same issues?

Probably, as it's *world* corruption and not save corruption. :/

[RabblerouserGT]

So playing a 34.02 world in 34.05 will be buggy.

What if I reclaim my 32.02 fort? Will it still have the same issues?

Probably, as it's *world* corruption and not save corruption. :/

Ah. I just assumed it was an issue with the way dwarves were modeled and that starting a new save would give you a world with fresh newly generated properly-modeled dwarves.

Oh, well.

[WCG]

OK, so it's not actually saved game corruption, which was only a problem with 34.01, but fixed in 34.02 and later. So I guess I'll continue playing my fort which I started in 34.02, as long as it works OK.

But I do have a question about the info here under "HELP: Moving saves over to a new version."

It says, "To upgrade saves to latest version, open the new version's GUI, go to the Graphics tab, and install an updated graphics pack. Or just press Update Savegames if you don't want to use/update graphics."

But what if I'm already playing the game with the graphics I want? If I just want to use the Lazy Newb Pack, can I simply move the saves and play the game without updating anything? I'll still have the graphics OK, won't I? Or isn't that how this works?

As I said, I don't know much about this.   

[Taverius]

You should update the graphics pack for that version of DF as well as DF itself, and press update, so that the raws and gfx are updated to what's required to that version.

Check what's in the directories though, because for example Mayday graphics only pack requires you to add a few files from the default df gfx (mouse.png, the font, a few others.)

[BlackGyver]

Release LNP for 0.34.05 today, and I'll shave my beard.

Edit: Okay, release it today, and I'll shave my beard PLUS give you my firstborn.

[WCG]

You should update the graphics pack for that version of DF as well as DF itself, and press update, so that the raws and gfx are updated to what's required to that version.

Well, on the Phoebus' Graphics Set thread...

http://www.bay12forums.com/smf/index.php?topic=57557.0

... it says:

   DF 0.34.05 raws are not compatible with worlds generated with DF 0.34.04 or earlier
   If you want to use your old savegames in 0.34.05, do NOT update your savegame raws.

So that's why I was asking. But I don't know if this is just an issue with the Phoebus tileset or not. (If I understand it correctly, the problem has to do with the body_rcp_eyelids.txt, but there's always a lot of info in this message board, not all of it accurate.)

Right now, while waiting for the LNP update, I'm playing 34.05 with the Phoebus tileset, but I only updated the raws to 34.04. I was hoping I could continue playing with the LNP, once that is released.

[RabblerouserGT]

The eyelid issue?
From the main Bay 12 DF page:

Note that any old vanilla saves you move over will have a short error log on load for their broken eyelid raws. This isn't a big deal, and you can either update the body detail plan file or just leave it. New saves won't have this problem.

Makes it sound like you can still play just fine regardless.


Still creating a new world, though.

Also, if LNP 0.34.5 is released today, I will eat my own hair.