I fly a lot of general aviation at small airports without ATIS, and where there is no controlled airport for miles around. There are two frustrations I experience with flightgear in these situations:
1. The ATC/Frequencies box always says there's nothing within 40 nm. But in many cases there *is* an airport with ATIS close enough to receive ATIS (but not within 40 nm). Maybe this radius could be expanded, at least when nothing else was found? My local area happens to be a pathological case: KLRU is 40.7nm from KELP. 2. A lot of these airports, and almost always one within range no matter how remote you get (in the US anyway), have ASOS or AWOS (basically, almost everywhere you have a METAR you have either ATIS or ASOS/AWOS). They're essentially the same as ATIS, at least in all the ways that matter. FlightGear's database has these frequencies, but you hear nothing when tuning to them. The first point is a minor inconvenience, since a good pilot should be gathering things like radio frequencies *before* flying. :-) The second point makes it hard to get in-sim weather information (without "cheating" by looking at the weather scenario METAR) out west. I imagine the ASOS/AWOS thing might be a simple matter of expanding the search for frequencies somewhere. If someone can point me to the right area in the code I can probably work out a patch. -- Hans Fugal Fugal Computing ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
