Print

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

[KFK]

Fortress layout can have a huge impact on framerate. I've found large, centralized living quarters (resembling hotels, apartments, or even dungeons) extremely inefficient from a CPU perspective. Instead, try to have a bedroom and dining area near a dwarf's work space, and build self contained clusters. Every step a dwarf has to take shaves a little off your FPS, and even a modest fort can become unplayably slow if too many dwarfs need to move too much of the time.

Same goes for animals: cage any animal you're not using for milk or breeding. You only need one cage.

In the big picture, a few more frames per second will add more to your overall experience than temperature and weather. I second turning them off if you find it makes a difference.

[FuzzyDoom]

@FuzzyDoom: in .04, the init setting has changed to [PRINT_MODE:PARTIAL:2]

Tried it, but it had no effect. Oh well, I'm fine with .03.

[0x517A5D]

One thing not mentioned yet is controlling pathing using traffic designations.  I have read claims that restricting (d-o-r) seldom-used large areas can speed up pathfinding.

My own experiments weren't conclusive, however.  (Not that I spent too much effort looking at the before-and-after.)

I'm pretty sure that the game uses a two-level hybrid path system using precomputed connectivity tests between the 16x16 blocks to filter out dead-ends before needing to resort to the A* algorithm or whatever it uses to find the actual path.  So manually-placed restrictions might not be very useful in practice.

Anyone know better?