Hanse

Deputy Sheriffs
  • Content Count

    2111
  • Joined

  • Last visited

  • Days Won

    1

Hanse last won the day on July 15

Hanse had the most liked content!

Community Reputation

84 Excellent

3 Followers

About Hanse

  • Rank
    Privat Pilot - ME/IR

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Just set another aircraft state than TAKEOFF for DEFAULT. If no DEF is selected automatically TAKEOFF is loaded and then this message is correct.
  2. Hanse

    Approach CL

    Hi Goshob, EGPWS: I believe that this feature was mixed up with the Awareness Calls and therefore we can for the time being close this topic. AWARENESS CALLS: During climb and descent such calls were newly implemented into the CL based on requirements from RL pilots. 2.000 and 1.000 feet before the FCU altitude is reached those calls are made by the copilot. It is based on the FCU selected altitude and not on anything else like CRZ ALT. So if your CRZ ALT is 35.000 feet and on the FCU you selected 30.000 feet (because until now you did not get the ATC approval to climb to CRZ ALT) then there will be two calls e. g. at 28.000 and 29.000 feet. If you later change it to 35.000 then there will be additional calls at 33.000 and 34.000 feet. The same happenes during descent. I believe that explanation should be complete and understandable. LPMA Approach: In the NavDataPro DB there are the following approaches available for RWY05: RNAV 05 - Y, RNAV 05 - Z and RWY05. Looking into the charts the RNAV approaches are RNP and the difference between the two is if you arriving from North or South. As the Aerosoft Airbus is RNP 0.30 "approved" you can use both approaches and the MDA is in that case 910 feet. This is the perfect approach I used...... The RNAV (GNSS) A 05 approach is not modeled in this DB - maybe in the Navigraph DB. This one ends at MA566 with a visual final approach. But as the Aerosoft Airbus is RNP "approved" you can use those RNP approaches and they "guide" you to the runway. I think I now answered in depth all your questions and hope that in the meantime you changed your opinion regarding the Aerosoft support. As the topic of this thread is still "APPROACH CL" we now went far beyond that subject. If you have further questions please open a new topic with the appropriate headline. Regards, Rolf
  3. Hanse

    Approach CL

    Goshob, I tried both LPMA RNAV approaches and as you can see by the attached screenshots - no problems at all e.g. nice and smooth landings. I am now more and more convinced that your problems are based on your basic P3D v4 scenery. If you really want to fly such sophisticated aircrafts like the Airbus then you also should invest in the basic infrastructure...... Regards, Rolf
  4. Hanse

    Approach CL

    Goshob, You are stating that you can reproduce this issue (male EGPWS call = 2.500) on every flight? Is this correct or are you mixing it up with the copilot altitude awareness calls (see below)? But what about my question: If you get this call is also the exact radio altitude displayed at that moment on the PFD? If you caqn answer both previous questions with a definite YES then there is clearly a problem with your scenery: Please send me a copy of your scenery.cfg which you will find in the C:\ProgramData\Lockheed Martin\Prepar3D v\ folder.... so that I can check if the priorities are correct...... The copilot altitude awareness calls are something completely different than the EGPWS calls. During climb and descent the female copilot makes such calls at a difference of 2.000 and 1.000 feet before reaching the FCU altitude...... I really hope that you did not mix up the issue you stated with the awareness calls mentioned above........ Regards, Rolf
  5. Hanse

    KG - LBS on MCDU

    Did you select LBS in the MCDU3 Options Aircraft page?
  6. Hanse

    Approach CL

    Hi, first thanks for the good news that the glideslope issue disappeared after the new installation. Based on your detailed information I just made the same flight and fortunately I was not able to reproduce the 2.500 feet call until I passed the T/D (32 NM before INBOM) as well as passing INBOM itself already on descent. This means to me that the problem is based on something else but not on the Airbus software. So the question is what could cause this call. As I already told you the call is based on the radio altitude and those data are delivered by P3Dv4 and calculated from the scenery installed. For this flight I used FTX Global Base Pack and openLC Europe as well as FTX Global Vector and nothing else...... Therefore you should check the following: Can you reproduce this issue on every flight or it is just the flight EHAM-LPPT? What additional scenery is installed on your system and is the priority sequence in the library correct? What happens if you disable the scenery used for this specific flight? If you get this call is the exact radio altitude displayed at that moment displayed on the PFD? Regards, Rolf
  7. Hanse

    Approach CL

    Hi, first I allways try to reproduce the issue and then I know where to look into my code (I am the responsible developer of the MCDU3, CL and Copilot function). But in your 2 general issues (LS annoucements and EGPWS) I have no idea. As also there is not even one of a couple of thousands other users "complaining" about the same issues, it therefore must be related to the installation and not to the software. I am sorry that I was not precise enough in my last statement regarding "installation". From my point of view I would suggest a clean new installation of the Aerosoft Airbus Professional and before doing so to delete the current installation using the Windows functionality and afterwards manually deleting all maybe still remaining folders / files. If you do not know how to do this then please open another thread in the forum (not in this subforum) or try to contact support and get a ticket. Regarding your advice how to treat customers I do not accept this. If you look into this subforum - for which I take care - you will see that I tried to solve / answer all mentioned issues as fast and detailed as possible. And I am sure that it was successfull because there are today no open issues which I could not solve by telling the user what he should do or by updating the software or implementing new features. Regards, Rolf
  8. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  9. Hanse

    Approach CL

    2. Then there seems also to be a problem with this feature like with #3. Because until now you are the only user having those issues (and I am not able to reproduce) it must be related to your installation...... Regards, Rolf
  10. OK, will implement it into the Cockpit Preparation CL from C&D ...... Regards, Rolf
  11. Hanse

    Approach CL

    RL-Procedure: Before passing 10.000 feet all approach preperations (inputting of MCDU data, Autobrake setting, briefing) should be finished. Therefor the autobrake will be set before passing 10.000. Those ALT calls are a feature of the MCDU3 (Enhanced Ground Proxemity Warning) and are based on Radio ALT..... Those calls are not removed and still a feature (Localizer /Glideslope alive and captured) and I cannot reproduce the issue you are talking about e.g. it must be a problem of your installation or settings..... Regards, Rolf
  12. Ok, now I got what you mean..... e.g. the CREW SUPPLY PB is OFF if the C&D State is loaded and eletrical power is enabled. But I have two opportunities: Is this correct that the PB is OFF if the C&D State is loaded? If not then I have to correct the C&D State....... If it is correct then I have to implement the setting into the Cockpit Prep CL from C&D Please tell me which one is the correct choice........ Regards, Rolf
  13. Hanse

    translating the step by step

    Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.
  14. Hanse

    translating the step by step

    Currently the manual is still "under construction" e. g. is being updated in a lot of parts. When it is really uptodate we would appreciate your offer to translate it to Hebrew. Regards, Rolf
  15. If you load the plane, set it to C&D, switch on the eletric power (batteries and external power), light up the PFD, ND and ECAM screens and then start the CL everything works well. During the oxygen equipment check the test button is pushed and the light is going on e.g. gets green for a moment. Do you mean it has to stay on green or how / where it has to be switched on? Regards, Rolf