Shaders in Oolite: uniforms - Revision history

Cholmondely: Edited as per a_c's suggestions

2026-08-03T22:04:20Z

Edited as per a_c's suggestions

Cholmondely: /* Links */ Tweak

2026-08-03T07:39:54Z

‎Links: Tweak

Cholmondely: Tweak

2026-08-03T07:38:44Z

Tweak

Cholmondely: Added historical context, Links

2026-08-02T15:34:32Z

Added historical context, Links

Kanthoney: /* Entity */ Add fogUniform

2016-02-24T17:03:04Z

‎Entity: Add fogUniform

Tricky: /* Ship */ Change 'withinStationAegis' from 'float' to 'bool'

2012-08-06T07:01:52Z

‎Ship: Change 'withinStationAegis' from 'float' to 'bool'

Cim: /* Ship */ alertCondition uniform in 1.77

2012-06-20T21:45:45Z

‎Ship: alertCondition uniform in 1.77

Ahruman: /* Conversions */ Spelling

2012-01-19T17:29:18Z

‎Conversions: Spelling

Ahruman: /* Basic syntax */ Formatting fixes.

2012-01-19T17:28:24Z

‎Basic syntax: Formatting fixes.

Eric Walch: Added scripting category

2010-02-10T20:19:00Z

Added scripting category

@@ Line 1: / Line 1: @@
   Update!
-  *Shaders changed in Oolite v.1.90 (2020) with the introduction of filmic tone mapping, Oren-Nayar diffuse light model and increased light source radiance
+ * The first major shader revision occurred with Oolite v1.88 (2018) with the introduction of materials supporting Physically Based Rendering (PBR).
-  *Shaders changed again in Oolite v.1.92 (2026) with a [https://www.oolite.space/community/#whatsnew Reworked Renderer]
+   The basic PBR requirements are light energy conservation, microfacet surface model and physically based Bidirectional Reflective Distribution Function (BRDF)
-:<small>The information presented on this page applies to Oolite test release v.1.69 (2007) and later. It was last edited by somebody knowledgeable in 2016</small>
+:<small>The information presented on ''this'' page applies to Oolite test release v.1.69 (2007) and later. It was last added to by somebody ''knowledgeable'' in 2016</small>
 A '''uniform''' in a [[Shaders in Oolite|shader]] is a variable whose value is specified by the host application – in this case, [[Oolite]]. Oolite allows arbitrary uniforms to be specified for shaders applied to ships, and these may either take constant values specified in ''shipdata.plist'', or be “bound” to an attribute of the ship. This allows shader authors to access numerous properties of a game entity without having to ask for them and wait for an updated version of Oolite. ('''Note:''' in the case of subentities, bound properties are fetched from the parent ship.)

@@ Line 214: / Line 214: @@
 == Links ==
-*[[Shaders in Oolite]] - dates to Oolite v.1.72 (2008, but written in 2010)
+*[[Shaders in Oolite]] - dates to Oolite v.1.72 (wiki page written between 2008-10)
 *[[OXP howto texture]] has some up-to-date links

@@ Line 3: / Line 3: @@
   *Shaders changed again in Oolite v.1.92 (2026) with a [https://www.oolite.space/community/#whatsnew Reworked Renderer]
-:<small>The information presented on this page applies to Oolite test release v.1.69 (2007) and later.</small>
+:<small>The information presented on this page applies to Oolite test release v.1.69 (2007) and later. It was last edited by somebody knowledgeable in 2016</small>
 A '''uniform''' in a [[Shaders in Oolite|shader]] is a variable whose value is specified by the host application – in this case, [[Oolite]]. Oolite allows arbitrary uniforms to be specified for shaders applied to ships, and these may either take constant values specified in ''shipdata.plist'', or be “bound” to an attribute of the ship. This allows shader authors to access numerous properties of a game entity without having to ask for them and wait for an updated version of Oolite. ('''Note:''' in the case of subentities, bound properties are fetched from the parent ship.)

@@ Line 1: / Line 1: @@
-:<small>The information presented on this page applies to Oolite test release 1.69 and later.</small>
+ Update!
 A '''uniform''' in a [[Shaders in Oolite|shader]] is a variable whose value is specified by the host application – in this case, [[Oolite]]. Oolite allows arbitrary uniforms to be specified for shaders applied to ships, and these may either take constant values specified in ''shipdata.plist'', or be “bound” to an attribute of the ship. This allows shader authors to access numerous properties of a game entity without having to ask for them and wait for an updated version of Oolite. ('''Note:''' in the case of subentities, bound properties are fetched from the parent ship.)
@@ Line 208: / Line 212: @@
 |}
 Additionally, all [[Methods#Querying states|state query scripting methods]] ending with ''_number'' may be used for the player.
 [[Category:Oolite]]
 [[Category:Oolite scripting]]

@@ Line 97: / Line 97: @@
 |-
 | ''throwingSparks'' || bool || Whether the entity is generating sparks (for instance, a ship about to explode).
 |-
 |}
 ==== Ship ====

@@ Line 130: / Line 130: @@
 | ''scannerRange'' || float || The distance (in metres) in which the ship will scan for enemies.
 |-
-| ''withinStationAegis'' || float || True if the ship is within the aegis of the system’s main station.
+| ''withinStationAegis'' || bool || True if the ship is within the aegis of the system’s main station.
 |-
 | ''fuel'' || int || Ship’s fuel level, in tenths of a light year.

@@ Line 169: / Line 169: @@
 |-
 | ''lightsActive'' || bool || True if flashers are turned on, false otherwise.
 |-
 |}

@@ Line 59: / Line 59: @@
       clamped = true;
   };
-The '''clamped''' conversion option, when applied to a property of type ''float'', causes the value to be clamped to the range [0, 1]. When applied to an ''int'' propertie, any value other than 0 (including negative values) is converted to 1. The default value is ''false''.
+The '''clamped''' conversion option, when applied to a property of type ''float'', causes the value to be clamped to the range [0, 1]. When applied to an ''int'' property, any value other than 0 (including negative values) is converted to 1. The default value is ''false''.
 The '''normalized''' option causes vector properties to be normalized, that is, scaled so they have the same direction but length 1. The default value is ''false''.

@@ Line 27: / Line 27: @@
   <font color="#AAAAAA">    }</font>
   <font color="#AAAAAA">}</font>
-This contrived example declares three uniforms, ''shininess'', ''withinAegis'' and compassMode. ''shininess'' is a constant float; it is always 42. ''withinAegis'' is bound to the ship’s ''withinStationAegis'' property. (See below for information on available properties.) This is a boolean, that is, a number whose value is either 0 (meaning no) or 1 (meaning yes). ''compassMode'' is a binding to the ''compassMode'' property. To use the uniforms within a shader (either a vertex shader or a fragment shader), they are declared as follows:
+This contrived example declares three uniforms, ''shininess'', ''withinAegis'' and ''compassMode''. ''shininess'' is a constant <code>float</code>; it is always 42. ''withinAegis'' is bound to the ship’s ''withinStationAegis'' property. (See below for information on available properties.) This is a boolean, that is, a number whose value is either 0 (meaning no) or 1 (meaning yes). ''compassMode'' is a binding to the ''compassMode'' property. To use the uniforms within a shader (either a vertex shader or a fragment shader), they are declared as follows:
   uniform float shininess;
   uniform int withinAegis;

← Older revision		Revision as of 20:19, 10 February 2010
Line 209:		Line 209:

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