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:Maximizing framerate

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 107: Line 107:
 
:[[User_talk:Squirrelloid#Animals_try_to_path_through_tightly_closed_doors|Squirrelloid]]'s done some tests that end up proving the same point, but with animals instead of thieves/snatchers. Both of those groups use flawed pathfinding that doesn't properly account for created obstacles that are passable under certain conditions that aren't true at the time of the pathfind. (Doors being forbidden, or bridges raised for the thieves, and doors being designated as pet forbidden for the animals.) I still say that failed pathfinds cause 90% of framerate loss. --[[User:N9103|Edward]] 06:24, 1 May 2008 (EDT)
 
:[[User_talk:Squirrelloid#Animals_try_to_path_through_tightly_closed_doors|Squirrelloid]]'s done some tests that end up proving the same point, but with animals instead of thieves/snatchers. Both of those groups use flawed pathfinding that doesn't properly account for created obstacles that are passable under certain conditions that aren't true at the time of the pathfind. (Doors being forbidden, or bridges raised for the thieves, and doors being designated as pet forbidden for the animals.) I still say that failed pathfinds cause 90% of framerate loss. --[[User:N9103|Edward]] 06:24, 1 May 2008 (EDT)
  
:I've uploaded a zip of my errorlog.txt that encompasses a decent, but not overly long amount of time. The unzipped file is 22MB! Thankfully, text compresses very well, and the zip is only 387K. <99% of the file is failed mischief from either goblins or kobolds. [http://dffd.wimbli.com/file.php?id=167] --[[User:N9103|Edward]] 02:29, 11 May 2008 (EDT)
+
:I've uploaded a zip of my errorlog.txt that encompasses a decent, but not overly long amount of time. The unzipped file is 22MB! Thankfully, text compresses very well, and the zip is only 387K. <99% of the file is failed mischief from either goblins or kobolds. [[http://dffd.wimbli.com/file.php?id=167]]
  
 
: At some point the article on Maximizing Framerate should include a section that deals with player actions that can have an impact.  Things like connecting a large open pipe system to a running water source, mass-designating stone for dumping, and closing off your fortress should all be listed as cons.  I'm doing some research right now into the benefits of intelligent [[traffic area]] designations as well.  For example, rooms larger than 11x11 with only two doors should have a high-traffic line linking the two doors, and two low-traffic "curbs" on either edge, to prevent the Dijkstra half of A* from spending extra cycles looking in dumb places. --[[User:Jurph|Jurph]] 18:01, 8 April 2009 (UTC)
 
: At some point the article on Maximizing Framerate should include a section that deals with player actions that can have an impact.  Things like connecting a large open pipe system to a running water source, mass-designating stone for dumping, and closing off your fortress should all be listed as cons.  I'm doing some research right now into the benefits of intelligent [[traffic area]] designations as well.  For example, rooms larger than 11x11 with only two doors should have a high-traffic line linking the two doors, and two low-traffic "curbs" on either edge, to prevent the Dijkstra half of A* from spending extra cycles looking in dumb places. --[[User:Jurph|Jurph]] 18:01, 8 April 2009 (UTC)

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)