v50 Steam/Premium information for editors
  • v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
  • Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.

Editing v0.34:System requirements

Jump to navigation Jump to search

Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.

You are editing a page for an older version of Dwarf Fortress ("Main" is the current version, not "v0.34"). Please make sure you intend to do this. If you are here by mistake, see the current page instead.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 13: Line 13:
 
== RAM ==
 
== RAM ==
  
DF is not particularly RAM-hungry. Expect the process to allocate between 300 and 700 MB with medium regions. With 512MB you may be a bit on the short side, but 1 GB is absolutely sufficient. World Generation can eat up far more than that - it's possible to encounter crashes due to being out of memory. In particular major areas for this to occur are during history, final touches in finalizing sites, and while saving. This is especially problematic with unusual generator configurations, such as worlds with large numbers of megabeasts, caves, civilizations, high or non-existent site and population limits, and very lengthy histories. User-made modifications can also increase the requirements, depending on their nature.
+
DF is not particularly RAM-hungry. Expect the process to allocate between 300 and 700 MB with medium regions. With 512MB you may be a bit on the short side, but 1 GB is absolutely sufficient. World Generation can eat up far more than that - it's possible to encounter crashes due to being out of memory. In particular major areas for this to occur are during history, final touches in finalizing sites, and while saving. This is especially problematic with unusual generator configurations, such as worlds with large numbers of megabeasts, caves, civilizations, high or non-existant site and population limits, and very lengthy histories. User-made modifications can also increase the requirements, depending on their nature.
  
 
The most important thing to the performance of the game, however, is undoubtedly RAM ''latency''—the amount of lag the RAM has when working. Dwarf Fortress works the RAM every single frame for every single creature, every single item, every single piece of liquid, the temperature of every tile—you get the picture. The gigantic amount of operations working at the same time—which any current processor could handle much faster than what you see—is primarily bottlenecked by RAM latency and RAM speed.
 
The most important thing to the performance of the game, however, is undoubtedly RAM ''latency''—the amount of lag the RAM has when working. Dwarf Fortress works the RAM every single frame for every single creature, every single item, every single piece of liquid, the temperature of every tile—you get the picture. The gigantic amount of operations working at the same time—which any current processor could handle much faster than what you see—is primarily bottlenecked by RAM latency and RAM speed.
Line 19: Line 19:
 
CPU and FPS are mildly correlated, but this correlation has been attributed as a non-causative one. Rather, newer CPUs seem to come with faster RAM, but for the purpose of a Dwarf Fortress computer, RAM is more important.
 
CPU and FPS are mildly correlated, but this correlation has been attributed as a non-causative one. Rather, newer CPUs seem to come with faster RAM, but for the purpose of a Dwarf Fortress computer, RAM is more important.
  
== SDL vs. Legacy ==
+
== What is SDL and Legacy version difference? ==
[http://www.libsdl.org/ SDL] is a cross-platform application framework. The SDL version of DF runs on Windows, Mac OS X, and Linux. It includes Baughn's new OpenGL code, which is faster and has more features (including support for PNG tilesets and using scroll wheels).
+
SDL is a cross-platform application framework. The SDL version of DF uses that framework and so runs on mac and linux, along with including Baughn's new opengl code, which should be faster, allows png files for tilesets, zooming with the mousewheel, etc. The SDL version is also being actively worked on, getting features like "separate files for graphics and font", and true-type font support.
  
"Legacy" refers to the (Windows-only) framework Toady used before migrating to SDL. The legacy version is only necessary if the SDL version doesn't work for some reason.
+
Legacy is Toady's old code, only kept in case the SDL version doesn't work for someone. There is no legacy version for mac or linux.
  
 
== Experiential reports ==
 
== Experiential reports ==

Please note that all contributions to Dwarf Fortress Wiki are considered to be released under the GFDL & MIT (see Dwarf Fortress Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)