Print

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

Dwarven Selection

113 (6.3%)

Wildlife

58 (3.2%)

Ambushes

154 (8.6%)

Sieges

207 (11.5%)

Undeads

118 (6.6%)

Forgotten Beasts

110 (6.1%)

Megabeasts

42 (2.3%)

The Circus

84 (4.7%)

FUN Spiral

286 (15.9%)

Dwarven Engineering

131 (7.3%)

FPS Death

395 (22%)

Other? (please specify)

97 (5.4%)

Total Members Voted: 878

[radialmonster]

so i have a pre 34.05 world that i'm carrying over into 34.05.  On subsequent phoebus preinstalled releases should I never run the save game updater now from now on? Or now that I have opened my world in 34.05 and saved it it will be ok to run the updater?

[Phoebus]

so i have a pre 34.05 world that i'm carrying over into 34.05.  On subsequent phoebus preinstalled releases should I never run the save game updater now from now on? Or now that I have opened my world in 34.05 and saved it it will be ok to run the updater?

Never update that savegame.
The DF savegame system is designed so you don't need to update.
The reason why I tell people to update is so they can benefit from improvements to the raws, such as new creature tiles or changes to tileset association in the raws.
It's just graphic improvements, nothing to ditch or break your fort over.

[krenshala]

Phoebus, I only see one bug report (#0005097) for this, so I'm going to add a link in that report in Mantis to your posts showing what is going on.

[nenjin]

If you guys want any other fonts, I do have this lovely Medici-type.....

Spoiler (click to show/hide)

 

Although I guess if you added BlackAdder for s's and g's......

Spoiler: MY EYES! (click to show/hide)

[Footkerchief]

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.

You may want to put this in the thread title temporarily or something.  A lot of people (not just in that thread) aren't reading the fine print, and are confused about why they're getting crashes after updating their save.

[crossmr]

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.

You may want to put this in the thread title temporarily or something.  A lot of people (not just in that thread) aren't reading the fine print, and are confused about why they're getting crashes after updating their save.

Toady wrote:

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.

Which seems to indicate they are compatible you just need to update that. Any idea how to update it?

[MaximumZero]

Spoiler: MY EYES! (click to show/hide)

That would be really cool...right up until you got past the title screen.

[Thief^]

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.

You may want to put this in the thread title temporarily or something.  A lot of people (not just in that thread) aren't reading the fine print, and are confused about why they're getting crashes after updating their save.

Toady wrote:

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.

Which seems to indicate they are compatible you just need to update that. Any idea how to update it?

There's a working fix in that thread. Update all raws, then copy the RCP_2_EYELIDS section and call the copy RCP_EYELIDS. Perhaps a pre-installed pack could be updated with this change made to the master raws? Then savegame updates would work fine.

[Phoebus]

Download body_rcp_eyelids.txt @MediaFire and copy the file in your 0.34.04 /save/regionX/raw/objects/
This will make the savegame permanently compatible with 0.34.05 (and most likely future DF versions too), and allow you to update that savegame to the latest raws without ever breaking that compatibility.

Do NOT copy that file to your main raws, doing so should not break anything, but it could make your new worlds dependant on both the 0.34.04 eyelids AND the 0.34.05 eyelids.

[Intrinsic]

PTW, my current tileset of choice. Thumbs up!

[Faulik]

I used ttf and now(at 05 version, pure install) and i get this:


Its not like vanishing a text, but its moved to left. And its not in the place of original number(without ttf). Other character are in their place.

Its like '10' simply become black. Any suggest?

[Musaab]

I get the weird spaced out text as well as the vanishing text with truetype on.  Not sure if there any choice but to wait to see if Toady takes a look at it.

[Footkerchief]

I used ttf and now(at 05 version, pure install) and i get this:


Its not like vanishing a text, but its moved to left. And its not in the place of original number(without ttf). Other character are in their place.

Its like '10' simply become black. Any suggest?

This bug, I think.

[Musaab]

This bug, I think.

That looks about right.

[crossmr]

Ok, I've found why you're getting so much vanishing text.
When the TTF engine writes text, it reserves and draws over an area of the screen equal to the size of the text if it was drawn without TTF.
If that area overlaps text on the right, the text on the right vanishes.

Something doesn't make sense to me about this..
I would understand it blocking out stuff at the end of a line because of this..
but I don't understand how this makes sense when it blocks out the middle of a word like:
The goblin lasher at  cks th militia commander
Are you telling me the at is something taking up the space of the following ta, or the "th" is somehow taking up the space of the e? Why isn't any part of the commander word missing or goblin?
Why does "The goblin lasher" appear fine on that line, but on another line appear as:
"the goblin las  r" shouldn't those be drawn consistently the same?