December 29, 20187 yr I have recently installed the PMDG 747-400 v3 in P3D v4 (after switching from P3D v3), and I noticed today that the runway numbers at EGPK Prestwick (UK2000 Prestwick Xtreme) are not identified correctly in the FMS. The main runway is designated as 13/31, but this should be 12/30. This was not a problem in P3D v3, so I am not sure how to correct this. I have run the MAKERWYS utility to update the RAAS data, but I assume that the FMS information is in a separate database. Can someone please let me know if I have just forgotten an install/setup procedure? If not, is this something that I can easily correct? Edited December 29, 20187 yr by Christopher Low Christopher Low AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme UK2000 Beta Tester
December 29, 20187 yr Commercial Member 28 minutes ago, Christopher Low said: I have recently installed the PMDG 747-400 v3 in P3D v4 (after switching from P3D v3), and I noticed today that the runway numbers at EGPK Prestwick (UK2000 Prestwick Xtreme) are not identified correctly in the FMS. The main runway is designated as 13/31, but this should be 12/30. This was not a problem in P3D v3, so I am not sure how to correct this. I have run the MAKERWYS utility to update the RAAS data, but I assume that the FMS information is in a separate database. Can someone please let me know if I have just forgotten an install/setup procedure? I fnot, is this something that I can easily correct? Christopher. Are you using the latest navdata? Chris Makris PLEASE NOTE PMDG HAS DEPARTED AVSIM You can find us at http://forum.pmdg.com
December 29, 20187 yr Author No, I am using the navdata that is supplied in the 747 package. However, the runways at Prestwick were correctly identified in P3D v3. I think I saw a post somewhere about deleting the navdata file, and this would be rebuilt. Is it possible that the runway data from the default version of the airport was used when I first installed the 747 in P3D v4? Edited December 29, 20187 yr by Christopher Low Christopher Low AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme UK2000 Beta Tester
December 29, 20187 yr Commercial Member 45 minutes ago, Christopher Low said: No, I am using the navdata that is supplied in the 747 package. However, the runways at Prestwick were correctly identified in P3D v3. I think I saw a post somewhere about deleting the navdata file, and this would be rebuilt. Is it possible that the runway data from the default version of the airport was used when I first installed the 747 in P3D v4? If you have the old navdata then the FMC will read these, and these are contain the old numbers most probably. Most probably in P3Dv3 you had a newest version of navdata? You can try deleting the ARPT_RWY.dat from {SIM}\PMDG\NavData but most probably will not solve the issue Edited December 29, 20187 yr by Olympic260 Chris Makris PLEASE NOTE PMDG HAS DEPARTED AVSIM You can find us at http://forum.pmdg.com
December 29, 20187 yr Author I was using the 747 package navdata in P3D v3, and that correctly identified runway 12/30 at Prestwick. Christopher Low AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme UK2000 Beta Tester
December 29, 20187 yr According to Wikipedia, the runway numbering at EGPK changed from 13/31 to 12/30 in November of 2013. If the installed nav database or airport scenery is older than 11-2013, it would have the original numbering. You can check the effective date of the AIRAC on the FMS IDENT page. Most likely the first database release to contain the new runway numbering would have been 2013-12 Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
December 29, 20187 yr the pmdg B747 was released in 2016/2017 around that period. so the default data was also from that period. Koen Meier
December 29, 20187 yr Commercial Member 13 minutes ago, ph-cxz said: the pmdg B747 was released in 2016/2017 around that period. so the default data was also from that period. True but if he has let's say NGX installed and he installed NGX first then the Airac that NGX was shipped will be in use. Our installers do not overide any installed Airac. Chris Makris PLEASE NOTE PMDG HAS DEPARTED AVSIM You can find us at http://forum.pmdg.com
December 29, 20187 yr Author I did indeed install the NGX first......but then so did 99.9% of NGX customers, since that was released first. That being the case, how do I resolve this issue? Edited December 29, 20187 yr by Christopher Low Christopher Low AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme UK2000 Beta Tester
December 29, 20187 yr the only solution i think would be to purchase one month of navigraph Robert Marton
December 29, 20187 yr 21 minutes ago, Christopher Low said: I did indeed install the NGX first......but then so did 99.9% of NGX customers, since that was released first. That being the case, how do I resolve this issue? You can do a one-month one-time subscription from Navigraph to update your AIRAC to the current version. If you choose that option, and have other add-ons that use custom Nav data, take the opportunity to download the latest AIRAC files for those as well, since the Navigraph subscription entities you to download files for every add-on they support during the subscription period. Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
December 29, 20187 yr Author You are all missing the point. When I had these aircraft installed in P3D v3, the main runway at Prestwick was correctly identified on the FMS as 12/30. I have never subscribed or obtained any Navigraph updates to anything, so the correct information is almost certainly included in one of the PMDG packages. Christopher Low AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme UK2000 Beta Tester
December 29, 20187 yr Quoting a response from Tabs to a similar problem: "The airplane does ship with the latest Navdata (1702) but we do not automatically overwrite older data because there are people who deliberately fly using outdated data for compatibility with FSX ATC, scenery, custom made procedures, etc. If you want the latest one to install, do this: 1. Go to your <sim root>\PMDG\ folder - delete the NAVDATA and SIDSTARS folders. 2. Rerun the 747 installer and choose repair. It should put the 1702 data in". Steve Weeks
December 29, 20187 yr Author Thanks, Steve. That seems to have done the trick Christopher Low AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme UK2000 Beta Tester
Archived
This topic is now archived and is closed to further replies.