Treat everyone else in the forum with respect even when you disagree. We are all simmers here and no matter our differences of opinion, we share a common love of aviation, computing and simulation. Do this by clicking the username pull-down at the top right, then selecting "User Settings.
Posts that are unsigned will be quietly removed without comment by the moderators, so to make your life easy- we recommend enabling your forum signature so that you never need to remember. We do so because we feel that forums in which users must engage one another personally are generally warmer, more collegial and friendly. This is one of the few rigid rules that we enforce regularly. You took the time to be here, we want to get to know you. We do this in order to keep conversations personal and familiar.
Forgot password or user name? Sincewe have asked users to sign their real name, first and last, to all posts in the PMDG forum. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted. For additional details, refer to our Privacy Policy. We may share certain information about our users with our advertising and analytics partners. We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. Out of curiousity what were you developing and in what language?PMDG 777 P3D v2.5 takeoff and climb tutorial That should fix the problems and align the PMDG database with the sim's database.Įdit: Here is the link to the navaids website:
The good news is with more database updates (Search for FSX/P3D navigation update) and you should find a very good, easy to install package that updates the entire world navigation database. I am not sure if you'll be able to autoland if this is what is causing the problem. This may cause a NO AUTOLAND message too. If you have updated the PMDG Nav database, there is a possibility the database heading and the sim heading are different (magnetic pole drift over 10+ years adds up to a significant number in many parts of the world). You'll need to know the frequency of the localizer of the runway you're landing on, AND you'll need to know the magnetic heading of the runway. You can manually input the frequency in the FMC (NAV RAD page) and that should clear the problem.
This sounds like it might be your problem since you recently changed or upgraded the database. The other thing that can cause it is if there is a frequency or magnetic heading discrepancy. There is a hard limit before the autoland disables but I forget, maybe 1500 or 1600 feet, if you are not configured by this radio altitude autoland won't engage. Make sure your gear and flaps are configured for landing before you're under 2000 feet. The NO AUTOLAND can be caused by a few things. I landed right down the middle and taxied on and shut down. Did get a "NO AUTOLAND" message but it didn't seem to make any difference. The good news is that I have now successfully completed the tutorial flight and also managed Matt Davies' EGLL/OMDB including parking at building.
Yes I am a relative newcomer to this whole business, plus being almost 86 I'm afraid my short term memory is not as good as it was when I was an active software developer. Thanks for your supportive message James.