wulfbindewald wrote:Hi Francois,
only a small hickup for Your attention: In cruise mode and after selecting new altitude, the display info is confused pls. see pic.
I recommend to collect only such findings and to wait for the new users´feedback at first after a further panel update.
Wulf
Hi wulf,
There are now many combinations about the FMA readings !! according situation flight, and it is very difficult the find the right way now.
I am not at home and I cannot test, but I think that when you change flight level you have the following sequence :
- you are in
ALT CRZ
you select your now flight level : Reading becomes
CLB (and
SPEED or
MACH mode toggle in
THR CLB )
- when aircraft is at less than 500 feet of the new cruise altitude, reading becomes
ALT CST* (* means altitude captured)
- when new Flight level altitude reached, reading come back
ALT CRZ and if speed cruise is reached, A/THR returns in
SPEED or
MACH mode
Buit it possible than there is a bug, because aircraft is below the crossover altitude (altitude when aircraft toggle from IAS to Mach reference).
In my logic, A second flight level is used for long trip. And in case of long trip, always in my logic, a first flight level is mandatory above crossover altitude (29000 ft by default).
So , I think that I wrote the second flight level code to works above the crossover altitude.
Note :
Flight level change value cannot be less than 750 feet, otherwise FMC cannot detect properly the function.
Mosquito and A320Pilot, i searched in AIRBUS FCOM.
T.O Inhibit and Landing Inhibit readings appears on EICAS to inform crew that only essentials messages will be displayed on the ECAM during these 2 phases.
My panel displays very few messages (in real aircraft, you can have the possibility to have dozen of messages, that crew can scrolling). I don't think that is essential to add these readings, because many messages are missing in my panel.....
I understand that you would like a perfect panel, but I am alone to code, and I am not professional (I learned on my own XML, 3 years ago, and I am not a champion !) and I would like finish the job, because since 3 years, I past all my time on this aircraft....
I am a little tired now....
Now, I want just fix the last bugs and publish otherwise project will have no end..........
Edit :
Thomas, I don't know what is your panel, but its a panel coded in C++ (ND map not use the FSX GPS map, it is a map coded in C++ gauge). and you can do all you want in C++, but I am not a C++ programmer !
ANd there is an error : CLB and NAV reading must be in CYAN color when there are armed. No white color in the second line of the FMA.
Even paywares are not perfect !