Print

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

[SimRobert2001]

Has anyone attempted a full embark to see if it was possible yet? Does the game still crash? How slow was it compared to your normal embark?

[Fleeting Frames]

It's 16x16, not 20x20, which is probably why the term didn't show up on your searches or skimming through the 43.04 where it was tested, for instance. Short summary: yes it is possible, and starts at 50-15 FPS.

[steel jackal]

ive tried a 16x16 several times, biggest ive ever gotten was 7x7 but it was nearly unplayable with the lag at the very beginning.
biggest i can do and still have the game playable is 5x5

[SimRobert2001]

ive tried a 16x16 several times, biggest ive ever gotten was 7x7 but it was nearly unplayable with the lag at the very beginning.
biggest i can do and still have the game playable is 5x5

Even with the newest version?

[Väinämöinen]

I just did a full history and max sized embark.

While being a x64 process it still uses only a single processor (no multi core support) - so yeah you can play but FPS wont be that great.

[steel jackal]

ive tried a 16x16 several times, biggest ive ever gotten was 7x7 but it was nearly unplayable with the lag at the very beginning.
biggest i can do and still have the game playable is 5x5

Even with the newest version?

no this was in 0.40 ish, im playing a 5x5 embark right now and the game stops for a few moments every once in a while and it takes AGES to save and load. the FPS seems fine but i havent breached the caverns and im only on the 2nd year

[SimRobert2001]

ive tried a 16x16 several times, biggest ive ever gotten was 7x7 but it was nearly unplayable with the lag at the very beginning.
biggest i can do and still have the game playable is 5x5

Even with the newest version?

no this was in 0.40 ish, im playing a 5x5 embark right now and the game stops for a few moments every once in a while and it takes AGES to save and load. the FPS seems fine but i havent breached the caverns and im only on the 2nd year

ah. Cause the problem with .40 is that the 32 bit structure couldn't support a 16x16 without crashing.

[steel jackal]

ive tried a 16x16 several times, biggest ive ever gotten was 7x7 but it was nearly unplayable with the lag at the very beginning.
biggest i can do and still have the game playable is 5x5

Even with the newest version?

no this was in 0.40 ish, im playing a 5x5 embark right now and the game stops for a few moments every once in a while and it takes AGES to save and load. the FPS seems fine but i havent breached the caverns and im only on the 2nd year

ah. Cause the problem with .40 is that the 32 bit structure couldn't support a 16x16 without crashing.

huh i guess i should upgrade, im still running 0.43.02
that might make my game not take 2 minutes to save and load

[They Got Leader]

Someone with more knowledge on the subject can add more to this, but:

The change from 32 bit to 64 bit was less to do with the way that the processor handles the task, but more of how the RAM sees it. The architecture of 64 bit allows for larger strings to be stored when the game is running (from 32 bit strings to 64 bit strings). This means that the game can page more RAM. A 32 bit game can't access more than ~4 gb of RAM before the architecture stops functioning while 64 bit is... well, let us just call it nigh-infinite.

So what does this mean for Dwarf Fortress?

Well, from what I can tell, once the game is RUNNING and everything has loaded, it (for me) runs smoother over the course of a day. I load in and after about 30 minutes of playing, I get a steady  35 FPS with almost no dips or drops. My fortress is on a 5x5 square and I have ~75 dwarves, 10 bards, ~30 animals, and all 3 cavern layers found.

[steel jackal]

Someone with more knowledge on the subject can add more to this, but:

The change from 32 bit to 64 bit was less to do with the way that the processor handles the task, but more of how the RAM sees it. The architecture of 64 bit allows for larger strings to be stored when the game is running (from 32 bit strings to 64 bit strings). This means that the game can page more RAM. A 32 bit game can't access more than ~4 gb of RAM before the architecture stops functioning while 64 bit is... well, let us just call it nigh-infinite.

So what does this mean for Dwarf Fortress?

Well, from what I can tell, once the game is RUNNING and everything has loaded, it (for me) runs smoother over the course of a day. I load in and after about 30 minutes of playing, I get a steady  35 FPS with almost no dips or drops. My fortress is on a 5x5 square and I have ~75 dwarves, 10 bards, ~30 animals, and all 3 cavern layers found.

you pretty much covered it, theres a youtuber called scott manly that talked about kerbal space program going from 32 bit to 64 bit and he said pretty much everything you did but in a more long-winded way.
although i thought it was 2GB, my comp only has 4 gb of ram so if 32 bit already had 4gb of ram i shouldent notice such a significant diffrence

but yeah i just got 64 bit set up a few mins ago and the game runs SOOO much more smoothly <3

[Shonai_Dweller]

It's 2GB in Windows because it artificially imposes a 2GB limit in 32 bit for some reason.

[They Got Leader]

It's 2GB in Windows because it artificially imposes a 2GB limit in 32 bit for some reason.

"In non-PAE modes of x86 processors, the RAM is always limited to 3.76GB" from wikipedia, but you can find more at Microsoft. The math of a 64 bit is silly, at best. The reason for the self-imposed 32 bit RAM ceiling is because a 32 bit operating system could ONLY have 4 gigabytes of RAM total (before PAE). Your operating system needs some of that to run, and some of it is cushion space to open and run other processes in the background. Multi-threading offers an interesting work around as it allows your PC to run all of it's OTHER processes on other threads while DF can hop between a few with little bother. On a 64 bit install of Windows, you can put up to 128 gigabytes (I think that is the motherboard physical LIMIT right now, short of server hardware), and the OS can use all of it.

As a side note: if you want to get the most out of your DF and multi-thread machine, open task manager, go to processes, right click on DF and set it's priority to HIGH, and then set the AFFINITY to a couple cores and viola. The game will now use specific cores and it will run its process regardless of background programs.

[Väinämöinen]

You can rise the amount of memory available by flagging LAA on the x86 process. But x64 and related code is more efficient and recent.

[Linkxsc]

16x16 is 256 48x48s.
Thats just a bit over a half million tiles alone.


Sefinitely going to want to use burrows, dont want to have everyone trying to run all the way across the map.


But i cant wait. Ima give it 1 more bugfix before giving the 16x16 a try. One can only hope 16gb or ram will be enough.

[RocheLimit]

16x16 is 256 48x48s.
Thats just a bit over a half million tiles alone.

That's... far more tiles than I had thought.  You know Flarechannel?  That masterwork of a fort used a quarter million blocks.  It would take twice that number just to floor the surface of a 16x16.

Spoiler (click to show/hide)

Flarechannel: http://www.bay12forums.com/smf/index.php?topic=43679.0

But i cant wait. Ima give it 1 more bugfix before giving the 16x16 a try. One can only hope 16gb or ram will be enough.

I managed to get a 14x14' working' (you can embark but unpausing crashes) using a Large-Address-Aware modded 40.24 Dwarf Fortress.  Took about 3.8 gig.  I can't imagine a 16x16 taking more than 8.