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.
Difference between revisions of "v0.31:Maximizing framerate"
Jump to navigation
Jump to search
Birthright (talk | contribs) m (augh) |
m |
||
Line 11: | Line 11: | ||
− | *Limiting the number of dwarves and other moving units (cage animals!) greatly helps keep speed up. | + | *Limiting the number of dwarves and other moving units (cage/butcher animals!) greatly helps keep speed up. |
− | *World size and fortress site size increase RAM | + | *World size and fortress site size increase RAM usage and decrease speed. Check if you are happier with an embark rectangle of 3x3 and a medium or small world. |
Revision as of 23:00, 23 April 2010
- Using Baughn's Accelerator program. This was written for the old 40d stuff before most of the recent graphics updates. It is generally reported to increase performance in both windows and WINE emulated DF games, though there have been some reports of a blue tinge and instability arising from the accelerator. See the Bay12 thread here. Please note that this is intended solely as a stopgap until the 40d-graphics merge, so if it doesn't work, don't use it. Baughn has stated that he will not devote time to bugtesting it.
- Changing [PARTIAL_PRINT:NO:2] to [PARTIAL_PRINT:YES:2] often dramatically improves performance.
- Disabling TEMPERATURE and WEATHER in the init file has been shown to increase speed.
- Limiting the number of dwarves and other moving units (cage/butcher animals!) greatly helps keep speed up.
- World size and fortress site size increase RAM usage and decrease speed. Check if you are happier with an embark rectangle of 3x3 and a medium or small world.