!! Windows 7 no longer supported !!

As Microsoft will stop supporting Windows 7 on Jan 20th we will be unable to test any of our
products on that platform. It may work, or it may not, but no guarantees from our side. 

Jump to content

Hanse

Deputy Sheriffs
  • Content Count

    2522
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Hanse

  1. Please enable in the MCDU3 - OPTIONS - VIEWS and then the VIEW SYSTEM to ON as well as the EXTERIOR VIEW BAR......!
  2. This issie should have been solved already with 1.0.0.6! So please update to the current version 1.0.0.7!
  3. Hi Rich, confirmed e. g. there seems to be a problem and I will have a detailed look into the code next week. It means there is nor more need to prepare a video! Let you know when I have finished my investigation. Regards, Rolf
  4. Jonas, I just checked it in the A320 CFM and the CVR is automatically switched OFF after the two engines are started. So please tell me more about the issue you detected. Are you talking about the Professional e.g. the 64 version? Which model you used e. g. A318/A319, A320/A321 or the A330? Please check if the CVR is automatically switched OFF after both engines are started and AVAIL The reason is quite simple as it should not be ON during the whole flight because this is the normal procedure e.g. the CVR is automatically running. It is manually set to ON during cockpit preparation also to cover the period until the engines are started and fully available. Regards, Rolf
  5. Please update the A330 to 1.0.0.7 which ar least should solve this issue....... Regarding your other issue. The appearence of the message that the "Descent Prep CL" will start in ..... is calculated in a different way and has nothing to with the display of the T/D on the MCDU as well as the ND. Normally the T/D is already calculated when all flight preparations are finished e. g. all relevant information entered in the MCDU and that means a complete finished INIT B page / FUEL PREDICTION including ZFW/ZFWCG and BLOCK fuel. So please after that check the F-PLAN page and the T/D pseudo waypoint should be already there and calculated. Regards, Rolf
  6. Thanks for your information and we will check this. Regards, Rolf
  7. Marcus, in respect to GA nothing has been changed since a long time and it should work as required even on the A330. A detailed GA description you find in the A31X/A32x documentation folder "Vol6 Step-by-Step Tutorial" in chapter 12.22 on page 122. One question: After initiating GA did you remove the F-PLAN DISCONTUNITY between the GA flight path and a new approach? Regards, Rolf
  8. A new update 1.0.0.7 is available now which regarding the checklist and copilot solves the following issues: BEFORE ENGINE START CL: Starting issue in connection with GSX closing doors - solved - ECAM PAGES: Manually selected by CL are now reset to standard when next CL item is called CHRONO FO: Set ON when takeoff thrust is set and stopped after landing VC LIGHTS: When C&D as well as TO state is used VC-lights are automatically set to "flight" when TAXI CL is started LANDING LIGHTS: Were not really ON after descending below 10k feet even that OVHD switch was ON - solved BEFORE TAKEOFF - Landing Lights are now automatically switched on when plane enters the departure runway. I therefore will close this topic and ask you if there are still " checklist issues" to open a new thread. Regards, Rolf
  9. A new update 1.0.0.7 is available now which regarding the checklist and copilot solves the following issues: BEFORE ENGINE START CL: Starting issue in connection with GSX closing doors - solved - ECAM PAGES: Manually selected by CL are now reset to standard when next CL item is called CHRONO FO: Set ON when takeoff thrust is set and stopped after landing VC LIGHTS: When C&D as well as TO state is used VC-lights are automatically set to "flight" when TAXI CL is started LANDING LIGHTS: Were not really ON after descending below 10k feet even that OVHD switch was ON - solved BEFORE TAKEOFF - Landing Lights are now automatically switched on when plane enters the departure runway. I therefore will close this topic and ask you if there are still " checklist issues" to open a new thread. Regards, Rolf
  10. A new update 1.0.0.7 is available now which regarding the checklist and copilot solves the following issues: BEFORE ENGINE START CL: Starting issue in connection with GSX closing doors - solved - ECAM PAGES: Manually selected by CL are now reset to standard when next CL item is called CHRONO FO: Set ON when takeoff thrust is set and stopped after landing VC LIGHTS: When C&D as well as TO state is used VC-lights are automatically set to "flight" when TAXI CL is started LANDING LIGHTS: Were not really ON after descending below 10k feet even that OVHD switch was ON - solved BEFORE TAKEOFF - Landing Lights are now automatically switched on when plane enters the departure runway. I therefore will close this topic and ask you if there are still " checklist issues" to open a new thread. Regards, Rolf
  11. A new update 1.0.0.7 is available now which regarding the checklist and copilot solves the following issues: BEFORE ENGINE START CL: Starting issue in connection with GSX closing doors - solved - ECAM PAGES: Manually selected by CL are now reset to standard when next CL item is called CHRONO FO: Set ON when takeoff thrust is set and stopped after landing VC LIGHTS: When C&D as well as TO state is used VC-lights are automatically set to "flight" when TAXI CL is started LANDING LIGHTS: Were not really ON after descending below 10k feet even that OVHD switch was ON - solved BEFORE TAKEOFF - Landing Lights are now automatically switched on when plane enters the departure runway. I therefore will close this topic and ask you if there are still " checklist issues" to open a new thread. Regards, Rolf
  12. A new update 1.0.0.7 is available now which regarding the checklist and copilot solves the following issues: BEFORE ENGINE START CL: Starting issue in connection with GSX closing doors - solved - ECAM PAGES: Manually selected by CL are now reset to standard when next CL item is called CHRONO FO: Set ON when takeoff thrust is set and stopped after landing VC LIGHTS: When C&D as well as TO state is used VC-lights are automatically set to "flight" when TAXI CL is started LANDING LIGHTS: Were not really ON after descending below 10k feet even that OVHD switch was ON - solved BEFORE TAKEOFF - Landing Lights are now automatically switched on when plane enters the departure runway. I therefore will close this topic and ask you if there are still " checklist issues" to open a new thread. Regards, Rolf
  13. A new update 1.0.0.7 is available now which regarding the checklist and copilot solves the following issues: BEFORE ENGINE START CL: Starting issue in connection with GSX closing doors - solved - ECAM PAGES: Manually selected by CL are now reset to standard when next CL item is called CHRONO FO: Set ON when takeoff thrust is set and stopped after landing VC LIGHTS: When C&D as well as TO state is used VC-lights are automatically set to "flight" when TAXI CL is started LANDING LIGHTS: Were not really ON after descending below 10k feet even that OVHD switch was ON - solved BEFORE TAKEOFF - Landing Lights are now automatically switched on when plane enters the departure runway. I therefore will close this topic and ask you if there are still " checklist issues" to open a new thread. Regards, Rolf
  14. A new update 1.0.0.7 is available now which regarding the checklist and copilot solves the following issues: BEFORE ENGINE START CL: Starting issue in connection with GSX closing doors - solved - ECAM PAGES: Manually selected by CL are now reset to standard when next CL item is called CHRONO FO: Set ON when takeoff thrust is set and stopped after landing VC LIGHTS: When C&D as well as TO state is used VC-lights are automatically set to "flight" when TAXI CL is started LANDING LIGHTS: Were not really ON after descending below 10k feet even that OVHD switch was ON - solved BEFORE TAKEOFF - Landing Lights are now automatically switched on when plane enters the departure runway. I therefore will close this topic and ask you if there are still " checklist issues" to open a new thread. Regards, Rolf
  15. A new update 1.0.0.7 is available now which regarding the checklist and copilot solves the following issues: BEFORE ENGINE START CL: Starting issue in connection with GSX closing doors - solved - ECAM PAGES: Manually selected by CL are now reset to standard when next CL item is called CHRONO FO: Set ON when takeoff thrust is set and stopped after landing VC LIGHTS: When C&D as well as TO state is used VC-lights are automatically set to "flight" when TAXI CL is started LANDING LIGHTS: Were not really ON after descending below 10k feet even that OVHD switch was ON - solved BEFORE TAKEOFF - Landing Lights are now automatically switched on when plane enters the departure runway. I therefore will close this topic and ask you if there are still " checklist issues" to open a new thread. Regards, Rolf
  16. A new update 1.0.0.7 is available now which regarding the checklist and copilot solves the following issues: BEFORE ENGINE START CL: Starting issue in connection with GSX closing doors - solved - ECAM PAGES: Manually selected by CL are now reset to standard when next CL item is called CHRONO FO: Set ON when takeoff thrust is set and stopped after landing VC LIGHTS: When C&D as well as TO state is used VC-lights are automatically set to "flight" when TAXI CL is started LANDING LIGHTS: Were not really ON after descending below 10k feet even that OVHD switch was ON - solved BEFORE TAKEOFF - Landing Lights are now automatically switched on when plane enters the departure runway. I therefore will close this topic and ask you if there are still " checklist issues" to open a new thread. Regards, Rolf
  17. A new update 1.0.0.7 is available now which regarding the checklist and copilot solves the following issues: BEFORE ENGINE START CL: Starting issue in connection with GSX closing doors - solved - ECAM PAGES: Manually selected by CL are now reset to standard when next CL item is called CHRONO FO: Set ON when takeoff thrust is set and stopped after landing VC LIGHTS: When C&D as well as TO state is used VC-lights are automatically set to "flight" when TAXI CL is started LANDING LIGHTS: Were not really ON after descending below 10k feet even that OVHD switch was ON - solved BEFORE TAKEOFF - Landing Lights are now automatically switched on when plane enters the departure runway. I therefore will close this topic and ask you if there are still " checklist issues" to open a new thread. Regards, Rolf
  18. There are three panels which have to be switched on CPT, FO and the one on the OVHD and in that sequence...... Regards, Rolf
  19. Meese, if you are on 1.0.0.6 there is only one thing you should do yourself (and not by GSX function) and that is manaually closing the doors! The rest works fine..... Regards, Rolf
  20. Ray, we had some problems with the trim setting but those should be solved with rev. 1.0.0.6. So please update and try again. Now the copilot really sets the trim to all the way down or up to the value stated in the MCDU. Regards, Rolf Meese, if you are on 1.0.0.6 there is only one thing you should do yourself (and not by GSX function) and that is manaually closing the doors! The rest works fine..... Regards, Rolf
  21. Sebastien, I have no idea why you have those issues on the A318-A321 because we did not touch the CL / CoP function...... Regards, Rolf
  22. Gaz, why asking the same question in several threads? We are working on it ..... so please be patient! Regards, Rolf
  23. Gaz, please be a little bit patient.... we are working on the solution. Regards, Rolf
  24. Thomas, please explain your problem a little bit more in detail so that I am able to try to reproduce the issue. What do you mean by "stuck" for LIGHTS OFF as well as for "SEAT BELTS". Are you talking after departing from SLLP at 10.000 resp. 20.000 feet? Normally those functions are based on the actual altitude of the plane regardless the altitude of the departing airport. I just realized that SLLP is already at app. 13.000 feet e. g. the "LIGHTS OFF" are already triggered before TO. This is a special situation for which I currently have no solution........ Rolf
  25. This issue should be solved after updating to 1.0.0.6
×
×
  • Create New...