Print

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

[Newbunkle]

The stone list seems to have shrunk considerably. Without the ability to filter out sandstone and force them to use shale, my furniture will not be in matching colours. The horror!

[Rafal99]

Just a quick question, which files did actually change from 34.1 to 34.2 ?

There are tools to easily find what files changed between two folders, and then merge/copy changes you want.
Personally I use WinMerge, compare new DF folder with old one, and then merge my custom changes (usually init params and worldgen params) to the folder with new DF.
Takes about 3 minutes and I have all my changes copied.

The stone list seems to have shrunk considerably. Without the ability to filter out sandstone and force them to use shale, my furniture will not be in matching colours. The horror!

I kinda liked the extended (z)->stones list containing all stone types. You could easily force your masons to use only a certain stone.
But the list was getting very long so having it fixed is actually a good thing.

[Kordanor]

Thanks for the update.

I am not sure if you tried to speed up world generation by any of these changes.
However with the new build it is still not possible to creat large worlds with much more than 250 years of history.
Not just that it takes very long until it would be finished, the game still uses about 4-5MB for each year of history (in the beginning). So without the memory change thingy it will never survive that.
Besides of that after year 150 for every additional ~ 10 years the calculation generation time for an additional year increases by 50%, reaching 10 minutes for my machine at year 190 to 200, and 16 minutes from 200 to 210. If I am not wrong that would make some billion real life years to calculate the 1050 year history. So...if it's not possible to speed up this process I would suggest to disable the option to use Very Long and Long (still some hundred years of calculation) for the world generation with big worlds as it's also quite hard to stop the process once it takes several minutes per year to load.

[NewsMuffin]

Would it be possible for me to mod the swarms of giant mosquitoes back in, or was that hardcoded?

[abadidea]

So when you say wagons are back in, you mean the caravans will arrive by wagon instead of by donkeyback again?

This actually hampers my security methods, oh well 

[Isher]

I am at year 476! Only 74 more to go.

[Wirevix]

Would it be possible for me to mod the swarms of giant mosquitoes back in, or was that hardcoded?

You can go to their raw and change the cluster number tag to a much higher number if you like.

[Footkerchief]

They don't collapse, I don't think, so they'd probably need to be beheaded if they have heads or bifurcated and otherwise you are in trouble.  The pulping calls again.

There's a bug report about invincible husks, although I think the reporter might not have been using any edged weapons.

Pulping is a feature I can't get soon enough.  I miss the 40d days of "It is smashed into the body, an unrecognizable mass!"  Rotten-ness should make the tissue materials more squishy, to facilitate the smashing of zombie heads.

[Orkel]

They don't collapse, I don't think, so they'd probably need to be beheaded if they have heads or bifurcated and otherwise you are in trouble.  The pulping calls again.

There's a bug report about invincible husks, although I think the reporter might not have been using any edged weapons.

Pulping is a feature I can't get soon enough.  I miss the 40d days of "It is smashed into the body, an unrecognizable mass!"  Rotten-ness should make the tissue materials more squishy, to facilitate the smashing of zombie heads.

Yeah, I agree. I'd be glad for even a hotfix for the current unkillable zombie problem. Giving each undead a couple of resurrections after which they don't get up anymore would be the best solution and probably wouldn't be too hard to code in.

[Babylon]

Would it be possible for me to mod the swarms of giant mosquitoes back in, or was that hardcoded?

Shouldn't be too hard, just change the values attached to the CLUSTER_NUMBER tag.

[Angel-of-Dusk]

They don't collapse, I don't think, so they'd probably need to be beheaded if they have heads or bifurcated and otherwise you are in trouble.  The pulping calls again.

There's a bug report about invincible husks, although I think the reporter might not have been using any edged weapons.

Pulping is a feature I can't get soon enough.  I miss the 40d days of "It is smashed into the body, an unrecognizable mass!"  Rotten-ness should make the tissue materials more squishy, to facilitate the smashing of zombie heads.

Yeah, I agree. I'd be glad for even a hotfix for the current unkillable zombie problem. Giving each undead a couple of resurrections after which they don't get up anymore would be the best solution and probably wouldn't be too hard to code in.

Honnestly, I'd be alot more happy with a belly full of- er

I'd prefer they keep there ressurection status, because there just is no more "true" undead in lore/games these days,  but they need to be tweaked at speed, so corpses can be managed.

[Eoganachta]

Thanks again Toady.

Thanks for the update.

I am not sure if you tried to speed up world generation by any of these changes.
However with the new build it is still not possible to creat large worlds with much more than 250 years of history.
Not just that it takes very long until it would be finished, the game still uses about 4-5MB for each year of history (in the beginning). So without the memory change thingy it will never survive that.
Besides of that after year 150 for every additional ~ 10 years the calculation generation time for an additional year increases by 50%, reaching 10 minutes for my machine at year 190 to 200, and 16 minutes from 200 to 210. If I am not wrong that would make some billion real life years to calculate the 1050 year history. So...if it's not possible to speed up this process I would suggest to disable the option to use Very Long and Long (still some hundred years of calculation) for the world generation with big worlds as it's also quite hard to stop the process once it takes several minutes per year to load.

This. While I don't normally gen 1050 large worlds due to hardware constraints I could easily manage 250 large worlds very smoothly in 31.25.  However I don't know if this is just because the game is tracking so many more characters in so much more detail for the historical migrants feature.

[Zerkuron1]

The stone list seems to have shrunk considerably. Without the ability to filter out sandstone and force them to use shale, my furniture will not be in matching colours. The horror!

I kinda liked the extended (z)->stones list containing all stone types. You could easily force your masons to use only a certain stone.
But the list was getting very long so having it fixed is actually a good thing.

Toady I miss the easy "other stones" management while they were shown in the stones section. On the other hand i can understand why some people think this list becomes confusing.

Could you divide the stone section in Economical, Non Economical and Ores? In this way it stays clean and clear and we have an easier life in control our masons and stonecrafter. I think this would change the whole stone management in a user-friendly way. I know this is Dwarf Fortress and user friendly interfaces are bugs, but I would appreciate this change.

[Isher]

I am at year 476! Only 74 more to go.

The last 74 years took until this post - dual 3.0 with 1mb cache (way overclocked to get to 3.0).

I don't mind the amount of time but i can't imagine going to 1050.

528,635 historical figures
511,407 dead
4,888,642 events

Not bad for that amount of complexity.

Minute to minute and a half per year, it slowed down but the years seemed to pass with regularity past a certain point (rather than getting exponentially longer).

[knutor]

Thanks for the fixes.  Cannot wait to try um out.  Sincerely, Knutor