On Wed, Dec 23, 2009 at 5:25 AM, James Turner wrote:
> I'm surprised by this - partly because it doesn't fit with my intentions,
> or what I experience using the code daily here, but also because if the
> system is behaving as badly as you suggest, why haven't you (or other
> people) made more of
On 22 Dec 2009, at 14:51, Curtis Olson wrote:
> With the old route manager, the first way point is where I want to go for my
> first destination, because I just put it in there with that specific goal in
> mind. The 2nd waypoint is also where I want my second destination to be,
> again, becau
On Tue, 2009-12-22 at 14:10 +, James Turner wrote:
> A few things that will certainly help:
> - not adding the departure airport if no runway is selected
> - not adding the departure airport for an in-air route activation
Perhaps a quicker workaround, just set
the /autopilot/route-manag
s discussions
Subject: Re: [Flightgear-devel] Generic autopilot issues
On 21 Dec 2009, at 18:55, Curtis Olson wrote:
> What do you think would be a sensible course of action, in the situation you
> describe? Even if I choose not to add the departure airport for in-air route
> activat
On Tue, Dec 22, 2009 at 8:10 AM, James Turner wrote:
> What do you think would be a sensible course of action, in the situation
> you describe? Even if I choose not to add the departure airport for in-air
> route activation, there's no guarantee that the first route waypoint is
> where you actuall
On 21 Dec 2009, at 18:55, Curtis Olson wrote:
> What do you think would be a sensible course of action, in the situation you
> describe? Even if I choose not to add the departure airport for in-air route
> activation, there's no guarantee that the first route waypoint is where you
> actually w
6 matches
Mail list logo