On 08/17/2008 08:51 AM, James Turner wrote: [snip many lines of agreement]
> I think we're missing an 'audio-panel' simulation, except what > individual aircraft implement as Nasal scripts Agreed. > Yep, thinking about this more, I'm going to plan on moving ATIS to > FGAirportDynamics, so that ATIS is the same (ideally including the > point through the message) for each ATIS frequency at an airport. Sounds good to me. Tangential remark: The lack of adequate text-to-speech is going to be a hindrance here. > I'm still thinking about 'only enable ILS for the active landing > runways' - it seems quite easy, It's only an issue in the case of paired transmitters, sharing a frequency. In the absence of sharing, just turn it on and leave it on. > but I worry that's it's going to cause > many problems for people who don't pay attention to ATIS and are used > to just picking a runway themselves, tuning to ILS and assuming it > will work. Yes, I'm sure there are plenty of people out there who are in the habit of shooting approaches without properly IDENTing the navaids. This is a common student mistake. Such people ought to thank us for providing a simulation that demonstrates how dangerous that behavior is. > Might need a global pref to enable the new behaviour, The old behavior is dangerously unrealistic. No sane person would prefer it. It doesn't make sense to preserve "compatibility" with something that is dangerously wrong. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
