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 an issue of it, here? There were some initial issues > right after the commit at the start of October, and I thought I'd resolved > those to people's satisfaction, and that the code was working fine for > people who use it. To find out now, that that's not the case, is > unfortunate. > > To be clear, the current code: > > - adds the departure / destination runways if specified, otherwise the > corresponding airports, if specified, ONLY when you click 'activate'. That > is the *only* time it modifies the waypoint list, and I'm happy to limit > that behaviour further if it's really causing problems for people. (I am > considering splitting the flight-planning functionality into a separate, new > dialog, which uses the same waypoints, but enforces my stricter requirements > as regards flight-plans) >
Here are a couple questions: I'm testing all of this from within the alphajet. Is there a way to not select a departure runway? When I bring up the dialog box, it's already filled in. Even after takeoff, it's filled in so the departure airport appears to always be added to the route, even if you setup the route and click activate after take off. Also I noticed that my target altitude which I already setup gets reset to something seemingly a bit random and close to the ground when I clicked "Activate". There was a cruise altitude set to 10,000' in the route mgr dialog box, but this seems to be ignored. If there is already a target altitude, would it make sense to leave it alone? What is the current rules for how the target altitude is set? - Allows inserting / deleting waypoints exactly as with the old code - I use > this feature all the time > Ok, my bad, I saw a lot of changes to the dialog box, focused in on what didn't make sense, and didn't pay close enough attention to what was still there. > - Allows waypoints to be entered A/B/C/D as you suggest, hit activate, and > you should be done. The only additional step is hitting 'activate', and the > code is supposed to be completely deterministic. > What specifically does "activate" do? After I clicked activate, I still have to type "F6" to turn on route following for the autopilot to follow the route. > (I guess you can see from that list why I'm so surprised!) > I was filing a "bug" report from not-very-fresh-memory so I apologize for any reporting mistakes I made. > Fundamentally, the new code's public API is almost unchanged - there's some > (big) structural changes, and new features, but I am quite dismayed that it > would be described as complex or non-deterministic - especially when that's > at odds with what I see. Of course my expectations are different to other > people's, since I wrote the code. > > As ever, I'd be happiest if people would file bug-report type emails, that > gave a precise series of steps, expected results, and actual results. > > (Obviously the 'activate-adds-departure-and-destination-waypoints' thing is > causing some issues, but I find it hard to ascribe all the problems you > mention to that one thing ... especially since it's been discussed before, > and is documented in the wiki pages for the route manager) > > > The alphajet has it's own autopilot configuration. I wouldn't > characterize it as "generic" since it is specific for this aircraft. > Perhaps some of the gains could be tweaked, but it behaves pretty well for > me. > > That's not what I'm seeing in CVS data - thought it would explain why I > became so confused in trying to test the Alphajet autopilot yesterday. If > there's a non generic autopilot config for the Alphajet, where is it? I've > just looked through the Aircraft/Alphajet dir, and don't see an autopilot > .XML file. Hmmm, I may have been mistaken on that one. I don't see a specific configuration setup for the alphajet either. I swear it used to have one, but maybe I am misremembering that? The "generic" autopilot configuration then in this case is reasonable stable around slow to moderate flight speeds. So to summarize my questions: How do I de-select the departure runway? Or how can I avoid having the departure airport included in the route by default? What does "activate" specifically do? This is a non-intuitive portion of the interface that I do not fully understand. I see that if I press "activate", it inserts the departure and arrival waypoints into the route. If I then clean up the route so it is what I really want, then if I happen to press activate again, it re-inserts the departure and arrival airports into the routes and I have to manually clean up my route again. The answer might be don't press activate twice, but not fully understanding what the button is supposed to do in the first place so there may be occasions where I press it again trying to make something happen, it might be better to offer more end user protection from doing something wrong, or somehow make it more clear what all is affected/accomplished by pressing the "activate" button. 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
