Jump to content

Hanse

Deputy Sheriffs
  • Content Count

    2242
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Hanse

  1. Miguel, sorry, but are we developers not allowed to take some days off after all these weeks and why this is such an important problem for which you need an immediate answer? Until now you are the only user complaining about this feature APP SPEED LIMITER in general. In the next couple of days I will have a look into this feature...... Regards, Rolf
  2. Hi Miguel, you should be a little bit more precise and what do you mean by "it is on a platform" and "it does not need pushback"? Currently the MCDU3 GSX OPTION has nothing to do with any other GSX option like boarding, refueling etc. and its only function is currently in connection with pushback. This will be changed in the near future...... More details when this functionality is available. To summarize even if the MCDU3 GSX OPTION is disabled you can use all the other GSX features. We do not have the possibility to interface with GSX PUSHBACK because it does not offer this functionality e.g. we do not get any data from GSX to know which GSX PB option the user selected and GSX PB state and when it is finished. This means we have to assume when the pushback is finished and this we do by using engine start and add some time to it after both engines are stabilized. I already told you that in case no pushback is required just start both engines and WAIT..... the CL then will commence like normal with the After Engine Start CL! If you have a problem with the CL p.e. you do not know what to do then you can use SKIP ITEM to continue with the next CL item....... Regards, Rolf
  3. Sorry, I cannot reproduce the issue. Your are right, when this option had been implemented the settings could not be saved. But in the mean time this has been changed and I just tested it and the feature works e.g. the settings are saved. So please update to the current experimental version....... Regards, Rolf
  4. There is no "connection" between GSX and the Aerosoft Airbus because from GSX we get no information what kind of pushback the user selected and when it has been finished. So the CL assumes that the PB takes a certain time and that both engines are running. This means you have to start both engines, wait some time and then automatically WAIT will appear on the INFOBAR and the AFTER START CL begins....... Regards, Rolf
  5. Mika, I think this problem is related to using your own "Voice Checklist". The CL has been dramatically changed since the 32bit veersion e.g. a lot of actions / calls have been added / modified as well as the sequence changed (based on requirements from RL pilots). We can support only original installations. So try to use the original voiceset delivered with the Professional P3D v4 and if the issue still persists please come back..... Regards, Rolf
  6. Marc, unfortunately the documentation has not been updated yet. The functionality is still there but the location has been changed: Use on the MCDU the DATA key and then change to page 2. On that page 2 you will find a menu item called: PILOTS ROUTES. Select the appropriate LSK and a screen will open in which you can enter the name of the to be saved flightplan ....... Enter the name and the flight plan will be saved. Next time you enter this name into the field "COMPANYROUTE" it automatically will be loaded...... Regards, Rolf
  7. Hi Mika, Sorry nothing has been changed in this respect in the version 1.2.1.5. So I do not understand what happens on your system resp. that you get such a message. Please be a little bit more specific and give me more details: Exactly at which altitude happens it, was it during a complete flight or did you started using a saved flight situation, what was your flight level you descended from, what is the transition altitude e.g. happens it before or after passing transition altitude....... etc. Regards, Rolf
  8. This a flight level change and not a descent as you are describing it in your message. Did you enter the new "cruise level" into the MCDU (INIT A page) before starting to descend? The same you would do in case of a higher flight level......! Try again and report what happens then........
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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. I would not suggest to modify the panel.cfg because you have to do it for every type and it could happen that also an update overwrites your modifications. If you want to make up your own views then you have to use a seperate tool like ChasePlane, EZDOK or SimpleCam..... All of those give you the flexibility to create your own views and to define the "start" view. Regards, Rolf
  15. Normally those values should be automatically calculated after entering the FLAPS setting for TO........
  16. Now I am completely out of options because no other user reported those various issues and I am not able to reproduce it. The only advise I can give you is to completely deinstall the Aerosoft Professional Airbus (using the Windows functionality and afterwards "cleaning" maybe remaining files in the various directories) and then to reinstall it again. Download the actual version from your account and then run the Updater to bring it up to the current exprimental version 1.2.1.3. Maybe the following thread has some important information on the procedure....... Regarding the INFOBAR and the "LEAVE RUNWAY" massage: Did you enable the resp. option in the MCDU3 under OPTIONS / CHECKLISTS and INFO BAR e.g. is ON displayed in green? Then you should see the explained message.......
  17. First I see from your screenshots that you already left the runway...... I would like you to enable the INFOBAR in the MCDU3 under CHECKLIST. Then after breaking stay on the runway and slow down to below 30 knots. After you see the message "LEAVE RUNWAY" on the INFOBAR you can leave the runway....... Please also answer my question what were the calls you hear after touch down and especially which were the last one....... Without those informations I am not able to help...... Regards, Rolf
  18. Sorry, but I have to come back to this topic. One of our RL pilots corrected me and stated that manual breaking when autobrakes are enabled is common SOP. And because of that I tried it myself with the Airbus 320 CFM. When I started manual breaking automatically the autobrakes were disabled. And also the CL commenced - but I stayed on the runway until the INFOBAR showed "LEAVE RUNWAY"...... The copilot set Landing Lights to off, the APU to on and then the AFTER LANDING CL started. If this does not work on your system please tell me exactly what happened after the autobrakes automatically were disabled. Because I will be absent this week I will come back to you during the next weekend. Regards, Rolf
  19. Autobrakes MAX: OK my mistake - in flight not possible to set like in RL...... Regards, Rolf
  20. Hi, we just modelled "normal" procedures. What you are doing e.g. using manual brakes when the autobrakes are still on is never done in real life. If it is a "short" runway then you should set the autobrakes to MAX and use the reversers until the plane is below 70 knots. Use manual breaking only if the autobrakes are set off by the copilot. Your speed should below 30 knots before you try to leave the runway...... Between 70 and 30 knots (before leaving the runway) the copilot makes all the other necessary actions like p. e. setting the AP to off etc. Then you will see the message on the infobar "LEAVE RUNWAY" and only after that message appeared you should leave the runway....... After leaving the runway the copilot sets off the landing lights and starts the APU. After the AFTER LANDING CL will automatically start! Regards, Rolf
  21. The issue has been closed because it has been solved e. g. the user had no more any problems. OK, first I assume that you are also using the copilot and did you update to the latest version? After touchdown what are you hearing from the copilot e.g. what is he doing? Please tell me exactly the sequence resp. his confirmations. Do you hear p. e. autobrakes off, does he also set the autopilot to off etc.? Do you get the message "LEAVE RUNWAY" on the INFOBAR? After leaving the runway does he set the Landing Lights to off and the starts the APU? After that normally the AFTER LANDING CL Sorry I need all those details to find out when exactly the checklist sequence stops on your installation.....? Regards, Rolf
  22. The next step after activating the batteries is to establish Power e.g. EXT PWR or to start the APU. After EXT PWR or APU is available set the strobe light to AUTO and the navigation lights to ON. Then lighten up all screens e.g. PFD, ND as well as upper and lower ECAM. Then you can start the cockpit preparation CL from C&D. If you enabled the copilot the CL will run through and all necessary settings are made by the copilotautomatically - with one exception: The parking brakes have to be set ON manually after the respective PF call. If this does not work as described above then there is a problem with your installation...... Deinstall the Aerososoft Airbus completely using the Windows functionality, manually delete all remaining folders / files and newly reinstall the Airbus. Regards, Rolf
  23. The Cockpit Preparation Checklist needs to start properly the C&D or TURNAROUND aircraft state to be defined in the MCDU3 menu first. This is the basis that all settings are made before the CL starts and that the settings it expects are already done. My next question then is: Did you use the copilot or not? If you enabled the copilot normally he then should make all necessary settings (except setting the parking barkes to ON). If this all does not work on your system then please tell me which was the last call you heard before it stuck! Regards, Rolf
  24. 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.
  25. 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.
×
×
  • Create New...