Difference between revisions of "DCS event runway takeoff"

From DCS World Wiki - Hoggitworld.com
(Created page with "{{Template:DCS_events |eName=RUNWAY_TAKEOFF |vNum= 2.9.6 |id = 54 |desc= Occurs when the player aircraft takes off. Initiator : The unit that tookoff place: Object from...")
 
Line 7: Line 7:
 
|id = 54
 
|id = 54
  
|desc= Occurs when the player aircraft takes off.  
+
|desc= Occurs when an aircraft leaves the ground and takes off.  
  
 
Initiator : The unit that tookoff
 
Initiator : The unit that tookoff
Line 26: Line 26:
 
|exam=
 
|exam=
  
|notes= DCS 2.9.6 introduced a change with regard to take-off and landing events. There is now a separate event for when a player in SP or the host in MP takes off and lands. The existing takeoff and landing event will still occur for every other aircraft. Clients in MP should also get the existing takeoff and landing event.
+
|notes= DCS 2.9.6 changed the functionality of the [[DCS_event_takeoff|takeoff]] and [[DCS_event_land|land]] event effectively applying their previous behavior to [[DCS_event_runway_takeoff|runway_takeoff]], [[DCS_event_runway_touch|runway_touch]].
 
 
SP/MP Host: [[DCS_event_runway_takeoff|runway_takeoff]], [[DCS_event_runway_touch|runway_touch]]
 
 
 
Any AI and MP Clients: [[DCS_event_takeoff|takeoff]], [[DCS_event_land|land]]
 
  
 +
For example an aircraft that "bolters" a landing on the aircraft carrier will now call runway touch, runway takeoff rather than land and takeoff.
  
  

Revision as of 22:43, 9 August 2024


Event: S_EVENT_RUNWAY_TAKEOFF Added with: 2.9.6
Enum ID: 54 Event Locality: None
Description: Occurs when an aircraft leaves the ground and takes off.

Initiator : The unit that tookoff

place: Object from where the AI took-off from. Can be an Airbase Object, FARP, or Ships

Table Format: The takeoff event table is in the following format.
Event = {
  id = 54,
  time = Time,
  initiator = Unit,
  place = Airbase,
  subPlace = 0
}
Examples:
Notes: DCS 2.9.6 changed the functionality of the takeoff and land event effectively applying their previous behavior to runway_takeoff, runway_touch.

For example an aircraft that "bolters" a landing on the aircraft carrier will now call runway touch, runway takeoff rather than land and takeoff.

Events: shot, hit, takeoff, land, crash, ejection, refueling, dead, pilot_dead, base_captured, mission_start, mission_end, took_control, refueling_stop, birth, human_failure, detailed_failure, engine_startup, engine_shutdown, player_enter_unit, player_leave_unit, player_comment, shooting_start, shooting_end, mark_added, mark_change, mark_remove, kill, score, unit_lost, landing_after_ejection, discard_chair_after_ejection, weapon_add, landing_quality_mark, ai_abort_mission, weapon_drop, runway_takeoff, runway_touch,