Print

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

[mirrizin]

So, here's my situation. I've got what I think of as a late-stage fort. It just lost about half of its population (200, and then another 100 or so guests.) A dwarf contracted lycanthropy, and so I solved the problem with a militia hit. This led to a loyalty cascade that wiped out over 100 dwarves in relatively short time. Thanks to strange priorities and the usual, these were not buried immediately, and so the fort, which ahd previously been running at a tolerable 16 or so FPS, is running at zero. Things are moving, but at a rate that is incredibly slow.

I don't quite wish to quit, yet. I'd like to tie off a few things, satisfy my internal perfectionist, etc. But I don't want to have to sit and watch as it sluggishly calculates the exact position of every miasma cloud.

Would it be possible to set up a mode that would temporarily switch off the visual interface or non-priority events in the interest of speed? Say...run X clicks unless an interrupting event occurs?

[Bumber]

Typically it's the pathfinding that slows the game down, which you're not going to get anything done without. If your problem is miasma, you can dump all the corpses outside where they won't produce it, or atomsmash and engrave slab. It probably requires DFHack autodump for you at this point.

[mirrizin]

Typically it's the pathfinding that slows the game down, which you're not going to get anything done without. If your problem is miasma, you can dump all the corpses outside where they won't produce it, or atomsmash and engrave slab. It probably requires DFHack autodump for you at this point.

I gave up on the game. Problem with non-automated methods would be they'd still take days (I guess) of real time just to dump five corpses between dwarven priorities (they seem to prefer grabbing clothing to dealing with bodies or coffins) and the general atmosphere of lag.

If I'd intended to keep the game at all costs, I think what I'd have done was let it run passively and check it every half hour or so until the FPS went up again (whenever that happened?). I just decided that it wasn't worth it.

I imagine DFHack would have a better solution, but to my knowledge it's not flush with the latest version yet.

[Libash_Thunderhead]

Yeah, you have too many units.
It appears you have a better CPU but it doesn't means it can take that much.
The default population settings (200 dwarves) are already outdated.

[Diamond]

That's why I built a contraption to flood entire fortress with magma (except safe room, which is obsidianized at entrance instead) and then drain it.
Used it more times than I expected to as well.

[mirrizin]

Yeah, you have too many units.
It appears you have a better CPU but it doesn't means it can take that much.
The default population settings (200 dwarves) are already outdated.

Yes, I have a pretty powerful machine, and yes, I need to mod down the population cap, as well as the guest cap.

Did I mention that this fort was harboring something like 100 guests?

[mirrizin]

That's why I built a contraption to flood entire fortress with magma (except safe room, which is obsidianized at entrance instead) and then drain it.
Used it more times than I expected to as well.

Hmm. Yes. I'm usually a more sympathetic player far as the dorfs are concerned, but I do see the appeal. And magma means no bodies to fill the fort with time-consuming rot.