wulfbindewald wrote:thanks for the draft installation guide, Francois.
1) page 1: The name "Modules" is a FSX folder name, but it is not intended to put and install anything into "Modules".
For risk prevention I recommend to rename it e.g. Modules_content or so.
2) Chap 6-9: I am not quite sure if an installation guide of 6(!) closely described pages are "motivating" to do this complex installation.
So I propose only to describe the installation in a
pure and lite installation process as already done in chap 2-5. No explanations. Only take this and put it there. Nothing else.
3) For those who are looking for add. informations there can be added a separate appendix with all background informations, why to do so/author/versions/risks/propable upcoming updates (airports, Airac..) ....
IMHO the lite installation guide can be reduced to 2 customer friendly pages
Wulf
Hi Wulf,
1) I understand what you mean. I renamed "Modules" folder in "Modules_Required" folder, to avoid confusion.
2) & 3) If you don't declare the DLL's, FMC gauge cannot work . Even if you don't want use airports database (SID/STAR), nothing will work in managed mode. You can not even enter an altitude value or Thrust. Nothing will work because the FMC keyboard use XMLTools/XMLTools3D.
So I think that the aircraft has no interest without FMC functions (even if you don't use SID/STAR).
THis is the reason why I think that it is indispensable to install the DLL's. Procedure is not very complex; And I have began, one year ago, to write a "Setup" installer in Visual Basic 6. I have stop, because people told me that this automatic installation was not important. But if you think that installation will be too complex for people, I can finish this "Setup.exe" with an automatic installation.
But I havn't past 3 years to write these gauges if they are not used. I know that people think that this is the visible gauges which are required the most work, but not, tThese are the 21 hidden gauges that given to me the most work (all the algorithms that manage the climb/descent with constant thrust, all the vertical navigation control of the aircraft).
Last change, about the V/S reading on the VSI takes me 5 hours to works fine. The code which control the climb (pitch in managed mode) takes me 6 months of work !! But like it is not visible, people cannot know the difficulties.....
Ask to you the following question : Why a FMC witha true vertical navigation doesn't exist in freeware ? VAS-FMC is a pretty gauge, with a real look, but it has no vertical management. Very hard to code !
The320Pilot wrote:Francois, as you are now in the process of modifying the code of the A320 FD-FMC, is there still no way to add missed approaches? Perhaps in a later update?
SKCL is almost finished (again). I'll send it to you this week.
Missed appraoch is not a problem of gauge code, but a problem linked to the airport data file format. I have created the files format inthe same time of the panel. When I began to work on the panel, my knowledge in XML was very little. And the first file format that I have created is the SID format. This is the reason why, SID are limited, because at that time, I did not know I could create a complex code. his is the reason why SID format can manage only one type of constraint.
I have designed STAR and Appraoches file format later, and this is the reaon why these files have more information and can manage speed and altitude constraint at each waypoint, because my panel was moore advanced.
But today, it is impossible to change file format, otherwise, all airports already realized would be unusable.
I can find a tip to add missing approach data in appraoches files, by use the 3 last column of each approach line, but Airport creation will be more complex, and already, I find that few people involved in the Airports data creation project. So I do not want complicated matters.
Today, It is very simple to use the tool kit, and I would like more people join the group....and I am afraid to discourage people if I add again new functions.
Today, the FMC has a basic missed approach system (when you have loaded an approach) ; If you disconnect A/THR, just before landing and you set your throttles to TOGA, you engage a basic GO Around mode, which re-init flight plan and data at the first waypoint of the approach data (with altitude and speed).
This system works perfectly, except if airport is surrounded by mountains, because track to join the first waypoint of the approach is not the official track of a missed approach, but just a "direct to" from the runway theshold and the first wyapoint of the approch.
I know that my system is not perfect, but actually, I want stop the developement, to publish the aircraft, and adapt as soon as possible to other Project Airbus Aircraft.
When A318,A319,A321, A330 and A380 will be FMC ready, I will come back on the panel and improve it.
But today, I am tired, and I want finish.
Otherwise, there will be always something to add and A320 will never completed.........no end ! no limit !
New features will be for panel updates.
François
