Added RunwayTouch and RunwayTakeoff for more accurate TakeOff and Lan… #272
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As referenced in the below image.
DCS Changed the Land and Touchdown events' behaviour and implemented the original behaviour (exact touch/no touch) in new events.
These new events are
RunwayTouch
and RunwayTakeoff` which are now added with this release.Apparently 2.9.6 changed it.
https://wiki.hoggitworld.com/view/DCS_event_takeoff
To summize the new behaviour since 2.9.6:
S_EVENT_LAND
: Occurs when an aircraft lands at an airbase, farp or ship and sufficiently slows down.S_EVENT_TAKEOFF
: Occurs when an aircraft takes off from an airbase, farp, or ship. Occurs several seconds after take-off.S_EVENT_RUNWAY_TOUCH
: Occurs the moment when the player aircraft aircraft lands at an airbase, farp or ship.S_EVENT_RUNWAY_TAKEOFF
: Occurs when an aircraft leaves the ground and takes off.Previously the
S_EVENT_LAND
andS_EVENT_TAKEOFF
would trigger instantly, but they only fire now when DCS logically assumes a successful takeoff/landing was performed.S_EVENT_RUNWAY_TOUCH
andS_EVENT_RUNWAY_TAKEOFF
were (assumingly) added to still expose the earlier behaviour.