Print

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

[omglazers]

I'm building a massive above ground fort right now, and just from the stone dug out ABOVE ground I have 18,000 stone, with 6,000 in red [I assume this is constructions and stone used in floors, etc]

With such a huge amount of stone, I have read that every single stone gets checked for pathing calculations when doing building and such. If I start forbidding tons of stone or perhaps smashing it, can I reduce my FPS? If mass forbids are just as effective as smashing, then I'd like to find out.

Anyone happen to definitively be able to answer this?

[claer_runway]

time for SCIENCE!

[Khift]

Megaprojects say yes, reducing item count by smashing stone helps. But, megaprojects also deal with 20 or more times that much stone. So... would that much stone help by removing it? I wouldn't think it would, but you're welcome to try science.

[omglazers]

I've always been under the impression that stone FPS issues are caused by calculating pathing to stones when building or crafting. That stone stockpiles and forbidding stone en masse reduces this lag. But I wanted to make sure that this was true as opposed to the only other method I can consider, which is smashing them to bits.

[thijser]

But why do you have a large amout of stone dug out if you are building above ground? Anway You could try to see what happens if you forbid all stone in a few movements if you are building above ground.

[SniHjen]

I've always been under the impression that stone FPS issues are caused by calculating pathing to stones when building or crafting. That stone stockpiles and forbidding stone en masse reduces this lag. But I wanted to make sure that this was true as opposed to the only other method I can consider, which is smashing them to bits.

Dorfs don't look for jobs, jobs looks for dorfs.

[omglazers]

But why do you have a large amout of stone dug out if you are building above ground? Anway You could try to see what happens if you forbid all stone in a few movements if you are building above ground.

Because I carved into a mountain, and I am dwarfy.

[OcelotTango]

The stones don't patch as far as I know, that would just be silly.
I know that when you check you stock page and have TONS of stone, it can take a long time to load the stone amount, slowing the game, but that's just in that menu. As far as I can tell the amount of rocks doesn't really matter unless you have really really silly amounts of it all.

[Vastin]

Stone doesn't use up FPS nearly as fast as long corridors all over the place do.

Forbid all your stone. Forbidden objects aren't checked for much of anything, so if your FPS increases noticeably, then the stone was the issue.

On the other hand, try walling/locking off all your empty mine levels or cavern entrances. That tends to make a very real difference. Honestly I think a lot of the FPS hit we see in DF2010 is simply because of the caverns. Each cavern you breach adds a HUGE amount of very complex pathing space to the world, which can be expensive when dwarves are trying to reach destinations that are far away from their current location.

[Quietust]

Actually, large numbers of stones can cause extra CPU drain due to being affected by temperature changes, which can cause very significant lag if they are outdoors and thus subjected to the weather (underground, everything is temperature 10015).

[omglazers]

Actually, large numbers of stones can cause extra CPU drain due to being affected by temperature changes, which can cause very significant lag if they are outdoors and thus subjected to the weather (underground, everything is temperature 10015).

Ill have to turn off temperature then. I know that they are probably undergoing this, being all above ground.

[Vastin]

Yeah, if something has to calculate against all those objects like temperature, then the cost could start to get a bit rough. Still - pathfinding is numero uno in most forts, liquid flow is another potential killer.

Things like object count and temperature are a bit more of a special case that seems to come up during mega-projects.

[slothen]

I've always been under the impression that stone FPS issues are caused by calculating pathing to stones when building or crafting.

The only thing that is calculated is the direct distance from the job to the stone, which is a very easy calculation, and has a negligible effect on fps.

[omglazers]

Ill try disabling temperature, as it seems those calculations are probably having a lot more of an effect due to the variety of weather my embark gets.

Thanks

[Hokan]

Stones do not look for jobs, jobs look for dwarves and stones.