Landing Trigger - Revision history

BASys: Replaced Applicable-FSVersion for MSFS with MSFS2020, added MSFS2024

2024-05-25T17:49:26Z

Replaced Applicable-FSVersion for MSFS with MSFS2020, added MSFS2024

← Older revision		Revision as of 12:49, 25 May 2024
Line 4:		Line 4:

	{{Infobox-Applicable-FSVersion		{{Infobox-Applicable-FSVersion
	\| ~~MSFS~~ = true		\| MSFS2024 = unknown
			\| MSFS2020 = true
	\| FSXI = false		\| FSXI = false
	\| P3D5 = false		\| P3D5 = false

Mr LiamT: /* Related */ Update calculator link

2021-11-15T09:15:58Z

Related: Update calculator link

← Older revision		Revision as of 04:15, 15 November 2021
Line 47:		Line 47:
	== Related ==		== Related ==
	* You can use a [[Property Trigger]] to trigger at a specific speed after landing instead of using a '''full stop''' landing type, which triggers at ~25 kts.		* You can use a [[Property Trigger]] to trigger at a specific speed after landing instead of using a '''full stop''' landing type, which triggers at ~25 kts.
	* You can use a [[calculator]] for relevant copilot feedback after landing.		* You can use a [[MSFS_Mission_Script_-_Calculator\|calculator]] for relevant copilot feedback after landing.
	* You can use a global '''AreaLandingTrigger''' and another '''LandingTrigger''' together to detect landings at the wrong place. Just make it so the '''AreaLandingTrigger''' gets disabled when the user is in the appropriate area and is re-enabled when they exit. You can use a [[Proximity Trigger\|ProximityTrigger]] for this.		* You can use a global '''AreaLandingTrigger''' and another '''LandingTrigger''' together to detect landings at the wrong place. Just make it so the '''AreaLandingTrigger''' gets disabled when the user is in the appropriate area and is re-enabled when they exit. You can use a [[Proximity Trigger\|ProximityTrigger]] for this.

Mr LiamT at 14:53, 17 October 2021

2021-10-17T14:53:54Z

← Older revision		Revision as of 09:53, 17 October 2021
Line 49:		Line 49:
	* You can use a [[calculator]] for relevant copilot feedback after landing.		* You can use a [[calculator]] for relevant copilot feedback after landing.
	* You can use a global '''AreaLandingTrigger''' and another '''LandingTrigger''' together to detect landings at the wrong place. Just make it so the '''AreaLandingTrigger''' gets disabled when the user is in the appropriate area and is re-enabled when they exit. You can use a [[Proximity Trigger\|ProximityTrigger]] for this.		* You can use a global '''AreaLandingTrigger''' and another '''LandingTrigger''' together to detect landings at the wrong place. Just make it so the '''AreaLandingTrigger''' gets disabled when the user is in the appropriate area and is re-enabled when they exit. You can use a [[Proximity Trigger\|ProximityTrigger]] for this.

	{{:Transclusion_MSFS_Mission_Script_-_Triggers}}		{{:Transclusion_MSFS_Mission_Script_-_Triggers}}


	{{Template:Navbox-Mission-Creation-MSFS}}		{{Template:Navbox-Mission-Creation-MSFS}}

Mr LiamT: Added mission navbox

2021-10-17T14:50:54Z

Added mission navbox

← Older revision		Revision as of 09:50, 17 October 2021
Line 49:		Line 49:
	* You can use a [[calculator]] for relevant copilot feedback after landing.		* You can use a [[calculator]] for relevant copilot feedback after landing.
	* You can use a global '''AreaLandingTrigger''' and another '''LandingTrigger''' together to detect landings at the wrong place. Just make it so the '''AreaLandingTrigger''' gets disabled when the user is in the appropriate area and is re-enabled when they exit. You can use a [[Proximity Trigger\|ProximityTrigger]] for this.		* You can use a global '''AreaLandingTrigger''' and another '''LandingTrigger''' together to detect landings at the wrong place. Just make it so the '''AreaLandingTrigger''' gets disabled when the user is in the appropriate area and is re-enabled when they exit. You can use a [[Proximity Trigger\|ProximityTrigger]] for this.
			{{:Transclusion_MSFS_Mission_Script_-_Triggers}}

	{{:~~Transclusion_MSFS_Mission_Script_~~-~~_Triggers~~}}
			{{Template:Navbox-Mission-Creation-MSFS}}

Mr LiamT: Renamed related, clarified, added trigger transclusion.

2021-10-13T13:56:18Z

Renamed related, clarified, added trigger transclusion.

← Older revision		Revision as of 08:56, 13 October 2021
Line 45:		Line 45:
	* Complete an objective.		* Complete an objective.

	== Related ~~elements and alternatives~~ ==		== Related ==
	* A [[Property Trigger]] ~~so you can choose an~~ after-landing ~~speed~~ instead of a '''full stop''' landing type.		* You can use a [[Property Trigger]] to trigger at a specific speed after landing instead of using a '''full stop''' landing type, which triggers at ~25 kts.
	* You can use a [[calculator]] for relevant copilot feedback after landing.		* You can use a [[calculator]] for relevant copilot feedback after landing.
	* You can use a global '''AreaLandingTrigger''' and another '''LandingTrigger''' together to detect landings at the wrong place. Just make it so the '''AreaLandingTrigger''' gets disabled when the user is in the appropriate area and is re-enabled when they exit. You can use a [[Proximity Trigger\|ProximityTrigger]] for this.		* You can use a global '''AreaLandingTrigger''' and another '''LandingTrigger''' together to detect landings at the wrong place. Just make it so the '''AreaLandingTrigger''' gets disabled when the user is in the appropriate area and is re-enabled when they exit. You can use a [[Proximity Trigger\|ProximityTrigger]] for this.

			{{:Transclusion_MSFS_Mission_Script_-_Triggers}}

Mr LiamT: Created page for landing triggers

2021-10-11T21:06:43Z

Created page for landing triggers

New page

[[Category:MSFS Mission Script]]

{{:Ambox-Content-WIP}}

{{Infobox-Applicable-FSVersion
| MSFS = true
| FSXI = false
| P3D5 = false
| P3D4 = false
| P3D3 = false
| P3D2 = false
| P3D = false
| FSW = false
| FSXSE = false
| FSXA = false
| FSX = false
| FS2004 = false
| FS2002 = false
| XP11 = false
| XP10 = false
| XP9 = false
}}
Detect landings in an area or on a runway.
{{Infobox-MSFS-Script-Element
| category = Triggers
| name = AirportLandingTrigger / AreaLandingTrigger
| short-descr = Fires when an object lands in one of the areas/airports/runways specified.
}}
!LandingType
|The type of landing can be; a '''touchdown''', it triggers when the plane makes a touchdown (the main gear carrying weight), a '''full stop''' happens when the plane slows down to ~25 kts.
|-
!Area
|You can link it to [[MSFS Mission Script - Areas|areas]] in which the trigger should be active. If no area is selected, the whole world will be active.
|-
!AirportIdent
|Airport ICAO identifier used in the sim.
|-
!RunwayFilter
|Number and designator of the runway for which the trigger should be active.
{{Infobox-MSFS-Script-Element-End}}

== Possible uses ==
* Copilot feedback.
* Complete an objective.

== Related elements and alternatives ==
* A [[Property Trigger]] so you can choose an after-landing speed instead of a '''full stop''' landing type.
* You can use a [[calculator]] for relevant copilot feedback after landing.
* You can use a global '''AreaLandingTrigger''' and another '''LandingTrigger''' together to detect landings at the wrong place. Just make it so the '''AreaLandingTrigger''' gets disabled when the user is in the appropriate area and is re-enabled when they exit. You can use a [[Proximity Trigger|ProximityTrigger]] for this.