Time scales in Oolite - Revision history

Cholmondely: Added link

2021-03-09T11:55:59Z

Added link

Commander McLane: changed category to scripting

2013-09-09T15:42:22Z

changed category to scripting

Ahruman: Whoops, no BBcode here.

2010-07-16T17:59:37Z

Whoops, no BBcode here.

Ahruman: Noted TAF

2010-07-16T17:59:17Z

Noted TAF

Ahruman: Added Category:Oolite scripting

2007-06-07T18:09:49Z

Added Category:Oolite scripting

Ahruman: formatting.

2007-06-07T18:08:36Z

formatting.

Ahruman: New page: When writing scripts or shaders for Oolite, there are several different '''time scales''' to consider. This article defines them and provides nomenclature to simp...

2007-06-07T18:07:44Z

New page: When writing scripts or shaders for Oolite, there are several different '''time scales''' to consider. This article defines them and provides nomenclature to simp...

New page

When writing scripts or [[shaders in Oolite|shaders]] for [[Oolite]], there are several different '''time scales''' to consider. This article defines them and provides nomenclature to simplify discussions where the distinctions matter.

=== Player real time ===
This is the time frame of the human being playing the game. By definition, it advances at a rate of one ''player real time second'' per real-world second.

=== Game real time ===
This is the time frame of the game simulation. Assuming a properly-functioning computer, it runs at one ''game real time second'' per ''player real time second'', except when the game is paused, at which time it is suspended. This is the time frame that’s generally relevant to shaders and AIs.

=== Game clock time ===
This is the time displayed on the clock on the HUD. It normally runs at a rate of one ''game clock time second'' per ''game real time second''. However, some in-game events take a significant amount of clock time without providing an opportunity for gameplay; examples include witchspace jumps, docking and loading cargo. When such an event occurs, the HUD clock shows the label “adjusting” and runs faster than ''game real time''. This time frame is relevant to missions with a time limit.

@@ Line 9: / Line 9: @@
 === Game clock time ===
 This is the time displayed on the clock on the HUD. It normally runs at a rate of one '''game clock time second''' per game real time second. However, some in-game events take a significant amount of clock time without providing an opportunity for gameplay; examples include witchspace jumps, docking and loading cargo. When such an event occurs, the HUD clock shows the label “adjusting” and runs faster than game real time. This time frame is relevant to missions with a time limit.
 [[Category:Oolite scripting]]

← Older revision		Revision as of 15:42, 9 September 2013
Line 10:		Line 10:
	This is the time displayed on the clock on the HUD. It normally runs at a rate of one '''game clock time second''' per game real time second. However, some in-game events take a significant amount of clock time without providing an opportunity for gameplay; examples include witchspace jumps, docking and loading cargo. When such an event occurs, the HUD clock shows the label “adjusting” and runs faster than game real time. This time frame is relevant to missions with a time limit.		This is the time displayed on the clock on the HUD. It normally runs at a rate of one '''game clock time second''' per game real time second. However, some in-game events take a significant amount of clock time without providing an opportunity for gameplay; examples include witchspace jumps, docking and loading cargo. When such an event occurs, the HUD clock shows the label “adjusting” and runs faster than game real time. This time frame is relevant to missions with a time limit.

−	[[Category:Oolite]]	+	[[Category:Oolite scripting]]

@@ Line 5: / Line 5: @@
 === Game real time ===
-This is the time frame of the game simulation. Assuming a properly-functioning computer, it runs at one '''game real time second''' per player real time second, except when the game is paused, at which time it is suspended. However, it can be run at different rates using the [i]time acceleration factor[/i] testing facility. This is the time frame that’s generally relevant to shaders and AIs.
+This is the time frame of the game simulation. Assuming a properly-functioning computer, it runs at one '''game real time second''' per player real time second, except when the game is paused, at which time it is suspended. However, it can be run at different rates using the ''time acceleration factor'' testing facility. This is the time frame that’s generally relevant to shaders and AIs.
 === Game clock time ===

@@ Line 5: / Line 5: @@
 === Game real time ===
-This is the time frame of the game simulation. Assuming a properly-functioning computer, it runs at one '''game real time second''' per player real time second, except when the game is paused, at which time it is suspended. This is the time frame that’s generally relevant to shaders and AIs.
+This is the time frame of the game simulation. Assuming a properly-functioning computer, it runs at one '''game real time second''' per player real time second, except when the game is paused, at which time it is suspended. However, it can be run at different rates using the [i]time acceleration factor[/i] testing facility. This is the time frame that’s generally relevant to shaders and AIs.
 === Game clock time ===

← Older revision		Revision as of 18:09, 7 June 2007
Line 9:		Line 9:
	=== Game clock time ===		=== Game clock time ===
	This is the time displayed on the clock on the HUD. It normally runs at a rate of one '''game clock time second''' per game real time second. However, some in-game events take a significant amount of clock time without providing an opportunity for gameplay; examples include witchspace jumps, docking and loading cargo. When such an event occurs, the HUD clock shows the label “adjusting” and runs faster than game real time. This time frame is relevant to missions with a time limit.		This is the time displayed on the clock on the HUD. It normally runs at a rate of one '''game clock time second''' per game real time second. However, some in-game events take a significant amount of clock time without providing an opportunity for gameplay; examples include witchspace jumps, docking and loading cargo. When such an event occurs, the HUD clock shows the label “adjusting” and runs faster than game real time. This time frame is relevant to missions with a time limit.
		+
		+	[[Category:Oolite]]

@@ Line 2: / Line 2: @@
 === Player real time ===
-This is the time frame of the human being playing the game. By definition, it advances at a rate of one ''player real time second'' per real-world second.
+This is the time frame of the human being playing the game. By definition, it advances at a rate of one '''player real time second''' per real-world second.
 === Game real time ===
-This is the time frame of the game simulation. Assuming a properly-functioning computer, it runs at one ''game real time second'' per ''player real time second'', except when the game is paused, at which time it is suspended. This is the time frame that’s generally relevant to shaders and AIs.
+This is the time frame of the game simulation. Assuming a properly-functioning computer, it runs at one '''game real time second''' per player real time second, except when the game is paused, at which time it is suspended. This is the time frame that’s generally relevant to shaders and AIs.
 === Game clock time ===
-This is the time displayed on the clock on the HUD. It normally runs at a rate of one ''game clock time second'' per ''game real time second''. However, some in-game events take a significant amount of clock time without providing an opportunity for gameplay; examples include witchspace jumps, docking and loading cargo. When such an event occurs, the HUD clock shows the label “adjusting” and runs faster than ''game real time''. This time frame is relevant to missions with a time limit.
+This is the time displayed on the clock on the HUD. It normally runs at a rate of one '''game clock time second''' per game real time second. However, some in-game events take a significant amount of clock time without providing an opportunity for gameplay; examples include witchspace jumps, docking and loading cargo. When such an event occurs, the HUD clock shows the label “adjusting” and runs faster than game real time. This time frame is relevant to missions with a time limit.