72
edits
Runway Awareness and Advisory System: Difference between revisions
Jump to navigation
Jump to search
Runway Awareness and Advisory System (view source)
Revision as of 23:11, 22 September 2014
, 22 September 2014no edit summary
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
|status = Under active development as of 08/2014 | |status = Under active development as of 08/2014 | ||
|developers = onox | |developers = onox | ||
|subforum = http://forum.flightgear.org/viewtopic.php?f=66&t=21266 | |||
}} | }} | ||
| Line 227: | Line 228: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
{{Note|In this case gear[1] and gear[2] are used to detect whether the aircraft is on the ground or in the air. You may want to modify this for your aircraft.}} | |||
{{Note|It is your responsibility to start and stop the announcers and to set the correct modes. Therefore it is necessary to connect to signals like landed-outside-runway and vacated-runway, even if they appear to be useless for your specific aircraft. The example of runway.nas above already does this for you.}} | |||
{{Note|You might want to replace copilot_say().}} | |||
The configuration object takeoff_config has a number of properties with default values. These properties can be modified if you want to change when certain signals are emitted. For example, in the example of runway.nas above, distance_center_line_m, distance_start_m, and distance_edge_max_m where overridden for large airliners. The defaults are: | The configuration object takeoff_config has a number of properties with default values. These properties can be modified if you want to change when certain signals are emitted. For example, in the example of runway.nas above, distance_center_line_m, distance_start_m, and distance_edge_max_m where overridden for large airliners. The defaults are: | ||