Project FMC simplified for Project Airbus

Abdullah Radwan · Post by **Abdullah Radwan** » 13 May 2018, 19:40

fdd_fr wrote: ↑
13 May 2018, 18:14
if you speak about SID/STAR files direction you must follow following rules.

SID :
think you are at the departure airport :
- Direction is the direction of the final leg of the SID (you go to......)

STAR :
think you are at the destination airport :
- Direction is the direction of the first STAR leg by thinking "I arrived by ....."

So for this chart, the direction should be S (South), right?

wulfbindewald · Post by **wulfbindewald** » 13 May 2018, 20:11

Have a look into the skyvector.com charts (world HI or world LO), which sometimes helps to find the right direction.
The corresponding airway to the transition waypoint DENVO is "SE" southeast from OBBI.

Abdullah Radwan · Post by **Abdullah Radwan** » 14 May 2018, 02:17

wulfbindewald wrote: ↑
13 May 2018, 20:11
Have a look into the skyvector.com charts (world HI or world LO), which sometimes helps to find the right direction.
The corresponding airway to the transition waypoint DENVO is "SE" southeast from OBBI.

Thank you so much. I got it now.

Abdullah Radwan · Post by **Abdullah Radwan** » 14 May 2018, 05:56

I've just download the last beta and.....
I didn't believe myself, I finally got a free pro-similar A320! Nice job guys! Really nice job! the FMC is awesome!
Please continue this great work! THANK YOU! REALLY THANK YOU!

Flyer10 · Post by **Flyer10** » 15 May 2018, 08:28

The popup MCDU is still transparent, I just changed the black to red 0 blue 1 green 0, it's still black but not see through any more. I would like to keep the popup MDCU at least because I know there has been talk of removing them.

The popup MCDU would be great with improved textures, I know our texture expert was looking for something to do.

wulfbindewald · Post by **wulfbindewald** » 15 May 2018, 08:45

The popup MCDU in the VC can be shown with keyboard commands too. The new MCDU since beta 2.0 and the old style MCDU panel are available:

new MCDU: shift+8
old style MCDU: shift+7

Flyer10 · Post by **Flyer10** » 15 May 2018, 09:02

That's what I use as I don't really want to zoom in so far that I cannot see what's happening out the window, I hope they both stay. I also need the engine start popup as the 3d ignition switch has never worked for me.

I can still select slats 1 with no flaps when on the ground Francois. That's because I use an axis for flaps but select them via the mouse is ok. It's not a big deal but at least I think I found out why we have some differences in the flap logic.

Prosdocimo · Post by **Prosdocimo** » 15 May 2018, 14:08

About MCDU, i put background_color=10,20,30 to remove its transparency. This line needs to be put in [window07] field in panel.cfg for each aircraft

@Flyer10. I read time ago that air model can't show it because there should be only 4 flap possible positions available in aircraft.cfg. But I am not sure on this!

Flyer10 · Post by **Flyer10** » 16 May 2018, 06:25

Thanks for that, I will do that now and it's an easy fix for Francois to add for the release.

wulfbindewald · Post by **wulfbindewald** » 16 May 2018, 08:46

Prosdocimo wrote: ↑
15 May 2018, 14:08
About MCDU, i put background_color=10,20,30 to remove its transparency. This line needs to be put in [window07] field in panel.cfg for each aircraft

The line "backgound_color=..." in [window07] already exists. Just change the numbers from 0,0,0 to 10,20,30 as stated above. Thanks Prosdocimo for this fix. It works on my end in the VC and the 2d cockpit day&night.

Bjoern · Post by **Bjoern** » 16 May 2018, 17:01

Looking at 2.0G at the moment and having quite a hard time updating my installation because it is not built on my Nov. 19th release.

Prosdocimo · Post by **Prosdocimo** » 16 May 2018, 17:17

Flyer10 wrote: ↑
15 May 2018, 09:02
That's what I use as I don't really want to zoom in so far that I cannot see what's happening out the window, I hope they both stay. I also need the engine start popup as the 3d ignition switch has never worked for me.

I can still select slats 1 with no flaps when on the ground Francois. That's because I use an axis for flaps but select them via the mouse is ok. It's not a big deal but at least I think I found out why we have some differences in the flap logic.

Hi, I misunderstood. Yes I also confirm that I can have just slats 1 on ground when selecting lever position 1 (by pressing F6 key). Hitting again F6 I get 1+F but the flap lever stays at 1. The othet positions are ok and also moving from 1+F to 1 when exceeding 210 kt

Bjoern · Post by **Bjoern** » 17 May 2018, 21:52

Based on the latest 2.0G release, I've attempted to fix the night rendering of the MCDU once and for all.
There are now four background bitmaps, switched depending on light state (no cockpit lights, panel only, cabin only, cabin and panel). White and orange button lighting when panel lights are on is retained.

The .xcf file can be used for altering the MCDU bitmaps in terms of brightness or color matching or whatever (make sure to export in 24bit bmp format).

Install by making a backup of "A32x_FD-FMC\A32x_MCDU.xml" and then put the modified files into "A32x_FD-FMC".

- Edit:
New version below: viewtopic.php?f=23&t=2823&start=3100#p32498

Prosdocimo · Post by **Prosdocimo** » 18 May 2018, 20:09

Hi I have an issue with dome lights. I installed the last complete package 2.0G.

I am in darkness: if I switch the dome lights on DIM, i don't get dome's but panel instruments lights on (panel instr' lights knob turns on). If i switch dome lights to BRT is nice, i have dome light. In BRT, i can turn off panel instruments lights. Is it a correct behaviour? I should have Diminished and Bright dome lights independently by panel instruments lights

Moreover I use Bjoern MCDU fix (thank you!) but Mcdu popup texture is still black at night

Bjoern · Post by **Bjoern** » 19 May 2018, 00:52

OH COME ON!

All textures required by the modified MCDU gauge are present in the archive I've uploaded and the MCDU displays just fine in every light condition even after testing it on my desktop PC!

No lights -> Standard texture
Panel lights -> Texture adapted to panel lighting
Cabin/dome lights -> Texture adapted to cabin/dome lighting
Cabin/dome and panel lights -> Texture adapted to cabin/dome and panel lighting

The only small error I could find in the modified MCDU gauge is in line 620. "A32x_MCDU_W.bmp" should be "A32x_MCDU_O.bmp", but this has absolutely nothing to do with the gauge background!

Gah! [Throws mouse against the wall]

wulfbindewald · Post by **wulfbindewald** » 19 May 2018, 06:42

Bjoern wrote: ↑
19 May 2018, 00:52
The only small error I could find in the modified MCDU gauge is in line 620. "A32x_MCDU_W.bmp" should be "A32x_MCDU_O.bmp", but this has absolutely nothing to do with the gauge background!

I have no line indications in the xml file. I found in total 2 "A32x_MCDU_W.bmp" entries. Is the first or the second one relevant to be modified?

I tested the MCDU hotfix in 2.0G and did not found any visual difference between the hotfix soln and the former soln with [window07] "background_color=10,20,30". The MCDU 2D popup window remains black during night and INT panel lights ON (DOME light off or on)....but better black at night than transparent

Prosdocimo · Post by **Prosdocimo** » 19 May 2018, 07:09

Bjoern, I was talking about MCDU popup window. The console Mcdu is fine.

I tested again the lights. I cannot turn on panel lights without touching dome lights switch. I must have dome lights on DIM position to automatically have panel lights. And turning it to BRT i have dome light. Why is there this link? Panel and dome lights should be indipendent switches. I should be able to command panel lights by turning the small knob on overhead panel or the switch on main panel. But i can't do that, i have panel light only switching the dome lights switch on DIM position. Is it better clear my bug? Thanks

wulfbindewald · Post by **wulfbindewald** » 19 May 2018, 07:48

Prosdocimo wrote: ↑
19 May 2018, 07:09
Bjoern, I was talking about MCDU popup window. The console Mcdu is fine.

I tested again the lights. I cannot turn on panel lights without touching dome lights switch. I must have dome lights on DIM position to automatically have panel lights. And turning it to BRT i have dome light. Why is there this link? Panel and dome lights should be indipendent switches. I should be able to command panel lights by turning the small knob on overhead panel or the switch on main panel. But i can't do that, i have panel light only switching the dome lights switch on DIM position. Is it better clear my bug? Thanks

This has been explained by Francois (13.April), who decided to link the panel light with the DOME dim light. I agree, independent switches are more realistic.
My favourite visual appearance in the VC during night needs the DOME dim lights too, because otherwise the VC panel with switched panel lights only looks too "dark", so it has been linked.

Bjoern · Post by **Bjoern** » 19 May 2018, 14:00

wulfbindewald wrote: ↑
19 May 2018, 06:42
I have no line indications in the xml file. I found in total 2 "A32x_MCDU_W.bmp" entries. Is the first or the second one relevant to be modified?

The second onee.
If you never use the orange cockpit lighting, you won't need to do anything at all.

I tested the MCDU hotfix in 2.0G and did not found any visual difference between the hotfix soln and the former soln with [window07] "background_color=10,20,30". The MCDU 2D popup window remains black during night and INT panel lights ON (DOME light off or on)....but better black at night than transparent

Prosdocimo wrote: ↑
19 May 2018, 07:09
Bjoern, I was talking about MCDU popup window. The console Mcdu is fine.

The fix was specifically intended for the popup MCDU!

One bitmap is very dark though and might fool you, but they're all images of the MCDU!

Prosdocimo · Post by **Prosdocimo** » 20 May 2018, 09:42

Is it this very dark? (Panel lights on)

https://postimg.cc/image/dqsahk9xz/

wulfbindewald · Post by **wulfbindewald** » 20 May 2018, 10:06

panel 2.0G: MCDU 2d popup with background_color=10,20,30 and one pic for the basic soln 0,0, for reference.
Bjoerns MCDU hotfix from 17.May corresponds to the 10,20,30 visual appearance on my end, therfore not explictly shown.

Bjoern · Post by **Bjoern** » 20 May 2018, 13:13

Separate versions for the 2D panel and VC should DEFINITELY fix this.

https://drive.google.com/file/d/1LH1E5f ... sp=sharing

All of this goes into "A32x_FD-FMC".
Don't forget to replace the relevant parts of the lines in the panel.cfg files with the new gauge names. See the included text file for hints.

Thanks for making us increase the required development and maintenance effort. I, for one, do not appreciate it.

moskito-x · Post by **moskito-x** » 20 May 2018, 23:29

Hello Bjoern,

I got next result with the update from your link.

and
with light on

panel.cfg

Code: Select all

[Window07]
Background_color=10,20,30
size_mm= 461,737
pixel_size=461,737
position=2
visible=0
ident=10102
gauge00=..\..\PA A32x_Common\A32xFD-FMC!A32x_MCDU_VC, 0,0,461,737
sizeable=0

aircraft.cfg (...\SimObjects\Airplanes\PA A321FD-FMC_CFM 2.0\PA A321FD-FMC_CFM 2.0\)

Code: Select all

[fltsim.0]
title=PA321_CFM - Virgin Atlantic CFM
ui_variation=Virgin Atlantic Airways
sim=pa321-cfm56-5B3
model=cfm
panel=A321CFM
sound=
texture=vir
description=Project Airbus presents the Airbus A321. Features include dynamic wingflex (with input from several new variables), drooping control surfaces, hardcoded double strobes, and over 40 other custom XML parts. Visit us at www.pairbus.com.
atc_id=G-VATH
atc_airline=Virgin
atc_flight_number=236
atc_parking_types=GATE,RAMP
atc_parking_codes=VIR
ui_manufacturer=Airbus
ui_type=A321-211 CFM
ui_typerole=Commercial Airliner
ui_createdby=Project Airbus
visual_damage=1
atc_heavy=0
kb_checklists=..\PA A32x_Common\Check_Ref\AirbusA321_check
kb_reference=..\PA A32x_Common\Check_Ref\AirbusA321_ref
// Virgin Atlantic Texture By Tom Collins

Thomas

wulfbindewald · Post by **wulfbindewald** » 21 May 2018, 06:12

Hi Bjoern, based on your 2.0G hotfix from 20.05 at 13:13. I interpreted your installation description as follows.

- To throw both new xml files "A32x_MCDU_2D.xml" and "A32x_MCDU_VC.xml" and the .bmp files into the existing A32xFD-FMC folder.
- To delete the existing file "A32x_MCDU.xml". But this is probably not necessary acc. to the panel.cfg entries.
- To modify the panel.cfg as follows:
[Window07]
Background_color=0,0,0
size_mm= 461,737
pixel_size=461,737
position=2
visible=0
ident=10102
//gauge00=..\..\PA A32x_Common\A32xFD-FMC!A32x_MCDU, 0,0,461,737
gauge00=..\..\PA A32x_Common\A32xFD-FMC!A32x_MCDU_2D, 0,0,461,737
gauge01=..\..\PA A32x_Common\A32xFD-FMC!A32x_MCDU_VC, 0,0,461,737
sizeable=0

The popup 2d MCDU looks fine except pic 3, but the visual impression looks similar to other additional gauges e.g. pic 3 top right.
It would be nice, if you send us your results in pics, if they differ from the shown pics below. Please advise, if the installation proc is wrong.

Bjoern · Post by **Bjoern** » 21 May 2018, 13:06

Wulf's screenshots look like what I have, but he slightly screwed up the installation.

"A32x_MCDU_2D" is for the popup version in [Window07] and "A32x_MCDU_VC" is for [VCockpit01].

Thomas screwed up altogether, needs to start over and think about the relationship between file names and installation locations, hinted at in the previous sentence.

Prosdocimo · Post by **Prosdocimo** » 22 May 2018, 21:44

Hi Wulf, I realized that in your Mcdu I can read "version 2.0 beta G". I don't in my installation, but I installed the last Françoise 2.0G from his link. I only put my textures. What's wrong in your opinion?

Bjoern · Post by **Bjoern** » 22 May 2018, 23:48

François:

I'm close to finishing an airplane manager (payload, fuel, doors, a/c configuration) for the A320 (for now; will try to make it smart enough for the A318-21 later on).

This will eliminate the need for your .ini file, since all custom configuration items in Config_A32xFD-FMC.ini (metric alt, barometric setting, etc...) will now be saved on a per-aircraft basis after initial configuration directly in the simulator. FMC save data, i.e. Save_FMS_Data.xml, Save_FP.xml and Load_FMS_Data.xml and the files it generates will NOT be affected.

ONLY the AIRCRAFT SYSTEM related loading and reset code in "A32x_FMS_init.xml" will be transferred to a new gauge to integrate them into the load/save system.
The auto reset and auto-configuration (air/ground) system can be retained, but I'll need to work it into the other stuff that'll need to be loaded and saved.

wulfbindewald · Post by **wulfbindewald** » 23 May 2018, 06:29

Prosdocimo wrote: ↑
22 May 2018, 21:44
Hi Wulf, I realized that in your Mcdu I can read "version 2.0 beta G". I don't in my installation, but I installed the last Françoise 2.0G from his link. I only put my textures. What's wrong in your opinion?

This is strange, because I did not change anything at first within the eight new 2.0G panel/aircraft folders (except livery changes in the aircraft.cfg). May be it helps, if you consequently delete any older panel folder at first from 2.0F downwards, even 1.55 or 1.6, to get a clean 2.0G panel, not any unwanted mix. Don´t forget to delete the old A318FD-FMC.CAB, A319FD-FMC.CAB, A320FD-FMC.CAB and A321FD-FMC.CAB files in the FSX/Gauges folder.

What I did at first: "cut (not copy) and paste" all older panel related files and folders into a new archive folder outside from FSX.
Bjoern´s MCDU hotfix, see above, did not change the panel version number displayed in the MCDU.

Abdullah Radwan · Post by **Abdullah Radwan** » 23 May 2018, 09:10

Hello,
I've just finished a flight with 2.0G, and here is my notices:
1- Why master caution light is on while it's useless?
2- The legs page is so strange! the points is repeated with incorrect information (Looks like it needs to re-coding)
3- Maybe not a bug but should be fixed:

Otherwise it's a nice aircraft, great job guys!

Prosdocimo · Post by **Prosdocimo** » 23 May 2018, 10:05

wulfbindewald wrote: ↑
23 May 2018, 06:29

Prosdocimo wrote: ↑
22 May 2018, 21:44
Hi Wulf, I realized that in your Mcdu I can read "version 2.0 beta G". I don't in my installation, but I installed the last Françoise 2.0G from his link. I only put my textures. What's wrong in your opinion?
Don´t forget to delete the old A318FD-FMC.CAB, A319FD-FMC.CAB, A320FD-FMC.CAB and A321FD-FMC.CAB files in the FSX/Gauges folder.

This is! Thanks!

Abdullah Radwan · Post by **Abdullah Radwan** » 23 May 2018, 18:13

I have a question: If an airport has RNAV transitions, should I put it in the procedure?

wulfbindewald · Post by **wulfbindewald** » 23 May 2018, 18:39

Abdullah Radwan wrote: ↑
23 May 2018, 18:13
I have a question: If an airport has RNAV transitions, should I put it in the procedure?

I am not sure, what you mean as there are different "RNAV transitions" during a flight cycle. May be one concrete chart example and pic would be helpfull and a short description how you want to define the proc.

Abdullah Radwan · Post by **Abdullah Radwan** » 23 May 2018, 20:07

wulfbindewald wrote: ↑
23 May 2018, 18:39
I am not sure, what you mean as there are different "RNAV transitions" during a flight cycle. May be one concrete chart example and pic would be helpfull and a short description how you want to define the proc.

Sorry it was my mistake, I didn't understand it well, now I got it. Thanks!

Abdullah Radwan · Post by **Abdullah Radwan** » 26 May 2018, 03:43

In such case, what is the best?

wulfbindewald · Post by **wulfbindewald** » 26 May 2018, 06:01

The std. hold pattern tracks are described in the "[EN] FreeNav DB Group Manual v4.15.pdf", chapter B1.4, and to be find in the freenavdbgroup.com download section.
IMO the above mentioned pattern is a right turn inbound pattern and coded as ...,1,2,172,352,60 (e.g. for 60s) in the appropriate data file.

Abdullah Radwan · Post by **Abdullah Radwan** » 26 May 2018, 08:24

wulfbindewald wrote: ↑
26 May 2018, 06:01
The std. hold pattern tracks are described in the "[EN] FreeNav DB Group Manual v4.15.pdf", chapter B1.4, and to be find in the freenavdbgroup.com download section.
IMO the above mentioned pattern is a right turn inbound pattern and coded as ...,1,2,172,352,60 (e.g. for 60s) in the appropriate data file.

I am asking what is better, use direct or parallel. I was only need '2' number in these. Anyway thanks!

Abdullah Radwan · Post by **Abdullah Radwan** » 26 May 2018, 22:39

2nd flight notices:

1- When I was in flight, the panel suddenly lags. I can't click on any button in cockpit, but the screen still active. I made a manual landing because this. I can't change anything in FMS, it completly freezes!

2- There is a lot of space in HESH STARs, make it almost invisible in 3D version. Just 1 space between runways is really enough! Also the procedures are outdated. I will see if I can make an updated version.

wulfbindewald · Post by **wulfbindewald** » 27 May 2018, 05:31

Abdullah Radwan wrote: ↑
26 May 2018, 22:39
2nd flight notices:
1- When I was in flight, the panel suddenly lags. I can't click on any button in cockpit, but the screen still active. I made a manual landing because this. I can't change anything in FMS, it completly freezes!

Please tell us which airport (ICAO), arrival and approach you have selected. Which fix was next when the panel began to freeze? Then there is a chance to duplicate this. Additional airport scenery used?

Abdullah Radwan · Post by **Abdullah Radwan** » 27 May 2018, 09:07

wulfbindewald wrote: ↑
27 May 2018, 05:31
Please tell us which airport (ICAO), arrival and approach you have selected. Which fix was next when the panel began to freeze? Then there is a chance to duplicate this. Additional airport scenery used?

Flight: From OJAI (No SID chosen) to HESH (DELMA RWY 22L STAR)
Approach: RNAV RWY 22L
Next fix: ------. I will explain: The problem starts from descent. I was on FL250. DELMA has altitude restriction 13000'. The panel start descent slowly (-700fpm)! I was thinking that is normal. But I end finally with FL220 on the approach point (I should be at 2200')! Then I opened 2D FMC via Shift+7. I start flipping pages between STAR and Approach to know what is the problem. I didn't change anything. Then I tried to close it via close button, but no success .I open the 2D FMC several times before to change some stuff and it works. I don't really know why it freezes this time without changing anything!
Then all of the whole panel freezes except screens. Even the A/P. I only was able to disconnect it using my joystick button. So the freeze was only visually, I can control stuff with shourtcuts.
I don't actually remember the whole flight. It was with panel 2.0G

Additional sceneries: IVAO EG HESH scenery, VATOJ OJAI scenery.

wulfbindewald · Post by **wulfbindewald** » 27 May 2018, 10:20

Hi Abdullah,
I repeated your defined flight from OJAI (No SID chosen) to HESH (DELMA RWY 22L STAR), Approach: RNAV RWY 22L without any prob with panel 2.0G and A320_IAE, HSEH is FSX default (no add. scenery). Everything is as expected, but I recommend to use the hold pattern at IAF HS425 to avoid extensive speed break usage lateron.
Have you put the throttle lever arms to idle during descent?
I wonder if the panel freeze is relating to a propable conflict with the additional scenery. Just deactivate this scenery for test purposes.

Prosdocimo · Post by **Prosdocimo** » 27 May 2018, 11:38

Abdullah Radwan wrote: ↑
27 May 2018, 09:07

wulfbindewald wrote: ↑
27 May 2018, 05:31
Please tell us which airport (ICAO), arrival and approach you have selected. Which fix was next when the panel began to freeze? Then there is a chance to duplicate this. Additional airport scenery used?
Flight: From OJAI (No SID chosen) to HESH (DELMA RWY 22L STAR)
Approach: RNAV RWY 22L
Next fix: ------. I will explain: The problem starts from descent. I was on FL250. DELMA has altitude restriction 13000'. The panel start descent slowly (-700fpm)! I was thinking that is normal. But I end finally with FL220 on the approach point (I should be at 2200')! Then I opened 2D FMC via Shift+7. I start flipping pages between STAR and Approach to know what is the problem. I didn't change anything. Then I tried to close it via close button, but no success .I open the 2D FMC several times before to change some stuff and it works. I don't really know why it freezes this time without changing anything!
Then all of the whole panel freezes except screens. Even the A/P. I only was able to disconnect it using my joystick button. So the freeze was only visually, I can control stuff with shourtcuts.
I don't actually remember the whole flight. It was with panel 2.0G

Additional sceneries: IVAO EG HESH scenery, VATOJ OJAI scenery.

Hi, please check your point of view position. If point of view goes behind the head rest (during airplane acceleration or deceleration), you may have these issues (not working clickspots)

Abdullah Radwan · Post by **Abdullah Radwan** » 27 May 2018, 12:42

Prosdocimo wrote: ↑
27 May 2018, 11:38
Hi, please check your point of view position. If point of view goes behind the head rest (during airplane acceleration or deceleration), you may have these issues (not working clickspots)

If I understand well, this shouldn't be the problem. Because FMC 2D panel doesn't work.

Abdullah Radwan · Post by **Abdullah Radwan** » 27 May 2018, 12:52

wulfbindewald wrote: ↑
27 May 2018, 10:20
Hi Abdullah,
I repeated your defined flight from OJAI (No SID chosen) to HESH (DELMA RWY 22L STAR), Approach: RNAV RWY 22L without any prob with panel 2.0G and A320_IAE, HSEH is FSX default (no add. scenery). Everything is as expected, but I recommend to use the hold pattern at IAF HS425 to avoid extensive speed break usage lateron.
Have you put the throttle lever arms to idle during descent?
I wonder if the panel freeze is relating to a propable conflict with the additional scenery. Just deactivate this scenery for test purposes.

Thank you so much, I'll do a test flight as soon as possible.

Bjoern · Post by **Bjoern** » 27 May 2018, 19:26

If the simulator pretty much freezes and doesn't manage to capture a specific target altitude, it points to a problem with the autopilot logic, namely spamming K: type events to the simulator.
I've tried to check "A32x_FMS_DES.xml" for any risk of spam, but the code is unannotated and very hard to read. So only François can do this.

Bjoern · Post by **Bjoern** » 28 May 2018, 21:57

Is "0 - 0 - 10 - 14 - 21 - 25" the flap configuration for the A321?

The other configs only differ for setting 4 (i.e. 35° or 40°) and only between engines (CFM or IAE), not between models (A318/9/20), correct?

Flyer10 · Post by **Flyer10** » 29 May 2018, 08:45

The A321 has different flaps, I could only find the full flaps setting which is 25 for both CFM and IAE, it's 35 on the 18,19 and 20. I assume the other settings are correct but they are hard to find.

Bjoern · Post by **Bjoern** » 29 May 2018, 20:43

It's a bit confusing since the A319 apparently also uses 40 degrees deflection for "FULL".
The SmartCockpit documents are nonspecific regarding the model that the tables apply to and is therefor of little help.

Background: I'm redoing the flap indicator for the next fork and want to make it smart, i.e. auto-adapt the internal calculations to the model in use.

Flyer10 · Post by **Flyer10** » 30 May 2018, 06:30

Everything I have read is that the A318,A319 and A320 are the same (This was an airline pdf), there is a possibility the A318 could be changed if airlines go for the steep approach option to get into places like EGLC with a 6* glide slope. Maybe that was what you were thinking of with the A319?

I actually fixed this myself a while ago and I found the flaps for the A321 were, 0-0-10-15-21-25 but it was so long ago I couldn't tell you where I found the info, I also had to edit the xml in order to get the indicator to match up too.

http://theflyingengineer.com/tag/flaps/ confirms 10 for 1+F, 21, 25 for 3 and full so I am pretty sure 15 is correct too.

Bjoern · Post by **Bjoern** » 30 May 2018, 21:20

This: http://www.airbusdriver.net/airbusnotes.pdf (p.34)
And this: http://www.airliners.net/forum/viewtopi ... #p10553259
..is the only conclusive information that I could find on the flap configurations.

A319: 0-0-10-15-20-40
A320: 0-0-10-15-20-35
A321: 0-0-10-14-21-25

And I assume that the settings on the A319 also apply to the A318.

So I'll work with that.

Flyer10 · Post by **Flyer10** » 31 May 2018, 06:58

Agree, it's weird that the bigger aircraft have less flaps even if they are using the same wing. Did you see the A321 has extra slots for more lift so it would make sense to give it a higher lift number in the aircraft.cfg so it will match the figures.