If you want a Honeycomb Alpha for Christma you better order fast because we are quickly running out of stock!

Jump to content

Hanse

Deputy Sheriffs
  • Content Count

    2349
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Hanse

  1. 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.
  2. 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.
  3. Dave, you are writing "when something out of the ordinary happens" and that this is the problem. The whole functionality is based on normal procedures / certain assumptions and it means that a GA is performed on FINAL e.g. on the final leg with no more waypoints with altitude constraints to the runway, glide slope and localizer are captured, GA altitude set , etc.. Try it that way and everything in connection with a GA works as required. There is no specific CL but in that case certain actions are automatically performed (based on certain settings) by the crew like FLAPS UP and GEAR UP etc. and you can fly another approach with all CL working well. The checklists cannot cover abnormal situations because each CL is based on certain assumptions / settings - and there is no possibility to think about and cover all possible varieties. In your case I would suggest to follow the flight path and wait until the plane is in the state as described above and then engage GA...... Regards, Rolf
  4. Luis, I fixed the bug and now also on SBSP (and on all other airports where the difference between magnetic and true heading is greater than 15°) you get the message "LEAVE RUNWAY" and the following actions are excuted like on all other airports..... The fix will be part of the next experimental update. Regards, Rolf
  5. If I use the SimStarter to "compose" a flight e.g. plane and location at SBRJ (Rio de Janairo / Brazil) RWY 20L (please see screenshot attached) the plane is not aligned with the runway. But if I use the P3D v4.4 menu to do the same everything is OK e.g. the plane is aligned to the runway. I think that there is a problem with magnetic and true headings.... by the way runway headings are allways magnetic! Regards, Rolf
  6. 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.
  7. 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.
  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. Luis, regarding the "LEAVE RUNWAY" message and the further to its related actions (please do not hijack this thread for additional issues like reverse thrust): In the mean time I found the root cause and it is related to landings on airports of the Southern Hemisphere e.g. flying in North America and Europe there are no such problems..... I am working on the solution and as soon as it is available I will let you know...... Regards, Rolf
  10. The whole installation of the Aerosoft Airbus should be in the folder C:\User\Your Name\Documents\Aerosoft\........and after that you should have 4 or 3 folders depending on the models installed Aerosoft A318-A319 Profeesional Aerosoft A320-A321 Professional ASUpdater General Regards, Rolf
  11. Luis, I made some tests myself on various airports and normally it works fine - please try again on another airport. The message LEAVE RUNWAY should appear if the plane is below 30 knots. But I also experienced the same problem like you (no message) after landing on SBSP 34L. First I thought that the problem is maybe connected to the airport elevation (app. 2600 feet) but also at LOWI (app. 1900 feet) as well as at KEGE (app. 6500 feet) it worked e. g. the message appeared when slowing down below 30 knots. So at the moment I am a little bit confused what is different on the SBSP 34L approach compared to other approaches..... as on all the other airports the feature is working well. I told you already that I will have a look into it...... if I find something I will let you know....... Regards, Rolf
  12. The problem might be in connection with your handling or settings e. g. where everything is installed..... The "red" message means that the MCDU3 cannot find the LOADSHEET where it is supposed to be located or that there is no one for this model of the Airbus. So first you should check if you really selected in the fuelplanner the right model - aircraft type. And second after using "Generate Loadsheet" there should be a file available in C:\User\Your Name\Documents\Aerosoft\General\A3XXX Fuel Planner\Loadsheets\......for the specific aircraft type..... Regards, Rolf
  13. I think 1940 m should be enough for a smooth landing - of course depending on your weight. I cannot believe that reversers are used until the last exit - those should be set off at 70 knots...... I think the problem was that your touchdown was maybe quite late...... I suggest that you try it again and maybe touch down a little bit earlier. I just tried a landing at SBSP34L with the A321 and there were no such problem with the runway length. But you are right the "LEAVE RUNWAY" message did not appear and I will have a look into this issue. Let you know when I found something. Please be patient...... Regards, Rolf
  14. Hi, the whole GSX2 immersion into the Aerosoft Airbus is still WIP! We are currently adjusting the MCDU3 accordingly and and are also waiting for new variables from FSDT ....... So please be patient until the "completion" is finally announced..... Regards, Rolf
  15. Luis, the PFD displays what the aircraft is capable of and not the ILS categrory of the airport your are using....... so everything in this repsect OK. And I think the other problem is related to your handling: You are leaving the centerline of the runway too early e.g. the plane has to slow down to less than 30 NM ...... Please have a look into the following discussion with the same isuue...... Regards, Rolf
  16. The best thing to "reset" the CL (if you are stuck and you do not knwo what to do) is to load one of the predefined AIRCRAFT STATES again...... Regards, Rolf
  17. Sorry, NO. What you did was not a normal SOP and in the Airbus the CL only covers normal procedures...... You should have entered in the MCDU LTFJ as alternate destination and adapted the flight path accordingly as well as the FL. Then the CL would have recognized those changes and would proceed the normal way. For each of the various CL states a certain aircraft state is the basis to start and this happens when the plane is on the ground and you are using one of the 4 predefined aircraft states. But to define various aircraft states when the plane is in the air is not possible because there are so many variables which could be different....... Regards, Rolf
  18. We are currently still working on the GSX-immersion and until now it is not completely finished e. g. it is still "under construction" and WIP. So please be a little bit patient....... Regards, Rolf
  19. Skydiver, normally there is also a CL part "GoAround" so I do not know why the system quits in your case. It should automatically be engaged in case you are setting the Thrusts Levers to TOGA. Please try again. If it does not work please tell us exactly what you did and in which CL stage you started the GA e.g. what were the last calls / actions of the CL....... Also was the Copilot engaged? Regarding your second issue I suggest to open another thread in the MCDU section of this forum because it is a different issue...... Regards, Rolf
  20. APP SPEED LIMITER I am currntly working on this feature and the new updated and enhanced version will be released soon....... but this does not solve the problems when wrong data are used........ Regards, Rolf
  21. Finally we found out that this problem was related to the Joystick setup and not to CL. Because we believe this topic has been solved we have closed it. If you have any more questions feel free to open a new topic.
  22. Hi, I had some other ideas what could cause your problem: Did you disable the NSW Steering / Tiller before doing the Rudder Check? This is RW ops...... Maybe you should re-calibrate your rudders...... What does the rudder trim on the pedestal states...... Regarding the video issue I suggest to open a new thread in the right section because then specific people (with the resp. knowledge) will look into it...... Please, never use one thred for various issues.... Regards, Rolf
  23. Hi, sorry but then I think this has nothing to do with the CL but with the setup of your joystick / rudder...... I am also not able to reproduce this problem and until now no other user reported such a problem. The only thing I can suggest is that you open a support ticket and then someone will try to find / solve your specific problem...... Sorry. Regards, Rolf
  24. Hi, does this also happen if you use "SKIP ITEM" for the rudder check? What are your settings P3D v4.4 Options / Realism / Flight Controls - Use Autorudder = unchecked? MCDU3 OPTIONS / AIRCRAFT / AUTO RUDDER = OFF? Regards, Rolf
  25. After a lot of investigation with ARTOX67 it is now clear that the problem was based on various not up-to-date files used in the installer. Users having the same issue please "update" (using experimental updating) your system.
×
×
  • Create New...