Print

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

[MorsDux]

Thanks for the insight! My fort is around 15 years old with 400 inhabitants. Im losing Fps year by year.
Maybe i can mod out masterworks? In a new world? Would that help? The fort made around 70,000 masterwork items 95% of which was useless like cloth food and crafts related.

[PatrikLundell]

I've noticed that butchered animals no longer appear on my fortress' list of the dead. Has this helped?

You're probably using DFHack's fix/dead-units script, in which case they do appear but are removed every time the script is run, which seems to be set to once per month. Apart from a bug fixed recently (it was a bit too enthusiastic in removing units), it probably helps a little bit. Note that units aren't actually deleted: they're removed from the "active" list and DF causes them to appear in the "bad" list, while the "all" list still contains all of them. One would assume DF performs regular processing of the "active" list only, though.

:
Too bad there is no dfhack command to purge these tables.
:

If DF actually does delete item smashed items (I haven't checked), then it ought to be possible to write a script to purge exported junk (you may still want to export junk to increase the exported value number), but it should be investigated where all the junk ends up. If they show up in large piles in adventure mode, that ought to mean they are stored in an item inventory structure in the caravan sending fortress, and if you delete the item in the item list you ought to also delete references to it at the (new) owner site.

[Grand Sage]

Ok, Im just putting this out there MorsDux, If you increased your cap to 400, everything that happens from there on is entirely on you. A 400 dwarf fort is awesome, no doubt, just saying... fps wise... well, you better have a good pc

Kinda flattered you saw my post Sethatos Indead, you seam to have mastered the art of playing this game at low fps

I dont think so.

I Actually believe that items carried of by merchants are no longer recorded anywhere. there value adds to exported wealth and the civ screen, but unless they are artefacts or otherwise historically important, they should not be tracked anywhere. unless it is needed for giving the next item an id, but that would apply to atomsmashing as well.

[wierd]

Needs science.  Toady did a lot of updates to trading and "world activation" since the cited research was conducted.

Is there a reliable way to iterate the total size of the item vector from dfhack? (Basically just walk the table, and give a numeric value for num_entries?)

With a quick test tool like that, I could use createitems to spawn shitloads of something directly on the depot, then trade them. I could then wait for the traders to leave, and then check again to see if the vector shrank or not.

[PatrikLundell]

Needs science.  Toady did a lot of updates to trading and "world activation" since the cited research was conducted.

Is there a reliable way to iterate the total size of the item vector from dfhack? (Basically just walk the table, and give a numeric value for num_entries?)

With a quick test tool like that, I could use createitems to spawn shitloads of something directly on the depot, then trade them. I could then wait for the traders to leave, and then check again to see if the vector shrank or not.

You can query the vector about its length with #whatever_the_vector_is_called in Lua. You can also iterate over it, although you'd have to know what a dud element looks like to recognize it if DF just marks items as dud. I've seen that you can destroy items by setting a flag in them, after which DF will catch that and destroy the item. I just tried it (I have a web_buster script), and the items destroyed are removed from the "all" vector (I haven't checked the category vectors, but assume the items are removed from them as well). However, the "bad" vector did not shrink (and I found a web item in there). It's possible this vector is cleaned up when a save is loaded, though (or possibly at long intervals), as I've seen that the units.all and units.bad vectors start out the same length on a load, even if fix/dead-units had culled units before the save (so they had different lengths at that time).

A trade experiment would be useful, though. I'll see if I can find a way to investigate it from the state of the items vectors, though.

Edit: Since I trade away worn masterworks clothing, there should be enormous amounts "out there" after 30+ years. I iterated over all items in the "all" vector, and came up with 7 worn masterworks "item_helmst", not the hundreds (or thousands) of caps and hoods traded away, so they're most probably removed from the fortress, but they may well contribute to the save game size explosion...

[CyberianK]

So if I understand everyone correctly for starting a fortress that does not die performance death I should:

Embark 1x1
Small+young world
Limit Caverns
No trees
Don't build stairs
pop below 50
no sieges
don't produce rotting clothes
destroy all excess items
don't mess with water
don't dig out much
no animals

Forgot anything? Maybe I try playing this game again maybe it can still be fun with the outside raids and such but those above measures drastically reduce the fun in a fortress.

[PatrikLundell]

Your fortress will probably succumb eventually anyway (unless your tolerance FPS limit is down to a crippled hand level): it's just a matter how long it takes.

Visitors path around, so you'd probably want to limit the number of those.

[bloop_bleep]

Listen, there's nothing you can do to prevent FPS from dropping to something like 50 for any decently long-lived fort. You might try to stop it from dropping even further, but trying to keep it above 50 is just futile.

[Leonidas]

What about buildings? Am I killing my FPS by putting hatches everywhere?

[Grand Sage]

I dont belive so. Sure, the game will need to perform temperature checks ect. on them, but it should be insignificant compared to the 100000 other tiles it is already checking.

[Robsoie]

About amount of items going insane.
Beware of fisherdwarves, only 4 or 5 of them can result in several thousands of mussels items every few months
And if you have a fishery workshop, several thousands of mussel shells.
So make sure to disable fishing on most of the fishers when you start to see them getting mussels if you don't want to have to constantly haul and atom smash so many items.

[Dragonborn]

Another thing to keep in mind: All the tweaks that are recommended here mean little if you're trying to play the game on low end hardware or a laptop.

[wierd]

Another thing to keep in mind: All the tweaks that are recommended here mean little if you're trying to play the game on low end hardware or a laptop.

Hey, my crappy linux-ized chromebook is able to handle the game quite well, all things considered.  I still get 12ish FPS with 150 dwarves on a default size embark.

[§k]

Above ground buildings - consisting of thousands of blocks - definitely stress the FPS, even the small ones.

[Robsoie]

Embark 1x1

You can go with 2x2 , it's larger enough for a decent fortress and you should be able to keep the framerate above 50+ for a decade or two without problem at 100 pop as i do on my current fort (assuming of course you use the other fps controlling tricks) on an old computer :


turning off siege is a problem to me as it introduce boredom very quick , mostly because unless you make your own self challenge rules in current and default gameplay it's too easy to get your fortress to be self sufficient in only a few months on your first fortress year (and that will still continue to be self sufficient even when you'll reach your max pop).

I usually only turn off siege temporarly so my dwarves can have enough time to haul all the useless items generated by defeating a siege into my atom smasher (as it can take a very lot of time when you're not using dfhack for its autodump destroy script) before the next siege

An additional benefit to have a 2x2 ( 1x1 ) map with siege enabled, is that it actually increase the siege challenge, because the invaders spawn so close to your fortress that your dwarves will have less time to prepare for them (assuming you jusy simply didn't walled/roofed your fortress completely.