Jump to content
Sign in to follow this  
ojiito

No Anchorage ARRs/DEPs even after scenery update

Recommended Posts

Hi Michael,

 

I've had the ANC scenery installed for a while, but just installed the latest update for it when the 777's FMC gave the rwy 15 error.  The update makes the change from

rwy 14 to 15.  But after trying other airports that have had runway configuration changes, resulting in similar FMC errors, it is apparent that the problem is not with the ANC

scenery.

 

Stephen thanks, I'm going to try that.  I've been suspecting RAAS as the culprit, I'll try turning it off first just to narrow it down.

 

 

Alex V.

Share this post


Link to post
Share on other sites

It is not RAAS Alex, the 777 should create/re-generate the APRT_RWY.dat file found in the navigation data folder. A scenery change, running makerwy's should automatically trigger an update, this doesn't always occur. Ryan suggests deleting that file and the 777 will be forced to create a new version.

Share this post


Link to post
Share on other sites

So found something interesting.  After trying the above suggestions with no luck, I looked up some of the airports in the PMDG nav database. 

Unfortunately I can't seem to paste text into this window, but the short of it is that PMDG's info is definitely off. 

For example, at ANC it showed the FMC database having runway 14, while it showed FSX having runway 15.  A quick change to correct the FMC database

to 15, and now it does what it's supposed to in the sim.

 

At ORD, the list of runways includes 9R and 27L, but no 9L/27R.  So if you have a 9R, there must be a 9L, but there isn't, hence the error I guess.

Which is great, but why are there these errors....

 

Similar at SEA, there's 16C and 16L, but no 16R. 

 

I'm sure there are more.   Any suggestions for a quick fix for a correct database?   No one else has encountered this?

Thanks again...

 

 

 

Alex V.

Share this post


Link to post
Share on other sites

I don't know which cycle navdata you are looking at, but it's not the current cycle, which is 1410 and the "pmdg" data (it's not from pmdg) for PANC is:

STEVENS ANCHORAGE INTL  PANC07L10600071 61.169764-150.008333109.9007100128
STEVENS ANCHORAGE INTL  PANC07R12400071 61.167811-150.042872111.3007100132
STEVENS ANCHORAGE INTL  PANC15 10960146 61.199464-150.014381111.7514600151
STEVENS ANCHORAGE INTL  PANC25L12400251 61.167881-149.972650000.0025100100
STEVENS ANCHORAGE INTL  PANC25R10600251 61.169811-149.948300000.0025100092
STEVENS ANCHORAGE INTL  PANC33 10960326 61.171753-149.998872000.0032600121

Note runways 07L/R 15 25L/R and 33 as it should be and the sidstar file also agrees with runway numbering. Specify what you are looking at when you say pmdg database. The above is from navdata\wpNavAPT.txt file.


Dan Downs KCRP

Share this post


Link to post
Share on other sites

So found something interesting. After trying the above suggestions with no luck, I looked up some of the airports in the PMDG nav database.

Unfortunately I can't seem to paste text into this window, but the short of it is that PMDG's info is definitely off.

For example, at ANC it showed the FMC database having runway 14, while it showed FSX having runway 15. A quick change to correct the FMC database

to 15, and now it does what it's supposed to in the sim.

 

At ORD, the list of runways includes 9R and 27L, but no 9L/27R. So if you have a 9R, there must be a 9L, but there isn't, hence the error I guess.

Which is great, but why are there these errors....

 

Similar at SEA, there's 16C and 16L, but no 16R.

 

I'm sure there are more. Any suggestions for a quick fix for a correct database? No one else has encountered this?

Thanks again...

 

 

 

Alex V.

Even though the database identifier in your FMS shows cycle 13-09, based on what you are reporting above, there is no question in my mind that you have at least some files from a much older version of the PMDG database in your PMDG\Navdata folder. I can verify that the 13-09 Navigraph database that was included with the 777 DOES have the correct runway info for SEA and PANC.

 

Something may have gone wrong when you installed the 777, that prevented all nav data files from updating properly. Perhaps a folder permissions issue (a folder or files marked as "read only" in Windows), or by not running the 777 installer as administrator.

 

At the very least, your airport data appears to be from an much earlier AIRAC cycle - perhaps from your installation of the 747 which you mentioned you owned before you purchased the 777.

 

You can delete the file APT_RWY.dat. It will be re-created the next time you load the 777, but it's contents come from the Navigraph airports.dat and wpNavAPT.txt files, and if those files are from the wrong cycle, then the APT_RWY.dat file will be wrong too when it is rebuilt.

 

Please check the following: in a text editor, open the file "wpNavAPT.txt" and scroll to the top of the file. Right below the Navigraph copyright notice, will be the AIRAC cycle that the file is from. Check if it shows "AIRAC Cycle 1309"

 

You should probably do the same for the other 3 text files that begin with "wpNav". They should all be from AIRAC Cycle 1309

 

All of the 4 files that begin with "wpNav" should have the same date and time stamp.

 

There is also a file called "airports.dat", if you open it with a text editor, it should have the same AIRAC cycle and date as the 4 wpNav files, and the same date and time stamp.

 

(The date and time stamps may differ if you have edited and re-saved any of these files)

 

If ANY of the files I have mentioned are NOT from cycle 1309, then your PMDG navdata installation is corrupt. The options to fix it are: re-install the 777 (as administrator) or purchase a 1-time database upgrade from either Navigraph or Aerosoft NavDataPro.

 

Please check the files mentioned above and let us know the AIRAC cycle info contained in them before doing any reinstallation or database updates.


Jim Barrett

Licensed 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.

Share this post


Link to post
Share on other sites

Ah HA, now we're getting somewhere.  I was looking at the ARPT_RWY.dat file.   But as you guys suggested, the wpNavAPT is very old, cycle 0805 from 2008. 

The airports.dat file is from cycle 0805 as well.  Excellent.  The other files all seem to be from the more recent (included with new 777 download from last week)

cycle 1309. 

 

SO:  wpNavAPT, old cycle

        airports.dat, old cycle

        everything else, cycle 1309  (Sep 2013)

 

Let me know what you think, hopefully this is it.  If I do a re-install, what do you think of this: uninstalling 777, deleting whatever NavData folder is in the PMDG

folder (for the older aircraft installs) to keep that from being a problem, then reinstalling.

 

Thanks guys for your help, seems like a silly little problem that's been dragged on but you keep coming back.

 

 

Alex V.  

Share this post


Link to post
Share on other sites

Ah HA, now we're getting somewhere. I was looking at the ARPT_RWY.dat file. But as you guys suggested, the wpNavAPT is very old, cycle 0805 from 2008.

The airports.dat file is from cycle 0805 as well. Excellent. The other files all seem to be from the more recent (included with new 777 download from last week)

cycle 1309.

 

SO: wpNavAPT, old cycle

airports.dat, old cycle

everything else, cycle 1309 (Sep 2013)

 

Let me know what you think, hopefully this is it. If I do a re-install, what do you think of this: uninstalling 777, deleting whatever NavData folder is in the PMDG

folder (for the older aircraft installs) to keep that from being a problem, then reinstalling.

 

Thanks guys for your help, seems like a silly little problem that's been dragged on but you keep coming back.

 

 

Alex V.

Glad you found the old files! Yes, erasing all the files in the NavData folder before re-installing the 777 would probably be a good idea... Then you will be certain that all the files that appear there after the install are indeed the newer 1309 versions. If there is any doubt, you can examine each one in Notepad to check the dates, as you just did.

 

Just be sure to reinstall as administrator. Should solve the problem. After you reinstall, apply any required 777 service packs to be sure the entire aircraft is entirely up to date.


Jim Barrett

Licensed 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.

Share this post


Link to post
Share on other sites

Success!!  Everything seems to be as it should.  Now I can get back to business.

 

 

Thank you again, wish I discovered this FS wisdom on the forums ten years ago...

 

 

 

 


OOps looks like I did the 'solved' thing a little wrong..

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...