Newgrf Airports Documentation - Revision history

Yexo: /* Airport Tiles (Feature 10) */

2010-02-01T19:38:48Z

‎Airport Tiles (Feature 10)

2010-01-21T01:59:28Z

‎Action 0 Airport Tiles

2010-01-21T01:49:39Z

‎Callbacks for Airport Tiles

2010-01-17T16:33:32Z

‎Action 0 Airport Tiles

2010-01-13T21:36:37Z

‎Action 0 Airports

2010-01-08T21:28:11Z

‎Action 0 Airports

2010-01-07T14:35:40Z

2009-11-03T20:32:20Z

counter-proposal for public airports

2009-11-03T07:16:32Z

‎Basic aircraft information

2009-11-03T06:59:27Z

‎Action 0 Aircraft

@@ Line 2: / Line 2: @@
 __TOC__
-=Airport Tiles (Feature 10)=
+=Airport Tiles (Feature 11)=
 '''Airport tiles''' are the graphical component of the airport.  They have no direct interaction or effect on the state machine on or aircraft.

@@ Line 13: / Line 13: @@
 * 10 (b) Animation speed
 as per [http://wiki.ttdpatch.net/tiki-index.php?page=Action0IndustryTiles Properties for industry tiles 0D, 0E, 0F and 10].
 * 13 (b) Hangar #, from 01 to 0F: Clicking on this tile will open the hangar window or create a hangar order. 00 = no hangar.

@@ Line 33: / Line 33: @@
 The related object for airport tiles is the airport.
 * Next animation frame (153, like 1A/26/141)
-* Animation control (152, like 1B/25/140) not yet implemented
+* Animation control (152, like 1B/25/140)
 * Length of animation frame (154, like 20/27/142)
 * Custom shape check (158, like 2F)

@@ Line 7: / Line 7: @@
 ==Action 0 Airport Tiles==
 * 08 (b) Substitute tile type. Default airport tile to use when this newgrf is no longer available. Valid values are 0-8F.
 * 0D (b) Land shape flags
 * 0E (b) Callback flags (not callback 2B and 2C)

@@ Line 44: / Line 44: @@
 * 08 (d) airport class (works like station class), use strings C6xx to set the name (like C4xx for station classes). Defaults: 'SMAL', 'LARG', 'HUB_', 'HELI'
 * 0A (data) Tile array similar to [http://wiki.ttdpatch.net/tiki-index.php?page=Action0Industries Industry Property 0A]. Important difference: you have to specify a rotation (b) for every layout. It's the first byte (just before the first tile) and can have the following values: 0 (= no rotation), 2 (= rotated 90 east), 4 (= rotated 180), 6 (=rotated 270 east = 90 west).
-* 0B (data) Node array.  Each node has an x,y,z position, and a flag byte (hangar, entry point, loading bay) used for overbuilding, buying/selling aircraft in the hangar and, in the case of the entry point(s), aircraft interception from outside the state machine.
+* 0B (data) Node array.  Each node has an x,y,z position, and a flag byte (hangar, loading bay) used for overbuilding, buying/selling aircraft in the hangar and.
-:* Format:  0B <num nodes> <xx xx yy yy zz zz dd ff> <xx xx yy yy zz zz dd ff> <xx xx yy yy zz zz dd fh> ...
+:* Format:  0B <num nodes> <xx xx yy yy zz zz dd fh> <xx xx yy yy zz zz dd fh> <xx xx yy yy zz zz dd fh> ...
-::*f values: 1 = loading bay.  h = hangar number.
+::*f values: 1 = loading bay
 * 0C-0D (2xw) - Years available (start and end year. 0000 and FFFF are forever respectively)
 * 0F (b) Small/Large/Helipad/Oilrig (note: for backwards compatibility with vehicle var 44)

@@ Line 53: / Line 53: @@
 * 12 (w) Name
 * 13 (w) Text string to show in the build list
 * 18 (4xb) Entry point nodes, for planes flying NE, SE, SW, NW.
@@ Line 79: / Line 81: @@
 Overbuilding industries is not known though.
 See action 0 industries for the spec.
 ==Action 4 Airports==

@@ Line 74: / Line 74: @@
 * 31 (d) Safe overbuilds.  Public airports may not be demolished if they are in use by competitors, but this property contains up to four (FF the remaining bytes) airport IDs from the same GRF which may be used to upgrade the airport by overbuilding.
-===Public Airports (counter-proposal; not implemented either)===
+===Public Airports (counter-proposal; implemented)===
 Public Airports are industries with an airport like oilrigs. They can be funded or they can randomly appear e.g. near towns (usual industry location callback). They can be used by every player just like oilrigs.
 No additional properties are needed, the statemachine callback can (if intended) count the number of aircraft of each company using persistent registers, and reject approaching aircraft if one company sends too many at once (i.e. limit aircraft on the airport, instead of membership in orders).
 Overbuilding industries is not known though.
@@ Line 233: / Line 234: @@
 The other states (such as 0F, 10, 12, 15) can still be used to let aircraft grfs know about when they should change speeds, graphics, etc.
 =Overbuilding (not yet implemented)=

← Older revision		Revision as of 20:32, 3 November 2009
Line 73:		Line 73:

	* 31 (d) Safe overbuilds. Public airports may not be demolished if they are in use by competitors, but this property contains up to four (FF the remaining bytes) airport IDs from the same GRF which may be used to upgrade the airport by overbuilding.		* 31 (d) Safe overbuilds. Public airports may not be demolished if they are in use by competitors, but this property contains up to four (FF the remaining bytes) airport IDs from the same GRF which may be used to upgrade the airport by overbuilding.
		+
		+	===Public Airports (counter-proposal; not implemented either)===
		+	Public Airports are industries with an airport like oilrigs. They can be funded or they can randomly appear e.g. near towns (usual industry location callback). They can be used by every player just like oilrigs.
		+	No additional properties are needed, the statemachine callback can (if intended) count the number of aircraft of each company using persistent registers, and reject approaching aircraft if one company sends too many at once (i.e. limit aircraft on the airport, instead of membership in orders).
		+	Overbuilding industries is not known though.
		+

	==Action 4 Airports==		==Action 4 Airports==

@@ Line 155: / Line 155: @@
 :*L = runway length required (0-15)
-:*s = bitmap of valid landing options. It's valid for a vehicle to have none of these bits set if more landing options are added in the (now reserved) extra bits.
+:*s = bitmap of valid landing options.
- Bit Meaning
+::{|border=1 bordercolor=black cellspacing=0 cellpadding=1
-  Aircraft can land on normal runway
+!Bit !!Val !!Meaning
-  Aircraft can land on water runway
+|-
-  Aircraft can land on heliport
+|0
-  Aircraft can load at zeppelin pylon
+|1
-:*xxxxxx = the other bytes are reserved.
+|Aircraft can land on land
 <!-- TODO: what should go in 'uu' in [http://wiki.ttdpatch.net/tiki-index.php?page=VarAction2Vehicles Vehicle Variable 42]?

@@ Line 150: / Line 150: @@
 Aircraft gain an additional property/variable to provide information to the airport state machine:
-==Action 0 Aircraft==
+==Action 0/Var Action 2 Aircraft==
 ===Basic aircraft information===
 *prop 1C/var 4A: Format xxxxxxsL