Time - Revision history

108.85.197.99: prepositions in English - oy

2026-03-09T01:15:52Z

prepositions in English - oy

Silverwing235: /* Framerate */

2025-06-29T09:44:35Z

Framerate

Zippy: The image makes more sense here.

2024-07-22T20:54:17Z

The image makes more sense here.

81.143.213.112: /* Framerate */

2023-02-21T14:46:13Z

Framerate

LethosorBot: Tagging v50 page (4400/4888)

2022-12-21T00:49:36Z

Tagging v50 page (4400/4888)

LethosorBot: LethosorBot moved page DF2014:Time to Time: Migrating v50 page (4195/4618) (content)

2022-12-20T04:03:27Z

LethosorBot moved page DF2014:Time to Time: Migrating v50 page (4195/4618) (content)

Lethosor: /* Framerate / no, it's not* misinformation, but it fits better in a performance-related article. Re-adding only the comparison.

2022-12-10T02:18:08Z

Framerate: no, it's *not* misinformation, but it fits better in a performance-related article. Re-adding only the comparison.

212.102.39.81: They're right - that's literally misinformation. It's not true and not relevant either. Undo revision 266915 by Lethosor (talk)

2022-12-10T00:11:19Z

They're right - that's literally misinformation. It's not true and not relevant either. Undo revision 266915 by Lethosor (talk)

Lethosor: That is quite reasonable. Undo revision 266911 by 185.38.49.2 (talk)

2022-12-04T03:39:40Z

That is quite reasonable. Undo revision 266911 by 185.38.49.2 (talk)

185.38.49.2: Misinformation

2022-12-03T19:02:12Z

Misinformation

@@ Line 3: / Line 3: @@
 : ''For a discussion on the greater passage of time as measured in days/weeks/months/years/ages, see [[Calendar]]
-[[File:moon_preview_anim.gif|right]]'''Time''', in the lower-level "unit-based" sense, is an integral part of any simulation, nonetheleast in one as complex as ''Dwarf Fortress''. Time is measured internally in units which the Adventurer key bindings menus call "instants", but are commonly dubbed "ticks" by the community. Each tick represents one step in the ''Dwarf Fortress'' program, requiring calculations related to [[speed|unit movement]], [[flow|fluid movement]], [[temperature|temperature transfer]], various event checks, [[combat|combat checks]], [[path|pathing checks]], [[labor|job changes]], [[skill|experience ticks]] - basically everything required to run the program, broken up between individual lumps of time. These ticks are then bundled up against days, months, seasons, and then years under the dwarven [[calendar]], which are then further engrossed within individual, context-sensitive [[Calendar#Ages|ages]].
+[[File:moon_preview_anim.gif|right]]'''Time''', in the lower-level "unit-based" sense, is an integral part of any simulation, nonetheleast in one as complex as ''Dwarf Fortress''. Time is measured internally in units which the Adventurer key bindings menus call "instants", but are commonly dubbed "ticks" by the community. Each tick represents one step in the ''Dwarf Fortress'' program, requiring calculations related to [[speed|unit movement]], [[flow|fluid movement]], [[temperature|temperature transfer]], various event checks, [[combat|combat checks]], [[path|pathing checks]], [[labor|job changes]], [[skill|experience ticks]] - basically everything required to run the program, broken up between individual lumps of time. These ticks are then bundled up into days, months, seasons, and then finally years under the dwarven [[calendar]], which, eventually, add up to individual, context-sensitive [[Calendar#Ages|ages]].
 == Basic mechanics ==

@@ Line 53: / Line 53: @@
 How quickly time ''appears'' to pass in your game, especially in fortress mode, has as much to do with your hardware as with the number of ticks in a year. The number of [[frames per second]] is a direct reflection of how many ticks a second your processor is working through. This should be distinguished from the frame ''refresh'' rate, which is how many frames appear on your ''screen'' per second. You can set your FPS to be visible by changing {{tt|[FPS:NO]}} to {{tt|[FPS:YES]}} in your [[Init.txt]] file, which will display two numbers in the top-right corner of your game window, the first being the frames per second and the second being the refresh rate (which is capped at a lower value by default). By default the framerate is capped at 100 FPS, but this setting can be changed or even removed: see [[Frames per second#Controlling FPS|here]] for a technical discussion. For tips on maximizing framerate, see the (topically named) [[Maximizing framerate]] article.
-''Dwarf Fortress'' is an ''extremely'' processor-intensive game, and so how many frames you actually get per second will depend on the strength of your machine, how far into the game and how much clutter there is in it, whether or not you are taking any fps-saving measures, what mods or other programs you are running, and so on. Regardless of mode, there are 28 days in a month and 12 months in a year. Assuming an FPS of 100, not counting pauses an hour of fortress mode gameplay will translate into a year in-game.
+''Dwarf Fortress'' is an ''extremely'' processor-intensive game, and so how many frames you actually get per second will depend on the strength of your machine, how far into the game and how much clutter there is in it, whether or not you are taking any FPS-saving measures, what mods or other programs you are running, and so on. Regardless of mode, there are 28 days in a month and 12 months in a year. Assuming an FPS of 100, not counting pauses an hour of fortress mode gameplay will translate into a year in-game.
 * At 100 FPS:
@@ Line 68: / Line 68: @@
 Then it hits some things that it does every tick.  Fluids and other map tile information is advanced (though there are various optimizations here so that not every tile is necessarily checked every turn, and there are various flags so that entire sections of the map can be skipped if nothing has happened.)  Vermin running around are updated.  Other 'events' on the map, like active fires, are handled.
-If a flag is set, wounded/thirsty/hungry dwarves that can't care for themselves get an update, and every so often, dead dwarves 'think' about their burial arrangements so that jobs can be set.  Caged and chained creatures update their thoughts and situation periodically. Then, creatures leave the map if they are set to at the edges.
+If a flag is set, wounded/thirsty/hungry dwarves that can't care for themselves get an update, and every so often, dead dwarves 'think' about their burial arrangements so that jobs can be set.  Caged and chained creatures update their thoughts and situation periodically. Then, creatures leave the map (if they are set to) at the edges.
 Every fifty ticks, staggered from other updates, all of the taverns, temples, libraries, etc. get their information updated.  Stockpiles, staggered on a different tick, also work this way.  Similarly with storage job creation, though that process is complicated with various optimizations and lengthening ping times and so forth, and it's still slow, since at some point, 50,000+ boulders will cause trouble.
@@ Line 74: / Line 74: @@
 Every thousand ticks, objects that have been marked for deletion and removed from the game are actually deleted and freed.  This happens more often with items, every fifty ticks, along with a building use check (mostly updates for wells and some other flags that often need checking.)
-We hit another every-tick update at this point.  Projectiles are moved.  Activities (which range from dances to martial training to storytelling) get updated as needed.  Dwarves and other creatures decide on and advance their immediate actions (movement to an adjacent tile, working at a workshop, etc.) -- the bulk of their AI (outside of job selection) is here.
+We hit another every-tick update at this point.  Projectiles are moved, and activities (ranging from dances, to martial training, to storytelling) get updated as needed.  Dwarves and other creatures decide on and advance their immediate actions (movement to an adjacent tile, working at a workshop, etc.) -- the bulk of their AI (outside of job selection) is here.
-Every hundred ticks, items are rotted.  Every tick, vegetation is advanced (though there are various staggers and flags here.)  Building states are updated every tick as needed, and minecarts are moved.  Hauling routes are advanced.  Temperature is updated (there are various optimization flags here, but this is still an unfortunately slow process.)
+Every hundred ticks, items are rotted.  Every tick, vegetation is advanced (though there are various staggers and flags here).  Building states are updated every tick as needed, and minecarts are moved.  Hauling routes are advanced.  Temperature is updated (there are various optimization flags here, but this is still an unfortunately slow process).
 Finally, the camera is updated to follow the creature you are following, if any.

@@ Line 1: / Line 1: @@
-{{migrated article}}
+{{Quality|Exceptional}}
-{{av}}{{Quality|Unrated}}
+{{av}}
 : ''For a discussion on the greater passage of time as measured in days/weeks/months/years/ages, see [[Calendar]]
-'''Time''', in the lower-level "unit-based" sense, is an integral part of any simulation, nonetheleast in one as complex as ''Dwarf Fortress''. Time is measured internally in units which the Adventurer key bindings menus call "instants", but are commonly dubbed "ticks" by the community. Each tick represents one step in the ''Dwarf Fortress'' program, requiring calculations related to [[speed|unit movement]], [[flow|fluid movement]], [[temperature|temperature transfer]], various event checks, [[combat|combat checks]], [[path|pathing checks]], [[labor|job changes]], [[skill|experience ticks]] - basically everything required to run the program, broken up between individual lumps of time. These ticks are then bundled up against days, months, seasons, and then years under the dwarven [[calendar]], which are then further engrossed within individual, context-sensitive [[Calendar#Ages|ages]].
+[[File:moon_preview_anim.gif|right]]'''Time''', in the lower-level "unit-based" sense, is an integral part of any simulation, nonetheleast in one as complex as ''Dwarf Fortress''. Time is measured internally in units which the Adventurer key bindings menus call "instants", but are commonly dubbed "ticks" by the community. Each tick represents one step in the ''Dwarf Fortress'' program, requiring calculations related to [[speed|unit movement]], [[flow|fluid movement]], [[temperature|temperature transfer]], various event checks, [[combat|combat checks]], [[path|pathing checks]], [[labor|job changes]], [[skill|experience ticks]] - basically everything required to run the program, broken up between individual lumps of time. These ticks are then bundled up against days, months, seasons, and then years under the dwarven [[calendar]], which are then further engrossed within individual, context-sensitive [[Calendar#Ages|ages]].
 == Basic mechanics ==

@@ Line 59: / Line 59: @@
 * At 60 FPS:
-:: 1 day  = 20 sec ;  1 month = 9 min 20 sec ;  1 year = 1 hour 40 min
+:: 1 day  = 20 sec ;  1 month = 9 min 20 sec ;  1 year = 1 hour 52 min
 * At 30 FPS:
-:: 1 day = 40 sec  ; 1 month = 18 min 40 sec ;  1 year = 3 hour 24 min
+:: 1 day = 40 sec  ; 1 month = 18 min 40 sec ;  1 year = 3 hour 44 min
 In dwarf mode, the game starts with some announcement checks and considers autosaves, etc.  A lot of the rest doesn't happen every tick.  Every hundred ticks, for instance, it'll check job assignments and strange moods. Armies are [[World activities|moved on the world map]].  Every hundred ticks (staggered from the job check), it handles job applications by dwarves, a kind of invisible auction that it uses to manage the various competing priorities.  Every ten ticks it advances the seasons, which actually does all kinds of things with the weather and map (both locally and in the world), and it also does a check for certain plot element advances (diplomats, sieges, etc.), and it checks whether your fort is still alive.

← Older revision		Revision as of 00:49, 21 December 2022
Line 1:		Line 1:
−	{{av}}{{Quality\|~~Exceptional\|04:21, 13 July 2013 (UTC)~~}}	+	{{migrated article}}
		+	{{av}}{{Quality\|Unrated}}
	: ''For a discussion on the greater passage of time as measured in days/weeks/months/years/ages, see [[Calendar]]		: ''For a discussion on the greater passage of time as measured in days/weeks/months/years/ages, see [[Calendar]]

@@ Line 50: / Line 50: @@
 ====Framerate====
-How quickly time ''appears'' to pass in your game, especially in fortress mode, has as much to do with your hardware as with the number of ticks in a year. The number of [[frames per second]] is a direct reflection of how many ticks a second your processor is working through. This should be distinguished from the frame ''refresh'' rate, which is how many frames appear on your ''screen'' per second. You can set your FPS to be visible by changing {{tt|[FPS:NO]}} to {{tt|[FPS:YES]}} in your [[Init.txt]] file, which will display two numbers in the top-right corner of your game window, the first being the frames per second and the second being the refresh rate. By default the framerate is capped at 100 FPS, but this setting can be changed or even removed: see [[Frames per second#Controlling FPS|here]] for a technical discussion. For tips on maximizing framerate, see the (topically named) [[Maximizing framerate]] article.
+How quickly time ''appears'' to pass in your game, especially in fortress mode, has as much to do with your hardware as with the number of ticks in a year. The number of [[frames per second]] is a direct reflection of how many ticks a second your processor is working through. This should be distinguished from the frame ''refresh'' rate, which is how many frames appear on your ''screen'' per second. You can set your FPS to be visible by changing {{tt|[FPS:NO]}} to {{tt|[FPS:YES]}} in your [[Init.txt]] file, which will display two numbers in the top-right corner of your game window, the first being the frames per second and the second being the refresh rate (which is capped at a lower value by default). By default the framerate is capped at 100 FPS, but this setting can be changed or even removed: see [[Frames per second#Controlling FPS|here]] for a technical discussion. For tips on maximizing framerate, see the (topically named) [[Maximizing framerate]] article.
 ''Dwarf Fortress'' is an ''extremely'' processor-intensive game, and so how many frames you actually get per second will depend on the strength of your machine, how far into the game and how much clutter there is in it, whether or not you are taking any fps-saving measures, what mods or other programs you are running, and so on. Regardless of mode, there are 28 days in a month and 12 months in a year. Assuming an FPS of 100, not counting pauses an hour of fortress mode gameplay will translate into a year in-game.