On Tue, Sep 15, 2009 at 5:25 AM, James Turner wrote:
> This is 'fixed' now - except it's not.
>
> penaltyForNav is basically broken - we all know it's broken
> conceptually, but it's also broken in practice, because it doesn't
> even do what it claims (and never has, that I can see) - bias to
> directional transmitters based on aircraft *heading*. The problem is
> it's biasing based on *bearing* from the aircraft to the transmitter.
>
Hi James,
I believe the original intent was to make the system function in away that
made it appear that whatever approach you were trying to fly was the one
that was turned on. So biasing the choice based on which approach you are
most likely to be flying seems to make some sense. You don't care about
aircraft heading because (I don't know) maybe you do a 180 because you get
lost or you want to fly back and start over again, or whatever. The active
glideslope & dme & ils transmitters should change when you turn away from
the airport. The important thing is which end of the runway you are off of.
I think we can concede that we don't have real world controllers turning
approaches and lighting on and off for us on the ground. So either we
create an elaborate system and force the user to make all these detailed
choices every time we start up the sim, or we create some functional
defaults that behave like people would expect, and allow people to easily
use the simulation to practice flying any published approach.
Once that base line capability is reestablished with all this new code and
development activity, then yes, it would be great to allow an instructor to
disable one side of an approach, or select which side is active, or even
disable both sides. There could be some good training value.
I think it's pretty important to be able to fire up FlightGear and practice
any published approach without needing to go through contortions or
elaborate setup proceedures, or having to repeatedly restart the sim until
the particular approach we are interested randomly is enabled. FlightGear
is used as part of FAA certified flight training devices so this is an area
of the code where the basics need to work and be solid, and then if we want
to get fancy and add additional realism, that's great.
So at the end of the day, somehow we need to be able to just fire up the sim
and fly any published approach without needing to go through some
extravagant setup procedure each time.
Regards,
Curt.
The fix is sort of a work-around (but also a correctness improvement);
> in the problem cases, we're picking the 'opposite' end LOC, but still
> getting the correct GS. Eg at EGPH, as you pass over the Rwy 06 LOC
> (ident=IVG), while flying the rwy 24 (ident ITH) ILS, the navradio
> switches to the 06/IVG LOC - but we're still using the ITH GS. What
> I've done is adjust the navradio to handle this case (mismatched LOC
> and GS) sanely, and hence avoid the bizarre angles being generated.
>
> The CDI needle still jumps when the LOC switches, but since it jumps
> onto the back course lobe, that's much more tolerable.
>
> As ever, please test and let me know what you think. All of this is
> short-term fixes until we properly model active/inactive ILS
> installations; which I'm going to be working on 'soon'.
>
> Regards,
> James
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
Curtis Olson: http://baron.flightgear.org/~curt/
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
