On 17 Jun 2013, at 14:41, grtuxhangar team <hohora...@gmail.com> wrote:
> though not sure
>
> gps.cxx line 774
>
> if (!_config.driveAutopilot() || !_defaultGPSMode) {
> _apDrivingFlag->setBoolValue(false);
>
> isn't it that strange ?
> _apDrivingFlag is ever set to false
Yes, the problem is I assumed aircraft with an explicit GPS instrument are
using a fully configured setup, but in fact many (such as yours) are listing an
explicit GPS in instrumentation.xml, but relying on the default configuration.
These problems are because long ago it was decided it would be a good idea to
have the route-manager, GPS & AP work in aircraft which never had such things
in real-life (Spitfires, Cubs…) , so we have to (in C++) decide if the user is
asking for a simulated GPS (which should obey electrical power, and often needs
manual synchronisation of the GPS course -> CDI course, and maybe no AP at all
all), or if they are asking for the internal features to 'just work'
regardless.
Anyway, for now the fix is just to go back to the old situation, where we
assume the user wants the GPS to drive the AP all the time.
Longer term, I think I will contemplate a more radical renaming to fix the
issue, where explicit simulated GPSs such as the Garmins and so on use a
different instrument name. ('real-gps' or something) Then I could assume any
aircraft requesting a 'gps' instrument is legacy and wants the old behaviour,
but remove all the awkward defaults for people who really want full simulation.
Regards,
James------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
