@Lydiot,
I didn't say what you are saying I said.
How they differ:
The Route Manager and MCDU/FMGC are 2 separate and competing ways to enter and manage a flightplan. They are not intercompatible and supporting both is not possible because we cannot "guess" information about your flightplan that is not provided by the route manager -> so we proceeded to support the more realistic option, being the MCDU/FMGC.
Panel States are a completely different thing, exist in real sims and do not conflict with manual starting of the airplane -> if they did conflict with the ability to manually start the airplane on real checklists, we would have made the same decision, and removed them, in order to stay true to the more realistic option.
The Flightplan systems are part of the A320 simulation itself. Panel States are not, they are part of the simulator's configuration (like airport location). That is why they don't conflict with manual starting, but the Route Manager does conflict with the MCDU/FMGC. Does you understand?
Our project goal is realism first.
I believe you are looking at the subject from the point of view of someone with your preferences on what you want from a plane -> and from what you describe, it sounds like an accurate FMGC/MCDU is not one of them. That's fine, to each his own style of flight simming.
Our team look at it from the perspective of lets make this as real as possible. Lets also try to add things that make it easier to test/develop if needed, but if we cannot, then lets stick to what is in the real airplane. (and as merspieler stated, real flight sims also use panel state technology... and as I stated above, panel states do not conflict, thus I do not have to "choose" between them and manual starting, like I have to "choose" between MCDU/FMGC and Route Manager.
Hooray wrote:I don't think the feature is the real problem, rather the UI (which is why I responded referring specifically to PUI).
Correct. The current Route Manager system doesn't provide near as much info as the MCDU/FMGC which is why the conflict exits.
The actual flightplan system underneath Route Manager we also use in our MCDU/FMGC -> since the flightplan system is a framework, we have set up our implementation to match A320 real. If the route manager some day supports enough options that we can function properly, then of course we can re-enable for the users who prefer to use him instead.
Kind Regards,
Josh