forked from Marginal/AutoGate
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathReadMe.html
298 lines (262 loc) · 27.3 KB
/
ReadMe.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
<meta content="Animated jetway and docking guidance system for X-Plane scenery package developers">
<meta content="X-Plane, simulator, scenery" name="keywords">
<title>AutoGate</title>
<meta content="Jonathan Harris" name="author">
<style type="text/css">
.banner { font-family: Arial,Helvetica,sans-serif; background-color: lightskyblue; text-align: left; height: 32px; }
.dnl { font-family: Arial,Helvetica,sans-serif; font-size: small; background-color: lightskyblue; }
samp { font-family: Arial,Helvetica,sans-serif; }
h2 { font-family: Arial,Helvetica,sans-serif; }
h3 { font-family: Arial,Helvetica,sans-serif; }
h4 { font-family: Arial,Helvetica,sans-serif; }
h5 { font-family: Arial,Helvetica,sans-serif; }
dt { margin: 5px 0 5px 0; }
li { margin: 5px 0 5px 0; }
kbd {font-family: sans-serif; color: black; background-color: white; border: 1px solid black; -webkit-border-radius:5px; -moz-border-radius:5px; border-radius: 5px; padding: 2px 3px 0px; }
</style>
</head>
<body>
<table style="width: 100%;" border="0" cellpadding="2">
<tbody>
<tr>
<td class="banner">Marginal → <a href="http://marginal.org.uk/x-planescenery/">X-Plane Scenery</a> → <a href="http://marginal.org.uk/x-planescenery/tools.html">Tools</a> → AutoGate</td>
</tr>
</tbody>
</table>
<hr>
<h2>AutoGate jetway and docking guidance system kit for X-Plane<small><sup>®</sup></small></h2>
<h3>Overview</h3>
<p>This kit allows X-Plane scenery designers to add animated jetway and docking guidance systems (DGS) to scenery packages. Two types of jetway and four types of DGS are included.</p>
</p>
<p>The jetway animates to “dock” with the plane's main door when the pilot engages the parking brake and shuts down the plane's engines with the plane within ½m of the correct stopping position. The DGS guides the pilot to the correct stopping position.</p>
<p> An <a href="http://marginal.org.uk/x-planescenery/AutoGate%20Demo.zip">example</a> scenery package built using this kit is available. Please see the notes <a href="#upgrade">below</a> if you're upgrading from an earlier of this kit.</p>
<h3>How it works</h3>
<p>The jetways and DGSs are standard X-Plane scenery objects that you place in your scenery package using <a href="http://marginal.org.uk/x-planescenery/tools.html#overlayeditor" target="_blank">OverlayEditor</a> <small>(version 2.48 or later recommended)</small> or <a href="http://developer.x-plane.com/tools/worldeditor/" target="_blank">WED</a> <small>(version 1.1r1 or later recommended)</small>. They are animated by X-Plane custom datarefs which are supplied by a plugin.</p>
<p>The plugin needs to know the type of aircraft that the user is piloting and the location of its main boarding door. The plugin reads this information from the “ICAO code” and “boarding door location” values in the ACF file of the aircraft that the user is piloting. These values can be edited on the Standard → Viewpoint screen in Plane-Maker. If the ACF file does not have this information correctly recorded then the DGS will display “ID FAIL” and the jetway will remain in the retracted position.</p>
<p>The system is designed so that it imposes no more load on X-Plane than normal “static” scenery objects unless the user's viewpoint is within 1000m of a jetway or 500m of a DGS, in which case the load remains very modest. If the plugin is not installed then the DGS and jetway objects will behave as if they were normal “static” scenery objects.</p>
<h3>Usage</h3>
<p>Download and install the AutoGate <a href="http://marginal.org.uk/x-planescenery/AutoGate.zip">plugin</a>. Installation instructions are in the file <code>ReadMe.txt</code> included.</p>
<p>Please do not re-distribute the plugin with your scenery package; ask your users to download it from <a href="http://marginal.org.uk/x-planescenery/AutoGate.zip">http://marginal.org.uk/x-planescenery/AutoGate.zip</a> instead. This ensures that they have the latest version. <small>(Future versions of the plugin may support more jetways and/or DGSs, but will remain backwards-compatible)</small>.</p>
<h4><a id="jetway">Jetways</a></h4>
<p>Two types of animated jetway are supplied:<p>
<table>
<tfoot>
<tr>
<th> </th>
<th>Glass jetway</th>
<th>Steel jetway</th>
</tr>
</tfoot>
<tbody>
<tr>
<td></td>
<td><img alt="Glass jetway screenshot" src="imgs/glass.jpeg"></td>
<td><img alt="Steel jetway screenshot" src="imgs/steel.jpeg"></td>
</tr>
</tbody>
</table>
<p>In four orientations:</p>
<table>
<tfoot>
<tr>
<th> </th>
<th>Default</th>
<th>Straight</th>
<th>Perpendicular</th>
<th>Short</th>
</tr>
</tfoot>
<tbody>
<tr>
<td></td>
<td><img alt="AutoGate default screenshot" src="imgs/AutoGate.jpeg"></td>
<td><img alt="AutoGate straight screenshot" src="imgs/AutoGate-straight.jpeg"></td>
<td><img alt="AutoGate perpendicular screenshot" src="imgs/AutoGate-perpendicular.jpeg"></td>
<td><img alt="AutoGate short screenshot" src="imgs/AutoGate-short.jpeg"></td>
</tr>
</tbody>
</table>
<p>Various versions of these jetway objects are supplied in this kit's <code>Jetways-Glass</code> and <code>Jetways-Steel</code> folders, named <code>AutoGate-<i>l</i>m-glass.obj</code>, <code>AutoGate-straight-<i>l</i>m-glass.obj</code>, <code>AutoGate-perpendicular-<i>l</i>m-glass.obj</code>, <code>AutoGate-short-<i>l</i>m-glass.obj</code> and <code>AutoGate-<i>l</i>m-steel.obj</code>, <code>AutoGate-straight-<i>l</i>m-steel.obj</code>, <code>AutoGate-perpendicular-<i>l</i>m-steel.obj</code>, <code>AutoGate-short-<i>l</i>m-steel.obj</code>. These differ in the (approximate) length <i><code>l</code></i> of the jetway in its retracted position. You don't need to distribute all of these objects with your scenery package - only the ones that you use.</p>
<p>To place an animated jetway into your scenery package:</p>
<ul>
<li>First, copy one or more of the <code>AutoGate-*.obj</code> jetway objects from the <code>Jetways-Glass</code> and/or <code>Jetways-Steel</code> folders into your scenery package:
<ul>
<li>OverlayEditor: Drag the jetway object(s) from the <code>Jetways-Glass</code> or <code>Jetways-Steel</code> folder and drop onto OverlayEditor's <samp>list of objects</samp>.</li>
<li>WED: Use Finder or Explorer to copy the jetway object(s) plus the associated textures <code>AutoGate2.dds</code> + <code>AutoGate2_LIT.dds</code> from the <code>Jetways-Glass</code> or <code>Jetways-Steel</code> folder into your scenery package folder.</li>
</ul>
Alternatively, just copy the entire <code>Jetways-Glass</code> and/or <code>Jetways-Steel</code> folder(s) into your scenery package (but don't forget to strip out unused objects before distributing, <i>e.g.</i> using the <a href="http://marginal.org.uk/x-planescenery/tools.html#xpublish" target="_blank">X-Publish</a> tool).</li>
<li>Place a static aircraft for reference into your scenery package with the position and heading that you want the user's aircraft to have when it's stopped at the gate/stand that you're modelling.<br>
In the screenshots above I've used <code>lib/airport/aircraft/heavy_metal/747_United.obj</code> from X-Plane 10's built-in library, but if you're designing for a regional airport or terminal you should use a smaller aircraft, <i>e.g.</i> <code>opensceneryx/aircraft/jets/hevay/a320.obj</code>.</li>
<li>Note the reference aircraft's heading in the status bar (OverlayEditor) or attributes pane (WED).</li>
<li>If you're using OverlayEditor select the reference aircraft and press <kbd>Shift</kbd> <kbd>C</kbd> to align your view with it.</li>
<li>Place one of the jetway objects:
<ul>
<li>With the same heading as the reference aircraft.</li>
<li>With the origin aligned with the reference aircraft's centreline.</li>
<li>With the jetway door lined up with the reference aircraft's boarding door.</li>
</ul>
You will likely have to experiment with different orientations and lengths of jetway objects to find one that best fits the space while complying with these constraints.</li>
<li>To visualise the jetway object's origin:
<table>
<tbody>
<tr>
<td></td>
<td>OverlayEditor: Select the jetway object and press <kbd>C</kbd>.<br>
The red cursor jumps to the jetway object's origin:</td>
<td>WED: Select the jetway object using the <samp>Vertex</samp> tool.<br>
The yellow cursor shows the jetway object's origin:</td>
</tr>
<tr>
<td> </td>
<td><img alt="OverlayEditor screenshot" src="imgs/AG-OE.jpeg"></td>
<td><img alt="WED screenshot" src="imgs/AG-WED.jpeg"></td>
</tr>
</tbody>
</table>
</li>
<li>The pilot will find it difficult to line-up at the gate without a lead-in apron line so you may wish to add one and connect it to the taxi network. The lead-in line should pass through the jetway object's origin. (According to ICAO Annex 14 gate lead-in lines should, like taxi lines, be solid yellow).</li>
<li>Place only one animated jetway at each gate. If you are modelling a complicated gate with multiple jetways the additional jetways must be static; use the <code>StaticGate-*.obj</code> jetway objects described <a href="#static">below</a>. <small>(This limitation exists in part because the X-Plane ACF file only specifies one boarding door location)</small>. The <a href="http://marginal.org.uk/x-planescenery/AutoGate%20Demo.zip">example</a> scenery package contains a gate of this configuration.
<li>If you want to designate this gate as a “Ramp Start” then place the Ramp Start at the stopping position / jetway object origin and change its type to “Gate”.<br>
<small>Note: X-Plane v9 doesn't support Ramp Start types, and places aircraft with their center of gravity at the Ramp Start location; so if designing for v9 place the Ramp Start well back from the stopping position / jetway object origin.</small></li>
<li>Place the animated jetway objects with their origins more than 20m away from any other AutoGate animated jetways.</li>
</ul>
<h4><a id="dgs">Docking Guidance Systems</a></h4>
<p>Use of a DGS is optional - the animated jetways work fine without it - but the pilot will find it difficult to stop the aircraft at the correct position if you don't include a DGS.</p>
<p>Four types of DGS are supplied:</p>
<table>
<tfoot>
<tr>
<th> </th>
<th>Safegate<small><sup>®</sup></small> inductive-loop DGS</th>
<th>Safedock<small><sup>®</sup></small>2S advanced DGS</th>
<th>Safedock<small><sup>®</sup></small>T2 advanced DGS</th>
<th>Human marshaller</th>
</tr>
</tfoot>
<tbody>
<tr>
<td></td>
<td><img alt="Safegate screenshot" src="imgs/Safegate.jpeg"></td>
<td><img alt="Safedock2S screenshot" src="imgs/Safedock2S.jpeg"></td>
<td><img alt="SafedockT2 screenshot" src="imgs/SafedockT2.jpeg"></td>
<td><img alt="Marshaller screenshot" src="imgs/Marshaller.jpeg"></td>
</tr>
</tbody>
</table>
<p>Various versions of the DGS objects are supplied in this kit's <code>DGSs-Safegate</code>, <code>DGSs-Safedock2S</code>, <code>DGSs-SafedockT2</code> and <code>DGSs-Marshaller</code> folders, named <code>Safegate-<i>h</i>m<i>[-pole]</i>.obj</code>, <code>Safedock2S-<i>h</i>m<i>[-pole]</i>.obj</code>, <code>SafedockT2-<i>h</i>m<i>[-pole]</i>.obj</code> and <code>Marshaller.obj</code>. These differ in the height <code><i>h</i></code> of the DGS above the ground, and whether the DGS is mounted on a pole. Gates intended for heavies will need the taller DGSs. You don't need to distribute all of these objects with your scenery package - only the ones that you use.</p>
<p>To add a DGS to your gate:</p>
<ul>
<li>First, copy one or more of the DGS objects from the <code>DGSs-Safegate</code>, <code>DGSs-Safedock2S</code>, <code>DGSs-SafedockT2</code> and/or <code>DGSs-Marshaller</code> folder into your scenery package:
<ul>
<li>OverlayEditor: Drag the object(s) from the <code>DGSs-Safegate</code>, <code>DGSs-Safedock2S</code>, <code>DGSs-SafedockT2</code> or <code>DGSs-Marshaller</code> folder and drop onto OverlayEditor's <samp>list of objects</samp>.</li>
<li>WED: Use Finder or Explorer to copy the DGS object(s) plus the associated textures (<code>Safegate.dds</code> + <code>Safegate_LIT.dds</code>, <code>Safedock2S.dds</code> + <code>Safedock2S_LIT.dds</code>, <code>SafedockT2.dds</code> + <code>SafedockT2_LIT.dds</code> or <code>Marshaller.dds</code> + <code>Marshaller_LIT.dds</code>) from the <code>DGSs-Safegate</code>, <code>DGSs-Safedock2S</code>, <code>DGSs-SafedockT2</code> or <code>DGSs-Marshaller</code> folder into your scenery package folder.</li>
</ul>
Alternatively, just copy the entire <code>DGSs-Safegate</code>, <code>DGSs-Safedock2S</code>, <code>DGSs-SafedockT2</code> and/or <code>DGSs-Marshaller</code> folder(s) into your scenery package (but don't forget to strip out unused objects before distributing, <i>e.g.</i> using the <a href="http://marginal.org.uk/x-planescenery/tools.html#xpublish" target="_blank">X-Publish</a> tool).</li>
<li>Place the DGS objects in your scenery package just like any other 3D object. For correct operation the DGSs must be placed with the same heading as the jetways, which is the same heading that the aircraft will have when it is stopped at the gate/stand.</li>
<li>The DGS objects must be placed within this zone relative to the jetway object's origin and heading:
<table>
<tbody>
<tr>
<td><img alt="OverlayEditor screenshot" src="imgs/DGS-OE.jpeg"></td>
<td><img alt="WED screenshot" src="imgs/DGS-WED.jpeg"></td>
</tr>
</tbody>
</table>
</li>
<li>The older Safegate DGS works by parallax and so must be placed directly ahead of the pilot's seat.</li>
<li>There's a <code>greenzone.obj</code> object in the <code>Helpers</code> folder to help you with DGS positioning - place this object with the same origin and heading as the jetway object.</li>
<li>Place the DGS objects such that they are not inside the “green zone” of any any other AutoGate animated jetways.</li>
<li>The DGS will remain blank or will display incorrect information if it is not placed next to an AutoGate jetway.</li>
</ul>
<h4><a id="standalone">Stand-alone Docking Guidance Systems</a></h4>
<p>You can also place a DGS without an accompanying animated jetway, <i>e.g.</i> at an apron parking stand.</p>
<ul>
<li>Follow the process described <a href="#jetway">above</a> for adding jetways but, instead of placing a jetway object at the aircraft's stopping point, place the supplied <code>StoppingPoint.obj</code> object supplied in this in this kit's <code>Standalone</code> folder instead:
<table>
<tbody>
<tr>
<td><img alt="StoppingPoint screenshot" src="imgs/StoppingPoint.jpeg"></td>
</tr>
</tbody>
</table>
</li>
<li>Place the <code>StoppingPoint.obj</code> object with the position and heading that you want the user's aircraft to have when it's stopped at the stand that you're modelling.</li>
<li>Place the DGS object in the “green zone” relative to the <code>StoppingPoint.obj</code> object's origin and heading.</li>
</ul>
<h4><a id="static">Static Objects</a></h4>
<p>Various static objects are supplied in this kit's <code>Jetways-Glass</code> and <code>Jetways-Steel</code> folders:</p>
<dl>
<dt><code>StaticGate-<i>l</i>m-glass.obj</code>, <code>StaticGate-perpendicular-<i>l</i>m-glass.obj</code>, <code>StaticGate-short-<i>l</i>m-glass.obj</code>, <code>StaticGate-straight-<i>l</i>m-glass.obj</code>, <code>StaticGate-<i>l</i>m-steel.obj</code>, <code>StaticGate-perpendicular-<i>l</i>m-steel.obj</code>, <code>StaticGate-short-<i>l</i>m-steel.obj</code> and <code>StaticGate-straight-<i>l</i>m-steel.obj</code></dt>
<dd>Static versions of the AutoGate jetways. These can be used when a static aircraft is parked at a gate. These can also be used in conjunction with a single AutoGate animated jetway at a gate which has multiple jetways.</dd>
<dt><code>JetwayExt-<i>l</i>m-glass.obj</code> and <code>JetwayExt-<i>l</i>m-steel.obj</code></dt>
<dd>Jetway extensions with a supporting pillar at one end.</dd>
<dt><code>JetwayCon-<i>l</i>m-glass.obj</code> and <code>JetwayCon-<i>l</i>m-steel.obj</code></dt>
<dd>Jetway connectors with no supporting pillar.</dd>
</dl>
<p>Similarly, various static DGS objects are supplied in this kit's <code>DGSs-Safegate</code>, <code>DGSs-Safedock2S</code>, <code>DGSs-SafedockT2</code> and <code>DGSs-Marshaller</code> folders that can be used when a static aircraft is parked at a gate.</p>
<p>You don't need to distribute all of these objects with your scenery package - only the ones that you use.</p>
<h3><a id="customisation">Customisation</h3>
<h4>Jetways</h4>
<p>The static and animated glass and steel jetway objects share common texture files <code>AutoGate2.dds</code> and <code>AutoGate2_LIT.dds</code> in the <code>Jetways-Glass</code> and <code>Jetways-Steel</code> folders. You can edit or replace these files in your scenery package folder. These files are very modestly sized; consider doubling their size if you want to add more detail. The file <code>PaintKit.png</code> in the <code>Helpers</code> folder describes how the textures in these files map to the jetway objects.</p>
<p>You can edit the object files in a text editor to change the name of the texture files specified in the <code><a href="http://developer.x-plane.com/?article=obj8-file-format-specification#TEXTURE_lttex_file_namegt" target="_blank">TEXTURE<a></code> and <code><a href="http://developer.x-plane.com/?article=obj8-file-format-specification#TEXTURE_LIT_lttex_file_namegt" target="_blank">TEXTURE_LIT<a></code> statements, and save the object with a different filename. This allows you to have a mix of differently textured jetways. <small>(Note that the spacing rules described above still apply irrespective of the objects' filenames)</small>.</p>
<p>The static, animated and extension/connector glass jetways are drawn in “<a href="http://developer.x-plane.com/?article=obj8-file-format-specification#ATTR_layer_group_ltnamegt_ltoffsetgt" target="_blank">layer group</a>” <code>objects+4</code>, <code>objects+3</code> and <code>objects+2</code> respectively, so that other scenery objects (which are normally drawn in layer group <code>objects+0</code>) can be viewed through the glass windows. If you have a number of glass objects at a gate you may need to change the <code>ATTR_layer_group objects <i>n</i></code> statements in some of the object files to change their relative drawing order; <i>i.e.</i> so that objects further from the terminal building are drawn later than objects closer to the terminal building.</p>
<h4>Custom Jetway models</h4>
<p>You can use your own animated jetway objects instead of or in addition to the supplied objects. Your objects must be modelled to conform to the following constraints:</p>
<ul>
<li>Passengers stepping off the jetway onto the aircraft would be walking in the direction of the x axis - <i>i.e.</i> imagine the aircraft to be parked pointing along the y axis in your 3D modelling app.</li>
<li>When the jetway is idle, the centre of the leading edge of the floor of the entrance must be at -7.5m on the x axis, 0m on the y axis, and +4.0m on the z (vertical) axis in your 3D modelling app.</li>
<li>The entrance must be animated to rise vertically by 1m when the DataRef <code>marginal.org.uk/autogate/vert</code> value increases by 1.0, and fall by 1m when the DataRef value decreases by 1.0.</li>
<li>The entrance must be animated to move +1m towards the aircraft along the x axis when the DataRef <code>marginal.org.uk/autogate/lat</code> value increases by 1.0.</li>
<li>The rest of your jetway must be animated to smoothly follow the movements of the entrance.</li>
<li>The DataRef <code>marginal.org.uk/autogate/moving</code> has value 1.0 while the jetway is moving, otherwise 0.0. You can use this to display an animation while the jetway is moving - <i>e.g.</i> the supplied jetway objects use this DataRef in an “<a href="http://developer.x-plane.com/?article=obj8-file-format-specification#ANIM_hide_ltv1gt_ltv2gt_ltdatarefgt" target="_blank">ANIM_hide</a>” statement to display an <code>airplane_beacon</code> “<a href="http://developer.x-plane.com/?article=obj8-file-format-specification#LIGHT_NAMED_ltnamegt_ltxgt_ltygt_ltzgt" target="_blank">named light</a>” while the jetway is moving.</li>
<li>Jetways that contain transparency should be drawn in “<a href="http://developer.x-plane.com/?article=obj8-file-format-specification#ATTR_layer_group_ltnamegt_ltoffsetgt" target="_blank">layer group</a>” <code>objects+1</code> or later so that other scenery objects (which are normally drawn in layer group <code>objects+0</code>) can be viewed through the glass windows.</li>
<li>Consider including a static lower level-of-detail version of the jetway in your model, visible from distances greater than <i>e.g.</i> 1000m.</li>
</ul>
<p>You can use the Blender 2.4 models for the jetways supplied in this kit as an example or starting point - they are available as<code>.blend</code> files <a href="https://github.com/Marginal/AutoGate/tree/master/Jetways-Glass" target="_blank">here</a>.
<h4>Docking Guidance Systems</h4>
<p>The supplied DGSs are not designed to be customisable. However the plugin publishes various datarefs that you can use to construct your own DGS. Contact the <a href="mailto:[email protected]">author</a> if you would like more information.</p>
<h3><a id="upgrade">Upgrading from version 1.2 and earlier of this kit</a></h3>
<p>This kit and the associated AutoGate plugin require X-Plane version 9 or later. If you're designing a scenery package for X-Plane 8 then you should stick with a previous version of this kit and of the AutoGate plugin.</p>
<p>The DGS objects in the <code>DGSs-Safedock2S</code> and <code>DGSs-Safegate</code> folders are drop-in replacements for older objects of the same name, but use higher quality DDS textures. Use OverlayEditor's <samp>Import</samp> button, or use Finder or Explorer to replace your existing DGS objects and textures. Delete the old PNG textures <code>Safedock2S.png</code>, <code>Safedock2S_LIT.png</code>, <code>Safegate.png</code> and <code>Safegate_LIT.png</code> from your scenery package folder.</p>
<p>There are no direct replacement for the old <code>AutoGate.obj</code> and <code>AutoGate-angled.obj</code> objects, but:</p>
<ul>
<li><code>Jetways-Steel/AutoGate-straight-20m-steel.obj</code> plus <code>Jetways-Steel/JetwayExt-10m-steel.obj</code> take up roughly the same space as the old <code>AutoGate.obj</code>.</li>
<li><code>Jetways-Steel/AutoGate-20m-steel.obj</code> plus <code>Jetways-Steel/JetwayExt-10m-steel.obj</code> take up roughly the same space as the old <code>AutoGate-angled.obj</code>.</li>
</ul>
<p>You can mix old and new objects in your scenery package. <small>(Note that the spacing rules described above still apply irrespective of whether objects are old or new)</small>.</p>
<h3>Upgrading from version 1.3 or later of this kit</a></h3>
<p>If you'd like your existing scenery package to take advantage of the latest objects, and you haven't renamed or customised any of the supplied files, then just overwrite any existing files in your scenery package with the latest files from this kit of the same name. You will need to replace the textures as well as the objects. (Note that the different types of DGSs and jetways were split out into different folders in version 1.60 of this kit, so you may have to look in more than one folder to find the replacement files).</p>
<p>If you've renamed and/or customised any of the supplied objects then may want to be more selective in replacing files, and/or re-apply your customisations. This is the list of what has changed and when:</p>
<ul>
<li>All of the <code>AutoGate-<i>d</i>m-glass</code>, <code>JetwayCon-<i>d</i>m-glass</code>, <code>JetwayExt-<i>d</i>m-glass</code> and <code>StaticGate-<i>d</i>m-glass</code> objects the <code>Jetways-Glass</code> folder were re-modelled in version 1.40 to add night lighting.<br>
The re-modelled objects require the updated <code>AutoGate2.dds</code> texture in that folder.</li>
<li>All of the <code>AutoGate-<i>d</i>m-*</code> and <code>AutoGate-straight-<i>d</i>m-*</code> objects in the <code>Jetways-Glass</code> and <code>Jetways-Steel</code> folders were re-modelled in version 1.50 to add a ground-level beacon.<br>
(The <code>AutoGate2.dds</code> and <code>AutoGate2_LIT.dds</code> textures in those folders were unchanged).</li>
<li>Some of the <code>AutoGate-perpendicular-*</code> objects in the <code>Jetways-Glass</code> and <code>Jetways-Steel</code> folders were re-modelled in version 1.60 to correct their animation.<br>
(The <code>AutoGate2.dds</code> and <code>AutoGate2_LIT.dds</code> textures in those folders were unchanged).</li>
<li>All of the <code>Safedock2S-*</code> objects in the <code>DGSs-Safedock2S</code> folder were re-modelled in version 1.60 to display arbitrary aircraft ICAO designations.<br>
The re-modelled objects require the updated <code>Safedock2S.dds</code> and <code>Safedock2S_LIT.dds</code> textures in that folder.</li>
<li>All of the <code>SA-*</code> stand-alone DGS objects were removed in version 1.70. Existing <code>SA-*</code> objects in your scenery package will continue to work, but you should start creating stand-alone DGSs using the method described <a href="#standalone">above</a>.</li>
</ul>
<h3>Acknowledgements</h3>
<p>“X-Plane” is a registered trademark of <a href="http://www.x-plane.com/">Laminar Research</a>.</p>
<p>“Safedock” and “Safegate” are registered trademarks of <a href="http://www.safegate.com/" target="_blank">Safegate Group</a>. Safegate Group is not associated with and does not endorse this scenery kit.</p>
<p>Marshaller figure courtesy of <a href="http://hosting.x-plane.org/mr3d/website/" target="_blank">Mr 3D</a>.</p>
<h3>License</h3>
<p>This kit is licensed under the Creative Commons <a rel="license" href="http://creativecommons.org/licenses/by/3.0/">Attribution</a> license. In short, you can use any part of this kit (including the 3D objects and their textures) in original or modified form in a free or commerical scenery package, but you must give the author credit.<p>
<p>The author would appreciate a courtesy copy of any commercial scenery that you make using this kit, but you are under no obligation.</p>
<p>The associated <a href="http://marginal.org.uk/x-planescenery/AutoGate.zip">plugin</a> is licensed under the GNU <a rel="license" target="_blank" href="http://www.gnu.org/licenses/lgpl-2.1-standalone.html">LGPL v2.1</a> license.</p>
<hr>
<table style="width: 100%;" border="0" cellpadding="2">
<tbody>
<tr>
<td class="banner">Version 1.72 © 2006-2016 <a href="mailto:[email protected]">Jonathan Harris</a>
<a rel="license" href="http://creativecommons.org/licenses/by/3.0/"><img style="border: 0px solid ; width: 88px; height: 31px; vertical-align: text-bottom;" alt="Creative Commons License" src="http://i.creativecommons.org/l/by/3.0/88x31.png"></a></td> </tr>
</tbody>
</table>
</body>
</html>