Print

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

[smigenboger]

It has been said somewhere that the liquid 'molten rock' will disappear from the game, but will still be counted for, so melting stone will not change your fps.

For the massive items test, you could make the elves pack 20 times their usual caravan, drown them in the depot, and see if the massive dip in fps stays due to the items.

[moosecow]

Another factor I thought of was perhaps the rampant amount of trees growing might have an impact? Or is there a set limit of how many trees will spawn? [I don't cut them down at all typically]

[Retro]

It has been said somewhere that the liquid 'molten rock' will disappear from the game, but will still be counted for, so melting stone will not change your fps.

Sort of - there's a bug where objects getting pushed around (presumably as they change state as it seems to only happen with magma) disappear from the DF universe but remain tracked forever. If you want stuff to melt it's best to drop it into a steady body of magma. Of course, FPS barely changes with amounts less than 50k-100k objects getting deleted so it's really not worth the effort to do.

[forsaken1111]

As far as I can see, stone removal is an aesthetic choice, not a real FPS improvement.

[Bartleby]

deleted

[darkflagrance]

In the latest version, could stuff be happening in the caverns that eventually cause the fort to grind to a halt?

[Retro]

In the latest version, could stuff be happening in the caverns that eventually cause the fort to grind to a halt?

Quite likely. Most people report that sealing the caverns from the rest of the fort reverses a lot of the initial FPS drop you get from opening them. Dunno any particulars though.

[Zavior]

In the latest version, could stuff be happening in the caverns that eventually cause the fort to grind to a halt?

Quite likely. Most people report that sealing the caverns from the rest of the fort reverses a lot of the initial FPS drop you get from opening them. Dunno any particulars though.

Just like ambushes, maybe there are few GCS lurking around eating your fps away...

[katyrnyn]

In the latest version, could stuff be happening in the caverns that eventually cause the fort to grind to a halt?

Quite likely. Most people report that sealing the caverns from the rest of the fort reverses a lot of the initial FPS drop you get from opening them. Dunno any particulars though.

Just like ambushes, maybe there are few GCS lurking around eating your fps away...

This is possibly part of my problem, as there is at least one GCS in the second cavern (and an endless herd of crundles).  Unsealing causes an immediate drop in FPS, sealing it back up reclaims most of it.  But that's not the what's causing the progressive drain over time as the critters are always there.

[ghosteh]

I just leave the FPS counter off. If I do not see it I do not get warning about ambushes or kobolds, so they are more of a surprise. Things get done when they get done.

 I agree the stone bit is not correct, I've had over 100,000 stone in stock on some forts and did not notice speed issues. I wonder if atom smashing isn't just hiding the objects if the FPS got worse.

I agree with leaving it off, if I don't see the counter, I don't actually worry about the FPS, it only bothers me when I can see it

[Luewen82]

Hmmm. So what i dig up in here tells that if i use stone to do something like decorate floors with stones it wont eat up fps? As i normally like to decorate stone tiles before i put workshops etc over them for better looks. Though every single floor tile i have made shows in building list.

[Jurph]

OP, if you have not yet designated high-traffic areas to improve pathfinding, now might be a good time to consider it. 

In particular, if you have a large chamber (10x10 or larger) with two or more exits, a dwarf entering at one end may need to check 100-ish possible paths to find the way out.  If you draw a high-traffic hallway through the center of that chamber, you can envision that path as a set of rails or channels in the floor of your fort: the dwarves won't leave the rails, or even consider pathing off the rails, until they're right up next to their destination.  If you have a dormitory area with many small rooms and a twisting main hallway, definitely paint the hallway green and the doorways to each room red; that will keep the dwarves from trying to path into any room except the one that is their destination.  Making dorms "dead ends", so that only one doorway leads into a dorm area, is another way to reduce pathing lag.

Every large chamber or dorm area you designate in this way will reduce the cost of every trip through that area, so focus on the largest chambers and the ones that see the most foot traffic.

[jseah]

The raw distance to an item is calculated in a relatively simple way; as the eagle flies mole burrows direct distance, ignoring paths. This value is what is calculated and used whenever a dwarf wants a certain item or material. Therefore, the selection method is;
1) Populate list of potential items.
2) Calculate distance to each.
3) Select the 'closest'.
4) Calculate path to this item.

I understand this is a pretty old post, but could the game just do it the other way around?
Scan outwards in an A* floodfill until you get to one qualifying item.  Then just grab it.  You get your path to the item as well as a bonus. 

[Urist Imiknorris]

I would like to point out that for the purposes of destroying objects, "magma flow" /semi-molten rock destroys absolutely everything that touches it. I never use atomsmashers anymore.

[tps12]

I understand this is a pretty old post, but could the game just do it the other way around?
Scan outwards in an A* floodfill until you get to one qualifying item.  Then just grab it.  You get your path to the item as well as a bonus.

You don't get the benefits of A* without some sort of heuristic telling you how close you are to your goal (if your goal is "any stone" then then you need some way of determining "how close is this tile to the nearest stone" without searching the world, which means storing and maintaining a "distance to nearest stone" or "location of nearest stone" for every tile (or determining and caching it on the fly), and then likewise for every other item type).

Without the heuristic, it's a breadth-first search, which does guarantee you the closest item and a path to it, but degenerates very quickly when the item is far away.

You might be able to start with the breadth-first search and give up if you don't find anything within 5 or 10 steps, reverting to the old method. That actually sort of makes sense in that a creature should be able to figure out the truly closest item within a short distance of themselves, but will maybe make the wrong decision for stuff further away.