I use the 2d panels for startup, it much easier and there were things on the panel that weren't on the 3d VC. Also the ignition switch has never worked for me on the VC leaving me having to use the 2d panel.

I am not sure if your version fixes this but people could have problems without 2d panels.

I also found there was no VC logo light on the old version. Ignore that if you already fixed it.

I think that it is better to keep 2D panels. But some windows can be removed bjoern, if you want get some new application :

MAJ+1 = useless because 2D cockpit can be siplayed by F10
MAJ+2 = Radio panel ; I prefer to keep it
MAJ+3 = GPS : useless with FD-FMC
MAJ+4 = throttle panel ; I prefer to keep it
MAJ+5= Overhead ; I prefer to keep it
MAJ+6= landing Gear ; Useless for me
MAJ+7 = FMC, must be kept
MAJ+8= PFD useless because you can open it by clicking on the VC PFD
MAJ+9= ND useless for the same reason that PFD.

So, 5 shortcuts can be recovered for me.

I fixed 2 bugs in the FMC.
- When a second flight level according a weight was used, FMC (and FCU) lost speed information during few seconds when aircraft reached second flight level : bug fixed
- When holding pattern was armed but not began, Managed speed was set to 285 kts or max holding pattern speed was applied immediately : bug fixed. Now, max holding pattern speed is applied only when holding begin.

I'll consider the 2D panels, although I think that the throttle panel can be done away with. Throttles can be controlled with a hardware controller while flaps and spoilers can at least be controlled by keystroke (F5 to F8 or Shift+F5 to Shift-F8).

Good news about the step climb bug, that was the one I reported when the the throttles went to idle? Would it be possible to display the VREF (like the v speeds) somewhere if you cant the the green ball to display on non star flight plans?

Also, I find the throttle panel useful as it displays the trim figure, the VC doesn't do that if IIRC. Of course that could be fixed by making the VC trim display the trim figure.

Yes but even then you don't need them on the real thing as the AT does it for you.

Aircraft goes into app mode 30 miles from airport or via pilot actions.
AT drops to slats speed
Pilot deploys slats
AT drops to F1
Pilot deploys F1
and so on until full flaps
at full flaps the AT will go to Vref.

I believe this version has the green ball display the VREF which displays if you use the STAR, however it doesn't display if you don't use the star so you have to guess the VREF. Not really good on any jet.

The AAL Airbus training manual indicates that green dot is always displaying at flaps 0 and indicates the best Lift/Drag ratio.
According to the FMS and PFD XML code, green dot speed is always calculated and displayed on the PFD. The only thing I'd change is the flap setting condition to display it.

Regarding Vapp:"You will only have VAPP target shown when in APPR phase. You can force the FMGC to approach phase by selecting PERF and then ←ACTIVATE APPR PHASE and *CONFIRM APPR PHASE. This will drive the managed speed to approach speed. Normally you will be on speed select when you do this but when you command speed engage the speed will be VAPP. Note that VLS will change depending on the flaps configuration selected and therefore the VAPP
will also change with landing flap configuration.
Airbus Gotcha: The VAPP is calculated from the weight and balance closeout
data you put in on taxi out. "

Assuming that you don't need an actual flight plan to use the FMGC performance calculations on the real Airbus and considering that we have a simplified FMGC unit, the "APPR" button on the ND control unit can be used to make the (continuously calculated) Vapp triangles display on the PFD.
At least that's how I'd do it.
I'll leave this to François to decide.

You never actually fly the Airbus without the AT unless its an emergency. I know Françoise doesn't want to or can't imitate the AT-Flaps slowdown (I have used it on the Aerosoft Airbus and it's a brilliant system, you never touch the throttles from pulling back from TOGA/Flex until pulling back to idle/reverse when landing) but landing the plane without any VREF or landing speed takes a fair bit of guesswork, especially on the new A330 where the weight different and thus landing speed difference can be very big.

That's why I suggested an easy way of doing it by listing the VREF alongside the V Speeds in the FMC if he doesn't want to or can't get the VREF to display on the PFD.

Great, the stupid board ate my other post and no time to type it all again.

Core message and assignment: Get the FCOM of the A320* and find me the page or chapter containing a table with stall speeds (VS or VS1g) for the Buses.
From that everything else used by the auto approach speed function in managed speed mode can be worked out.

François:
What do you think about a system for dynamically calculating F and S speeds?

All we'd need is the stall speeds for the various A32x models and then put them into XMLTables. From there, the integration into the PFD can be a first step before the auto-deceleration feature when in managed speed mode can be implemented.
(As far as I understood the real FCOM, the automatic approach speed management would have to consider STAR speed contraints, i.e. use the speed constraint if it is lower than the current F or S speed.)

A stall speed table is in FCOM 3.01.20, page 8 or in A319-320-321_Limitations.pdf from SmartCockpit, page 75.
Linear interpolation of the lines for an equation would be possible, but I figure that dividing the table into sensible intervals for interpolation by XMLTables would be even better.

This could also serve as a basis for the aural stall warning system. And probably for a custom AFLOOR protection.

Sidenote:
Since my FSX is knocked out cold due to the Windows 10 bug in the current 1709 release, I've continued working on the A32x exterior model animations in 3ds Max. It took me too many hours to redo the downlock mechanism on the main gear. Stupid three-dimensional movement. And things aren't going to be much better from here on (downlock actuators, shock absorbers, brake lines).

According to the FCOM:
VREF is 1.23 times VS for flaps down (full) configuration. Only displayed on the MCDU APPR page if landing is planned in FULL configuration.
VAPP is VLS + Wind correction. VLS is 1.13 * VS or 1.23 * VS or 1.28 * VS depending on configuration.VAPP is only displayed on the MCDU APPR page.
VAPP Target: GS mini + plane headwind = VAPP - Tower Wind (manually entered) + plane headwind. This is what you're seeing on the PFD magenta triangle).

All other speeds are explained in the same chapter, 3.04.10 ff and as you will see, all speeds refer to the respective stall speed in some way, which varies with aircraft weight (and pressure altitude).

François:
What do you think about a system for dynamically calculating F and S speeds?

All we'd need is the stall speeds for the various A32x models and then put them into XMLTables. From there, the integration into the PFD can be a first step before the auto-deceleration feature when in managed speed mode can be implemented.
(As far as I understood the real FCOM, the automatic approach speed management would have to consider STAR speed contraints, i.e. use the speed constraint if it is lower than the current F or S speed.)

A stall speed table is in FCOM 3.01.20, page 8 or in A319-320-321_Limitations.pdf from SmartCockpit, page 75.
Linear interpolation of the lines for an equation would be possible, but I figure that dividing the table into sensible intervals for interpolation by XMLTables would be even better.

This could also serve as a basis for the aural stall warning system. And probably for a custom AFLOOR protection.

Only Take-Off page and SID page are completed. Take a look about how it work, because I had to find some tricks according FD-FMC logic. And I have some issues with FMC keyboard (double character in some case...).

Thanks for the info on the approach speeds, I guess I was looking too early in the flight in the FMC, however it is not displayed on the ASI in an non star flight and I will double check to see if it is displayed in the FMC in approach mode without a star.

Thanks for the info on the approach speeds, I guess I was looking too early in the flight in the FMC, however it is not displayed on the ASI in an non star flight and I will double check to see if it is displayed in the FMC in approach mode without a star.

I think not using a star messes it up.

I don't remember if Vref/Vapp works without STAR or approach. I coded this part long time ago....I will check..

Only Take-Off page and SID page are completed. Take a look about how it work, because I had to find some tricks according FD-FMC logic. And I have some issues with FMC keyboard (double character in some case...).

That looks awesome!

Not sure if it works with letters and decimals, but I've got a working method for entering numbers with the keyboard. Might be useful to improve FMC usability.

To all who have signed up for "FMC Airport Manager".
Thank you for your interest in the software.

The delivery has been delayed a bit, because it does not work without a tutorial and a manual.(I,m working on that)
5 Days and I think a short tutorial is ready.
I ask all who have sent me a PM .... to apology.

Unfortunately, the official airport developers seem to have no interest in the help that the program offers.

Hundreds of errors are contained in the airports. This can quickly detect and correct by the program.

Here an example:

A) shows two waypoint errors. "VERDO ONE BERIK" and "VERDO ONE VERGA"
With a click on the wrong line the Manual Maintenance opens
B) shows the Manual Maintenace
There you can see the wrong order ,3,W,CY,CYYZ,NOAHA,,

next image
C) C = OK| S !! 2 : Sort is wrong by "2"
D) press Re-sort and all is good

So next month ( Dezember ) next 10 interested Users

Please send a PM to me
============================================================
Currently: 10 "Project FMC simplified for Project Airbus" users per month.
This limit should suffice to check any questions and bugs.

The personal message (PM) should have following content

============================================================
Full Name :
Email address (download link will be sent to ) :
============================================================

1.) that's not that easy. For legal reasons you can not just use the AIRAC data. A single user who has purchased an AIRAC cycle may do so on his computer for personal use, but not the FreeNav DB group.

2.) FD-FMC needs more data than in the Navigr. AIRAC data are present.
So a manual work at the airports is required.

But my next target for "FMC Airport Manager" is to use the AIRAC cycle for the basic data, SID STAR etc. So it is much faster to create an airport.

I am to get into negotiations with the AIRAC providers for permission.

I am to get into negotiations with the AIRAC providers for permission.

As far as I know, LittleNavMap (freeware) now comes prepackaged with an AIAC cycle from Navigraph, so chances for success are not the worst.

For generating an initial, worldwide starting point, Navigraph's AIRACs are a good idea, but I doubt that you can obtain constant updates for them without investing a considerable amount of money. So future updates might have to be done manually (by using your tool).

1.) that's not that easy. For legal reasons you can not just use the AIRAC data. A single user who has purchased an AIRAC cycle may do so on his computer for personal use, but not the FreeNav DB group.

2.) FD-FMC needs more data than in the Navigr. AIRAC data are present.
So a manual work at the airports is required.

But my next target for "FMC Airport Manager" is to use the AIRAC cycle for the basic data, SID STAR etc. So it is much faster to create an airport.

I am to get into negotiations with the AIRAC providers for permission.

I tried to look for the VREF in the FMC in approach mode but I am guessing it is in the approach tab but that is not clickable unless you load a star and approach, so it is impossible to find it for most airports.

Since the project has come a long way, how about renaming it to something catchy and more representative? Something like:
"A Free 20" (pun intended)
"Project 32x"
"Free 2x" (yes, again a pun)
"PAFDBK 32x" (initials of the main contributors)
"FFF - Free FiFi"
"Freebus 32x"
"FreeNav A32x"
...etc.

The current KORD has 16 runways. Have you thought of abandoning the SIDS and STARs seeing as LittlieNavMap can create flight plans that include SIDs, STARs and transitions from the airac for free? It seems to be a lot of wasted effort now. Then everyone would be able to use every airport at the planes full capability.

The problem with LNM's flightplans is that you'll have to set anything up before you start your flight. Every change of the SID or STAR due to runway changes would require you to minimize FSX, change the flight plan in LNM, save it and then load it into FSX. A built-in FMC database allows doing this on the fly (not sorry for the pun).

Maybe the flight plan handling can be adapted for flight plans featuring SIDs and STARs that were exported from LNM by comparing them with the A32x' internal database and therefor automatically recognizing that SIDs and STARs are already present.

Would be a good reason to investigate general flight plan saving and loading as this is one of the issues I can't get rid of with the FMC, regardless of version. Saving works fine, but every time I try to load the flight after that, FSX throws a "Error loading GPS_Engine". Not sure whether this is a known problem or not.

- Edit:

I think I know what causes the GPS_Engine error.
Flights exported by Little Navmap and used as the initial flight plan are named, e.g. "IFR Munich (EDDM) to Hamburg (EDDH).pln".
Flights exported by the FMC are called, e.g. "IFR Munich to Hamburg.pln"
The [GPS_Engine] section, "Filename=" line in the .flt file, however, points to "IFR Munich (EDDM) to Hamburg (EDDH)", which causes the error (form some reason).
If I manually edit the .pln file to point the "Filename=" line to "IFR Munich to Hamburg.pln", the flight and FMC data is loaded without error!

This makes things a bit complicated since users need to save their flight plans from Little Navmap with the exact same name that would be used by the default flight planner!

What ATC are you talking about? Pro ATC automatically updates Sids and stars dependent on any changes, the FP doesnt have any SIds and Stars until you request clearance and then they are assigned,. It should be ok with the default ATC but I don't know about others. That's why I asked if it was possible.
I know the plane doesn't reload if a new flight plan is added as long as its either the same name or same ICAOs involved.

You would also be using current data instead of 10 year old data. It was just a thought, I was 99% sure everyone would say no!

I wasn't talking about ATC, but the A320's FMC and autopilot.
ATC doesn't care what SID and STAR you take and whether they were loaded with the initial flight plan or added from the FMS since you're mostly left to your own devices (depending on the ATC client used).

The current KORD has 16 runways. Have you thought of abandoning the SIDS and STARs seeing as LittlieNavMap can create flight plans that include SIDs, STARs and transitions from the airac for free? It seems to be a lot of wasted effort now. Then everyone would be able to use every airport at the planes full capability.

Hello FLyer,

I agree that LittlieNavMap seems to be a good tool to create flightplan. But I suppose that it can only create a flight plan so just only waypoints sequence without any data; FSX flightplan format cannot include any data (speed/procedure/constraint) with waypoint.

At the origin, I created FD-FMC project for beginners, who want to discover a FMC and a flight management (true vertical navigation). The main part of the project is the aircraft/engine management to climb and descent.
So, avoid that user enter manually many data during preflight, this data are include in the airport's files that we create.
Freenav files are not only waypoint list, but more (for STAR and approaches) with speed constraints, altitude constraints, procedure (holding pattern, DME ARC, teardrop turn, no-standard approach gradient etc.....). When FD-FMC read Freenav airport files, it get all information to manage the flight and controls the autopilot, engines, and flight controls.

All this data cannot be include in a .PLN file.

By use a software like LittlieNavMap, you get a solution like VasFMC; You have SID, STAR and approaches, but that's all. No true vertical navigation. You aircraft must be in SPEED mode and vertical speed mode, so totally unrealistic....

the main part of FD-FMC is not what you see (horizontal navigation) but the aircraft system control (vertical navigation).

The only other way is only to use a payware aircraft with a payware AIRAC.

I know that my system is not perfect, but it is a simple way to learn how works a FMC, for free. And create airport files is very interesting and gives many pleasure.

All page works.
LEGS page has a provisional waypoints's altitude information (false for descent at this time)

Now, you can select/enter/delete SID, STAR and approaches.
I added a security for the delete function.

- Holding button can engage an holding pattern (not tested) when waypoint is active in the flight plan and has an holding pattern.
- Approach page has a new information : Predictive landing weight. This data is calculated during take off
- some info may be missed
- some bug may be expected
- EXECUTE button activate the FMC
- Arrows buttons scroll SID/STAR/Approachs lists.

Yes, you are right, I thought the procedures were saved as user waypoints in the .pln. I know it can be done as pro atc uses a .pln that has sids and stars in it meaning any plane that uses the default navigation becomes an aircraft that that fly airac procedures.