> Hmm, this is going to get fiddly. I've got a generic route/flight-plan
> backend sort of working (no flight traversal or waypoint sequencing as
> of yet), which I am planning to extend with airways, SIDs, STARs and so
> on (with editing of course). The long term plan was to build an FMC /
> MCDU / GPS on top of this, but it seems like you're a good way ahead of
> me. And of course this is built into flightGear so that it can access
> the exiting Navaids, fixes and runway data.
>
Not really, I've been focusing on an approach to build components for home
cockpit builders that would most
likely use a network of machines. I suspect trying to integrate or "wrap"
the source into FlightGear could lead
to insanity.
> > The not-so-good-news --- it runs as a single opengl app (I've got my
> > copy
> > running on a laptop) and uses the SimGear library socket functions. (You
> > need 3 networked machines, but you do get the *whole enchilada*)
> > A full complement of flight deck displays (OpenGC), a multi-function
> > control
> > unit (MCDU), a flight dynamics model
> > and scenery(FlightGear).
>
>
> I'm not sure the best way to proceed. I really think the auto-pilot code
> belongs in flight-gear, but the goal of having the FMC / MCDU run
> separately is valuable.
There are some advantages to having the autopilot external especilly since
FG has the hooks to control the
flight model via the network.
There's a lot of navigation data the FMC/MCDU
> needs that is simulator specific though : does your code have it's own
> copy or what?
Using Robin Peel's nav database, flight/aircraft models are on the FG side.
There is some new enviro data that needs
to be collected and shipped across for thrust calculations and the like.
Still thinking of how to handle wind. the FMC needs to calculate a wind
vector based on navigation performance, grabbing the values from the
property tree is "cheating"
>
Regards
John W.
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
