Print

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

[ToastySpace]

Has anyone ever successfully used a 16x16 embark area?

[MonkeyHead]

Pretty sure it would exceed the 2GB memory limit and crash.

[zubb2]

DO IT.

[KoboldWarmonger]

Pretty sure it would exceed the 2GB memory limit and crash.

that hasn't been a thing for a while now. DF is large address aware.

[Dorfimedes]

Could be problems with framerate unless you restrict most of it.

[krenshala]

I know my system can handle it (16GB of memory used by a 64bit linux), however, DF is still a 32 bit app, so I think it still has some issues with the larger embarks.  I haven't tried it myself, though, so I could be mistaken.  Has anyone actually tried anything that large recently (post 0.34.01)?

[Finn]

I'll try it tomorrow.  I'm not scared.

[Martin]

Just did it with 34.09. 3 year old MacBook Pro with 4GB RAM. Lovely woodland area with 4 biomes and 3 converging rivers with two nice-sized waterfalls. 182 other creatures on the map from weasels to ravens to hippos to holy fuck that's a lot of carp. So, some trees were chopped and a kitchen dug out. Framerate was in the low teens, which was a bit disappointing, until I remembered that I still had DF running (but paused) in Windows, so I reckon it could have done a fair bit better had I given it a proper showing. I doubt it would have remained better for long, however.


On a properly modern machine with an assload of RAM, I reckon it could be playable in a limited style. An aboveground no immigrant fortress, or something like that. Actually with a 16x16 embark, build a town in each corner and connect them with a massive rail system. But DF won't be properly playable like this without threading as that's how all modern processors are getting their performance.

[Jacko13]

When I was experimenting with big embarks I found processor speed more limiting than memory. Maybe just because my intel i7 is so reliant on hyper threading for its theoretical performance...

[Mrhappyface]

I did make a 16x16 fort...technically. Did in bite sized chunks using just embark to overlap.

[Rbrx]

Once I embarked over an entire human city, because why not.

After like a 15 minute load time, I had like 1800 other creatures, many of them hostile, including the town guards and the resident law giver, and a frame rate of one.

[Girlinhat]

I can do 16x16 embarks, but I don't play them.  I mostly just cover swathes of land like that when I'm looking for an Upright Candy, or a kobold cave, or other interesting map features that don't show up on the map.

[TheCoolSideofthePIllow]

This isn't common? I always make my embark site as large as it can be :O

[Jeoshua]

On Windows:

Get CFFExplorer.
Open Dwarf Fortress.exe
Select NT Headers -> File Header from the list on the left
Click "Click Here" next to Characteristics
Check "App Can Handle >2GB Address Space"
Save and quit

Dwarf Fortress is now able to address >2GB of Ram.

16x16 will still be slow, but if you have over 2 Gigs of RAM, it won't crash because of memory problems.

[Jacko13]

Going to try that out. I gave up playing on anything bigger than 8x8... Kinda pointless but I love all the space and increased chance of finding something !FUN!