On 15 Sep 2009, at 16:28, Martin Spott wrote: > I think it's perfectly fine to have an unrealistic 'dummy' mode for > those who don't care .... but setting such behaviour into stone by > hard-coding it into the implementation of a navaid reciever is > probably > not qualifying for extremely clever design in the long run. > > A reasonable compromise would be having a radio that works as in real > life, accompagnied by a separate routine - which allows to be manually > disabled or overridden by a real world controller - to implement the > desired dummy mode.
I agree with Martin here - I think we need more accurate behaviour here, but it's easy to keep the current behaviour as an option, controlled by a flag - something I've been considering for a while anyway - eg /sim/realism prop. Possibly the same could apply to the false GS and LOC lobes. In 'non'-realistic mode, we'd keep the current behaviour, with all ILSs enabled, though I will add a cap on the code to stop the navid changing below a certain altitude (or some similar kind of test), so that we don't observe the current flicking from one transmitter to another at 100ft above the runway. Once that's done, I don't think anyone can object to providing more realistic behaviour. The only debate then is the default value of /sim/realism :) 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
