Docking Instructions - Revision history

Phkb: Updating BB links

2024-02-29T01:35:43Z

Updating BB links

Cholmondely: Added Ian Bell quote

2023-01-09T10:21:47Z

Added Ian Bell quote

Cholmondely: Added Links (docked scenery - unsure if this is the best place for it)

2022-10-27T07:50:49Z

Added Links (docked scenery - unsure if this is the best place for it)

Cholmondely: Links!

2021-01-22T11:07:14Z

Links!

Debresser: Page moved. No need for _ in links.

2016-01-16T20:35:00Z

Page moved. No need for _ in links.

Cim: /* Stage 3 */

2012-07-14T11:52:47Z

‎Stage 3

Cim: /* Stage 2 */

2012-07-14T11:51:07Z

‎Stage 2

Makarius: introduction extended a little

2007-10-10T09:33:58Z

introduction extended a little

Eric Walch: /* Stage 2 */

2007-10-09T12:00:08Z

‎Stage 2

Eric Walch: /* Stage 2 */

2007-10-09T11:59:33Z

‎Stage 2

@@ Line 57: / Line 57: @@
   The first hurdle with docking, as any Commander knows, is getting lined-up with the letterbox (opening slot) of the space station. This was achieved by marking a point out in front of the letterbox with an invisible buoy. However, lining up with the letterbox is the least of a Commander's worries; it's the "boxing" or matching the rotation of the letterbox that really flummoxes.
-  We decided to imagine that there was one "arrow" or vector sticking out of the right wing of the ship and one out of the left side of the space station. As the station rotated, the two vectors described various positions of the hands of a clock. When the vectors pointed in the same direction, it was safe to dock without scraping the craft. Therefore we coded the flight program to minimise at all times the angle between the two vectors. Because the flight program actually manipulated the Cobra, the added bonus was that - if present - yaw boosters were utilised, and the player could still use the Cobra in case of trouble. Needless to say, the next communication from Commander Bell began, "Hello men..."! [http://aegidian.org/bb/viewtopic.php?p=182402#p182402 Gimbal Locke (2012)]
+  We decided to imagine that there was one "arrow" or vector sticking out of the right wing of the ship and one out of the left side of the space station. As the station rotated, the two vectors described various positions of the hands of a clock. When the vectors pointed in the same direction, it was safe to dock without scraping the craft. Therefore we coded the flight program to minimise at all times the angle between the two vectors. Because the flight program actually manipulated the Cobra, the added bonus was that - if present - yaw boosters were utilised, and the player could still use the Cobra in case of trouble. Needless to say, the next communication from Commander Bell began, "Hello men..."! [https://bb.oolite.space/viewtopic.php?p=182402#p182402 Gimbal Locke (2012)]
 == Links ==
-*[http://www.aegidian.org/bb/viewtopic.php?f=4&t=18654 Just an OXP idea: 3D "scenery" when docked] (2017)
+*[https://bb.oolite.space/viewtopic.php?f=4&t=18654 Just an OXP idea: 3D "scenery" when docked] (2017)
 [[Category:Oolite scripting]]

@@ Line 3: / Line 3: @@
 See [[Docking]] for details (and relevant links) of how to actually manage to do it!
-=The AI of the docking ship=
+== The AI of the docking ship ==
-==Stage 1==
+=== Stage 1 ===
 Oolite's AI command "requestDockingCoordinates", looks for the nearest station and guides the ship to its docking port.
 If no station in the system exist it returns: NO_STATION_FOUND
@@ Line 19: / Line 19: @@
 From this only 2, 3, 4 and 5 are important for AI handling. The commsMessage is only seen if the docking ship is  the player and rotation speed is automatically set in the last part of the approach.
-==Stage 2==
+=== Stage 2 ===
  In this stage no coordinates are given. The ship first checks if he is stationary himself and than if the ships are in the right distance from the station (between 1000 and 12500 meters).
@@ Line 32: / Line 32: @@
 If the ship is still to far away to give accurate coordinates (>12500 meter) it returns: APPROACH
-==Stage 3==
+=== Stage 3 ===
 On reaching stage 3 the ship is added to the docking list. From this point on valid approach coordinates in front of the dockingport are calculated and it returns: APPROACH_COORDINATES.  With the coordinates it also sets the approach speed and the desired range. Different ships get assigned positions around the station on at least 500 meters from each-other. One by one the ships are now guided to points more closely to the docking port by giving new approach parameters. In the last phase also a rotation is given on rotating stations. The AI must not set speed or range by himself. If he has to do so for some reason, he always can reset them to the advised values with: "recallDockingInstructions"
@@ Line 39: / Line 39: @@
 The same is true when a ship is killed in the docking procedure. e.g. by smashing into the carrier. The ship stays on the dockinglist and the carrier stays put. The carrier will eventually notice this, but it may take a while. This can be prevented by putting a "abortDocking" command into the death_actions (or [[Oolite JavaScript Reference: Ship script event handlers#shipDied|shipDied]] event) of the ships that are on the carrier. This way it is always sure he is removed from the list. And if he was not on a list the command does nothing.
-=The AI of the station or carrier=
+== The AI of the station or carrier ==
 Whenever a carrier receives a "requestDockingCoordinates" from a ship it goes for a standstill. This could take some time as carriers are usually heavy. In the meantime it issues a "DOCKING_REQUESTED" to his own AI. That should react to jump to a new state were the docking is handled. When the ship came to a standstill it can calculate docking coordinates and thus from this point on is starts sending coordinates tho the waiting ships. From here on it just works as a station.
 In this new state it should wait for the next two events: "DOCKING_COMPLETE" or "DOCKING_ABORTED". This event only happens when the last ship that is on the dockinglist has docked or has aborted.
@@ Line 46: / Line 46: @@
 Return to [[OXP howto AI]]
-= Links =
+== Links ==
 *[http://www.aegidian.org/bb/viewtopic.php?f=4&t=18654 Just an OXP idea: 3D "scenery" when docked] (2017)
 [[Category:Oolite scripting]]

← Older revision		Revision as of 07:50, 27 October 2022
Line 45:		Line 45:

	Return to [[OXP howto AI]]		Return to [[OXP howto AI]]
		+
		+
		+	= Links =
		+	*[http://www.aegidian.org/bb/viewtopic.php?f=4&t=18654 Just an OXP idea: 3D "scenery" when docked] (2017)

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

← Older revision		Revision as of 11:07, 22 January 2021
Line 1:		Line 1:
−	AI-Docking Instructions for Oolite ships. See ~~the~~ [[~~Pilot's Reference Manual~~]] for ~~not-AI based docking or check out the [[Docking Computers\|docking computer]].~~	+	AI-Docking Instructions for Oolite ships.
		+
		+	See [[Docking]] for details (and relevant links) of how to actually manage to do it!

	=The AI of the docking ship=		=The AI of the docking ship=

@@ Line 35: / Line 35: @@
 By issuing a "requestDockingCoordinates" the ship is added on the waitinglist for being handled by the station. If the ship for some reason aborts the docking it must issue a "abortDocking" command. This removes the ship from the waiting list. If it is not done the carrier could wait indefinitely for the last ship.
-The same is true when a ship is killed in the docking procedure. e.g. by smashing into the carrier. The ship stays on the dockinglist and the carrier stays put. The carrier will eventually notice this, but it may take a while. This can be prevented by putting a "abortDocking" command into the death_actions (or [[Oolite_JavaScript_Reference:_ship_script_event_handlers#shipDied|shipDied]] event) of the ships that are on the carrier. This way it is always sure he is removed from the list. And if he was not on a list the command does nothing.
+The same is true when a ship is killed in the docking procedure. e.g. by smashing into the carrier. The ship stays on the dockinglist and the carrier stays put. The carrier will eventually notice this, but it may take a while. This can be prevented by putting a "abortDocking" command into the death_actions (or [[Oolite JavaScript Reference: Ship script event handlers#shipDied|shipDied]] event) of the ships that are on the carrier. This way it is always sure he is removed from the list. And if he was not on a list the command does nothing.
 =The AI of the station or carrier=

@@ Line 20: / Line 20: @@
  In this stage no coordinates are given. The ship first checks if he is stationary himself and than if the ships are in the right distance from the station (between 1000 and 12500 meters).
-If an other ship is in launching status it returns: TRY_AGAIN_LATER
+If another ship is in launching status or another temporary condition preventing docking is in effect it returns: TRY_AGAIN_LATER
 If the station or carrier is moving to fast or is turning to fast with a non-rotating station it returns: HOLD_POSITION

← Older revision		Revision as of 09:33, 10 October 2007
Line 1:		Line 1:
−	Docking Instructions for Oolite ships	+	AI-Docking Instructions for Oolite ships. See the [[Pilot's Reference Manual]] for not-AI based docking or check out the [[Docking Computers\|docking computer]].

	=The AI of the docking ship=		=The AI of the docking ship=

@@ Line 26: / Line 26: @@
 If the ship is already to close to give accurate coordinates (<1000 meter) it returns: BACK_OFF
-If the ship is still too far away to give accurate coordinates (>12500 meter) it returns: APPROACH
+If the ship is still to far away to give accurate coordinates (>12500 meter) it returns: APPROACH
 ==Stage 3==