On 15 Aug 2008, at 23:07, John Denker wrote: > Possibly constructive suggestions: > > 1) In the case of paired transmitters, turn on the one that serves > the > runway _favored by the wind_. Do this regardless of the location of > the aircraft. > > Remark: This works even in multiplayer situations. > > Remark: Put a heavy low-pass filter on the choice of runway, so it > doesn't go nuts if the wind is variable. Maybe cooperate with the > ATIS > code so that the "active" runway reported by ATIS is the runway > with the > active transmitter.
Funnily enough, that's the next step in my runways code. However, selectively enabling and disabling ILS/LOC/GS navaids will take a bit more engineering. I think it's possible, since Durk's runway prefs logic knows which runway(s) are active for landings. And that code already has the low-pass filter, AND soon will be hooked up to the ATIS code. > 2) Fix the many other bugs in the service-volume code. Note that > there > is code in the Sport Model to handle false LOC courses, false GS > paths, > extended LOC volumes, and other stuff you encounter in the real > world. I don't know what the 'Sport Model' is, can you elaborate? If you could enumerate the issues here, in a new thread, that'd be interesting. I'm not promising to work on any issues besides this one, but at least we'd have the problems tracked in a searchable, archived place. Cheers, James ------------------------------------------------------------------------- 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
