|
From: James T. <jam...@kd...> - 2018-01-05 09:37:11
|
> On 4 Jan 2018, at 17:53, www2 <ww...@wo...> wrote: > > The two most important problem are witch route manager > 1. routemanager is not the main problem, interface not access from aircraft that have the Autopilot menu disable this is handy for planing you route. Okay, this is not so much a problem as a design choice :) The C172 lacks an autopilot, so the aircraft author(s) choose to disable that. Now, in real-life most pilots will use a hand-held GPS in the cockpit (possibly even an ipad / tablet) in 2017 I guess. And some fo the autopilot menu functions are really for the route-manager, and hence for a GPS. What I guess you want here, is to start creating the kind of GPS Ui that would be found in GA aircraft - for example a Garmin GNS 480 series or the more modern equivalent. This could be done as as a Nasal add-on so it could added as a variant into many GA aircraft including the C172, and would give you all the route-manager features and display. (It could also be a pop-out Canvas window) Since Stuart is working on the more complex G1000, probably you can get very far just taking what he is doing, simplifying it and adjusting for the 480 or whichever similar device you selection. I did some work on modelling an KLN-94 a few years ago the same way, but so much has improved since then, that it’s likely better to start from fresh. > 2. this is my main problem: route manager have problems with 3 charater airport code (the airports that have only a faa airport code). > The problem is in the c/c++ code that not accept airport that have only a 3 charter airport id. This is ‘just a bug’, let’s fix the C++ code, not crate a whole new system. Please go ahead and fix it yourself or ask if you need some help with parts of the C++ code. > > The other thing i like to see to add to flightgear are airspace. > This is a part that are include in little nav map. > And easier to install and update for the user. Well, everyone agrees we would like to add airspace data - what we’re missing is a suitable data source with the correct license. Torsten found a raster-based source but for wider use in the sim we really need vector data, so we can render it ourselves directly. Can you describe where the airspace data you’re using comes from, and the license? Kind regards, James |