- 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.
Difference between revisions of "v0.31:Frames per second"
(Fleshed out the article and re-rated) |
m (corrected redlinks) |
||
| Line 4: | Line 4: | ||
==What is FPS?== | ==What is FPS?== | ||
| − | '''Frames per second''', often referred to as FPS or framerate, is the measure of the amount of '''steps''' the game calculates in one second. Each step requires the calculation of | + | '''Frames per second''', often referred to as FPS or framerate, is the measure of the amount of '''steps''' the game calculates in one second. Each step requires the calculation of unit movement, fluid movement, and many checks for different events, such as {{L|cave-in|cave-ins}}, [[Digging_designation_canceled | damp/warm stone]], {{L|weather|weather conditions}}, and much more. |
| − | Note that game steps are independent of dwarf steps. A dwarf | + | Note that game steps are independent of dwarf steps. A dwarf with average {{L|attributes#Agility|agility}} will move 1 {{L|map tile|tile}} in 10 steps. |
==Maximizing FPS== | ==Maximizing FPS== | ||
| − | There are many methods to increase one's framerate, which can be found {{L|Maximizing framerate|here}}. These can be crucial, as a common reason for abandoning forts is that the framerate becomes too low from all the dwarves, {{L|animal|animals}}, and | + | There are many methods to increase one's framerate, which can be found {{L|Maximizing framerate|here}}. These can be crucial, as a common reason for abandoning forts is that the framerate becomes too low from all the dwarves, {{L|animal|animals}}, and explored tiles having to have calculations performed each step. This is especially true if many {{L|cavern|caverns}} have been {{L|mining|unearthed}}. |
==Controlling FPS== | ==Controlling FPS== | ||
| − | By default, the framerate is set to not exceed 100, though this can be changed in the {{L|init.txt}} file, under [FPS_CAP]. Increasing or disabling([FPS_CAP:0]) this setting will allow a fortress to progress more quickly, though eventually there will be a maximum reached as a result of CPU speed limits. This also requires more attention from the player as {{L|designation|designated jobs}} will be completed or cancelled more quickly, and potentially harmful events─such as wild animals, {{L|thief|thieves}}, and {{L| | + | By default, the framerate is set to not exceed 100, though this can be changed in the {{L|init.txt}} file, under [FPS_CAP]. Increasing or disabling([FPS_CAP:0]) this setting will allow a fortress to progress more quickly, though eventually there will be a maximum reached as a result of CPU speed limits. This also requires more attention from the player as {{L|designation|designated jobs}} will be completed or cancelled more quickly, and potentially harmful events─such as wild animals, {{L|thief|thieves}}, and {{L|ambush|invasions}}─will occur more frequently in a given span of real time. |
| − | Decreasing the FPS cap will slow down the progress of a fortress, though it may be useful for if the framerate undergoes large, rapid changes, as it will smooth out the play experience. It can also be useful to slow down the game in order to handle other | + | Decreasing the FPS cap will slow down the progress of a fortress, though it may be useful for if the framerate undergoes large, rapid changes, as it will smooth out the play experience. It can also be useful to slow down the game in order to handle other activities while still allowing the fortress to complete previously assigned tasks, while reducing the need to babysit the game. |
Revision as of 04:40, 10 June 2010
| This article is about an older version of DF. |
What is FPS?
Frames per second, often referred to as FPS or framerate, is the measure of the amount of steps the game calculates in one second. Each step requires the calculation of unit movement, fluid movement, and many checks for different events, such as Template:L, damp/warm stone, Template:L, and much more.
Note that game steps are independent of dwarf steps. A dwarf with average Template:L will move 1 Template:L in 10 steps.
Maximizing FPS
There are many methods to increase one's framerate, which can be found Template:L. These can be crucial, as a common reason for abandoning forts is that the framerate becomes too low from all the dwarves, Template:L, and explored tiles having to have calculations performed each step. This is especially true if many Template:L have been Template:L.
Controlling FPS
By default, the framerate is set to not exceed 100, though this can be changed in the Template:L file, under [FPS_CAP]. Increasing or disabling([FPS_CAP:0]) this setting will allow a fortress to progress more quickly, though eventually there will be a maximum reached as a result of CPU speed limits. This also requires more attention from the player as Template:L will be completed or cancelled more quickly, and potentially harmful events─such as wild animals, Template:L, and Template:L─will occur more frequently in a given span of real time.
Decreasing the FPS cap will slow down the progress of a fortress, though it may be useful for if the framerate undergoes large, rapid changes, as it will smooth out the play experience. It can also be useful to slow down the game in order to handle other activities while still allowing the fortress to complete previously assigned tasks, while reducing the need to babysit the game.