Print

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

[Cozmopolit]

On a 2007 Macbook running Linux I have to do a lot of management to keep FPS acceptable - I usually run/like about 70-100 FPS, if it drops below 30 I declare my fortresses FPS-dead.

I have temperature and weather turned off and keep the amount of dwarfs way down to achieve that (FPS dead according to above definition occurs usually at around 150-200 dwarfs).

My FPS limit is at 200, more is too fast for me.

[Mageziya]

I have absolutely no fudging idea....

I need to enable the framerate counter.

[Asra]

I think anything over 30 is acceptable, without having anything like temperature off or mass burning of items. That's at about 100 dwarfs or more.

[i2amroy]

I usually start around 200 depending on what is present in the fortress as well as how big the area is, and then it drops from there. Personally I used to not like it once it got below 70 or so, but then I realized the secret to running large fortresses... multitasking. On most computers you actually have more getting done in your fortress with more dwarves causing a slowdown in FPS ([20 dwarves]x[200 FPS]=[4000 work] compared to [200 dwarves]x[30 FPS]=[6000 work]), the problem is just that each individual task usually has the same amount of dwarves on it, so it seems like it's going slower. If you work on multiple projects simultaneously or the types of projects that can harness large amounts of dwarves at the same time (such as megaconstructions with lots of buildings to do), then it can "trick" your brain into taking into account the FPS slowdown and things will seem like they are going the same speed, or even faster then they were when you had less dwarves but more FPS.