On Mon, Dec 21, 2009 at 12:48 PM, James Turner wrote: > I thought I'd fixed that back at the start of October, soon after the > initial commit - Curt complained that h couldn't start a route 'in-air' so I > removed the need for departure/destination airports. > > Ah, I get it - you're specifying a departure airport, but then not > activating the route until airborne. > > Hmm. > > I'm not sure that's actually a bug. Activating a route starts a leg to the > first waypoint ... regardless of wether that's 'behind' you in the route or > anything. In real-life I'd activate the route, then select the enroute > waypoint I wanted to 'start' from, and 'DTO' on it, to head straight there - > that's exactly how I fly departures where ATC vector me, then clear me to a > SID waypoint. > > 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 want to be going.
Conceptually, including the starting point in the route seems like it could always be problematic. The "airport location" is some random point on the airport grounds (probably the average of the center points of the runways.) Even if you haven't taken off yet, it would be possible in some circumstances to not fly close to the center of the airport on take off. Then you would get routed back to the starting point before you could continue on to the next way point. I think we are just getting "lucky" when we fly close enough to the center of the airport in most situations for most runways to satisfy the route manager and it clicks on to the next waypoint. The KSFO airport layout is very friendly in this regards, but other airports like DFW and DEN are more sprawling. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
