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 40d Talk: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 "40d"). 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 67: Line 67:
 
It would be really useful to use one or more specific fortresses for benchmarking purposes and post them all on DFFD, rather than just including various details which don't include certain vital statistics such as the number of objects, amount of revealed tiles, mid-air Z-levels which have been "allocated" by building into them (such that using "k" actually shows them as "open space" rather than nothing at all), and actual fortress layout (and thus how much CPU time is spent pathfinding). For example, a 2.4GHz Core 2 Duo is listed as handling a minimalist 6x6 site with 95 dwarves at ~20fps, while my 2.4GHz Core 2 Quad was able to support an 8x4 site with magma + pit + underground river + HFS and 200 dwarves and get 20fps with everything turned '''on''' because I had taken care to organize the fortress in such a way as to minimize pathfinding load. --[[User:Quietust|Quietust]] 18:40, 20 January 2010 (UTC)
 
It would be really useful to use one or more specific fortresses for benchmarking purposes and post them all on DFFD, rather than just including various details which don't include certain vital statistics such as the number of objects, amount of revealed tiles, mid-air Z-levels which have been "allocated" by building into them (such that using "k" actually shows them as "open space" rather than nothing at all), and actual fortress layout (and thus how much CPU time is spent pathfinding). For example, a 2.4GHz Core 2 Duo is listed as handling a minimalist 6x6 site with 95 dwarves at ~20fps, while my 2.4GHz Core 2 Quad was able to support an 8x4 site with magma + pit + underground river + HFS and 200 dwarves and get 20fps with everything turned '''on''' because I had taken care to organize the fortress in such a way as to minimize pathfinding load. --[[User:Quietust|Quietust]] 18:40, 20 January 2010 (UTC)
  
:I like this idea overall. I don´t think it would be possible to assume what an "average" person builds their fortress like or if they even take pathfinding into account, but a standardized fortress, set of options, DF version, and t/f on use of OpenGL "accelerator" would make this list much more insightful. Unfortunately, it would throw out all previous data collected. If someone has the will and time, I think it would benefit readers, but I think the section does already serve its purpose in giving people a very rough idea of what to expect. In the data I personally posted, I did use the same fort (which paid no attention to optimizing the layout for minimizing pathfinding calculations) but I didn´t think to upload the save and no longer have it.[[User:Kludge|-K]] 03:37, 7 February 2010 (UTC) (a post-post thought -- It´d also be nice to have standardized data since the data could be merged into a pretty table!)
+
:I like this idea overall. I don´t think it would be possible to assume what an "average" person builds their fortress like or if they even take pathfinding into account, but a standardized fortress, set of options, DF version, and t/f on use of OpenGL "accelerator" would make this list much more insightful. Unfortunately, it would throw out all previous data collected. If someone has the will and time, I think it would benefit readers, but I think the section does already serve its purpose in giving people a very rough idea of what to expect. In the data I personally posted, I did use the same fort (which paid no attention to optimizing the layout for minimizing pathfinding calculations) but I didn´t think to upload the save and no longer have it.[[User:Kludge|-K]] 03:37, 7 February 2010 (UTC)
  
 
== Where do I get the Linux port? ==
 
== Where do I get the Linux port? ==

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!

Please sign comments with ~~~~

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

Cancel Editing help (opens in new window)