Print

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

[acetech09]

Project time!

Gonna leave my computer genning world history all night, will see how it turns out in morning.

[Vehudur]

It'll crash if it hits the RAM cap for your system.  If you're on a 32 bit this is pretty easy.

[acetech09]

Thx for reminding me.

*moves from his 4gb RAM macbook pro onto his 64gb workstation*

[Xenxe]

Thx for reminding me.

*moves from his 4gb RAM macbook pro onto his 64gb workstation*

That's half my hard drive in ram T_T

[acetech09]

Useful DF-enhancing tip:

Finding a way to selectively control cores of your processor, paired with overclocking, can make a computer run DF a crapton better.

i.e: My workstation, 64gb of ram, dual i7 990xs, dual 512mb SSDs and dual 1tb HDDs. I take one of my i7s down to a single core. Now that the i7 is running at what'd be normally half power/temp, I can overclock it beyond what I could do with all four cores running.

That results with a incredibly high core speed that supports DF's single threading a lot better. 300-dwarf forts run fine.

[Eric Blank]

cores... I just got an Intel i5 that should outperform this piece of shit I have now by a huge amount. and 8gb of RAM to support the new motherboard. I knew RAM had something to do with the crashing but everyone assured me it was purely the processor.

Also I find it odd how, during world gen, the game will reach 550-600k K of memory usage on the windows task manager screen, then spontaneously drop down to the baseline and ramp back up. Happens around year 130 or so.

On the real topic: I can only ever gen large worlds to year 200. I would love to go further, and am hoping the ram upgrade, which doesn't max out my motherboard, will let me reach 4-500. The best way to deal with the kobold issue is to just go to raw/objects/creature_standard.txt, search it for 'kobold' (ctrl-f to search for keywords) and below the tag [UTTERANCES] in the Kobold entry you just found place [NO_EAT], exactly like that. Then save and exit and generate a world. It'll work on a pre-genned world, but they'd already be dead anyway.

And if you can't generate a 1000+ year history, search for 'dragon' in that same file, and when you find it search for BODY_SIZE and select the one that reads [BODY_SIZE:1000:0:25000000], and change the '1000' to anything to less than the number in years you intend to generate to. This will force them to be the adult sized by the time world gen ends.

[Therolyn]

I perfer 250 because in my expernce its alot easyer to find sedimentary layers on a longer world gen. Dont ask why I just do. Maby because I Belive that DF makes it so that sedimentary layers show up as a result of constant erosion

Constant, hyper-effective erosion?

Maybe the water has a powerful acid in it...

Its probably why dwarves prefer booze to water...

[612DwarfAvenue]

Terrain only erodes during the terrain-forming part of worldgen, the history part has nothing to do with how much soil you have .

As for me, i usually do 100, though i might start doing 2 so the Kobolds don't die off.

[Loud Whispers]

I usually always choose year 2, although I also tried year 2012 for fun.

Rest assured, both settings induce lots of !!FUN!!.

[peskyninja]

If you embark year one you can be the first dwarf in the world to kill an elf.

Impossible, embarking advances the world time by 1 year.

[612DwarfAvenue]

If you embark year one you can be the first dwarf in the world to kill an elf.

Impossible, embarking advances the world time by 1 year.

Yes, but stuff doesn't happen outside of your fort when you're in Fort Mode. As such, it may kick you to year 2, but you'll still be the first to kill an Elf, assuming someone didn't beat you to the punch in year 1.

[Frelus]

The best way to deal with the kobold issue is to just go to raw/objects/creature_standard.txt, search it for 'kobold' (ctrl-f to search for keywords) and below the tag [UTTERANCES] in the Kobold entry you just found place [NO_EAT], exactly like that. Then save and exit and generate a world. It'll work on a pre-genned world, but they'd already be dead anyway.

And if you can't generate a 1000+ year history, search for 'dragon' in that same file, and when you find it search for BODY_SIZE and select the one that reads [BODY_SIZE:1000:0:25000000], and change the '1000' to anything to less than the number in years you intend to generate to. This will force them to be the adult sized by the time world gen ends.

You, Sir, are my hero.

[SuicideJunkie]

It'll crash if it hits the RAM cap for your system.  If you're on a 32 bit this is pretty easy.

Say what? 
I gen 1000+ years of history on my *netbook* with no problem.
2Gb of ram, and an atom processor, so it takes quite a lot of hours, but it works fine.

I am using the linux version, but any OS should handle swapping to disk when you run out of physical ram.

[Rinnix]

I usually let it stop around 200 years, but I usually go with a much lower number if I'm up to a great game in Adventurer. And as for the kobolds, I've actually had a world with about four (count em',: about-four) kobold civs. I thought it was a bug since I had been messing with the raws and adding things, so I got rid of the world. What a mistake.

[helf]

The amount of ram your system has doesn't matter other than for performance issues. Dwarf Fortress is a 32bit game and, under windows at least, will die horribly when it hits the 2GB address barrier for 32bit apps. You can make Windows allow up to 3GB per 32bit process and I think Linux allows this, but (unless I'm mistaken) the app has to be programmed to make use of this. I don't think DF is.

I've always had it doe once its hits 2GB of usage and I'm on a 64bit Windows 7 machine with 12gb of ram.