This is interesting Mike.  My Airport_Rwy file was showing as dated 12/17/14 as well.  However, I did update to V3 of 1413 after this date I believe. It looks like maybe when I updated to v3 of the 1413 AIRAC, something must have gone amiss.  Its REALLY strange for me that the incident was only focused on the 777 though.  My NGX didn't show ANY signs of the same problem. The only thing I can think that might have happened is if I inadvertantly updated the AIRAC while my PMDG 777 was loaded in FSX.  Maybe this caused something with-in the 777 to not regenerate a file to match the new NAV files since the 777 was loaded in the game during the update. I am ALWAYS cautious to make sure I have FSX closed when I update anything, but maybe I had a flight at a gate on pause in the back ground and didn't pay attention.  Anyways, issue is fixed! Thank you all again!!

 

-Dan Burke-

This is interesting Mike.

 

OK, FWIW, I installed my old, pre 10R version of AIRPRT_RWY.DAT, then loaded the T7 at KFLL, entered KFLL as the departure airport, and entered Rwy 10R under DEP window.  No problem!  BUT: the ARPRT_RWY.dat file updated, and now includes 10R in its list of runways.

 

So there must be some fairly unusual situation in which this file fails to update.

 

Not sure, but I have the impression that the NGX doesn't use this cache file even though it is in the top level PMDG folder.

 

Mike

 

PS: Just got an RAAS message "On Runway 27R" (instead of 28R where I loaded the aircraft), because I didn't run makerunways after I installed Ray Smith's KFLL.

 

 

Thank you Kyle for your reply, but I didn't really apprecaite your tone.  I am the one with the issue here and I will be the judge of whether or not I am wasting my time.  Every option is still an option until the option is exhausted through some sort of trial and error.  While I appreciate your knowledge, it certainly wasn't in vain for me to pull the add-on. It takes 2 seconds to pull 2 Bgl files out of the add-on folder.  To reply to your post from earlier...I did have a route in my 777 route from KFLL, but the runway was not specificed in the plan.  It was actually though this route I discovered the issue several days ago.

 

I apologize for the tone. I appreciate that you're the one here with an issue. I want to see your issues resolved probably just as much as you do. It's just quickest when we're all on the same track and same page. If I don't see my points addressed in a response - or, even more so if I see a response opposite to the guidance - I have to assume the message wasn't received and I have to repeat it in an effort to get everyone on the same path/page. I think everyone can agree that would be a bit frustrating. As you can see, the MakeRunways and scenery suggestions simply distracted us from getting to the end issue of routes and the ARPT_RWY file, which is where I was headed (thus the route mention).

It looks like maybe when I updated to v3 of the 1413 AIRAC, something must have gone amiss.

 

Just wondering if your previous update was before 10R became a runway at KFLL?  I have a backup copy of Airac 1407 from June/July 2014 and 10R/28L are not in it.  Just one runway, 10L/28R.

 

Mike

Mike,

 

10R re-opened (for commercial jet traffic) on September 18th, 2014.  Ray Smith's KFLL wasn't released until 10/3/14.  My previous update and flight from KFLL was on cycle 1412 with a 777 from KFLL to ENGM.  Everything worked like a dream.  Something happened in the updated to 1413 and in the revisions to the file specifically for 1413 v3 that navigraph released.  Again, I believe I might have updated the revision of 1413 v2 to 1413 v3 while FSX was opened, and possibly had a 777 loaded.  This may have caused the issue.

 

-Dan Burke-

 

10R re-opened (for commercial jet traffic) on September 18th, 2014.  Ray Smith's KFLL wasn't released until 10/3/14. My previous update and flight from KFLL was on cycle 1412 with a 777 from KFLL to ENGM.

 

10R/28L is showing up in my Airac 1411, but maybe it was closed for 1412 and reopened by 1413.  At any rate the problem is resolved and we should both probably move on to other things!

 

Mike

So maybe if your file was generated before the new runways were established at KFLL (and showed up in the first Airac after that) you might get this error? Kyle, do you have any idea what triggers a rebuild of the Airprt_RWY.dat file?

 

 

I had a similar problem in the NGX at a different airport a few months ago, that was cured by a rebuilt of apt_rwy.dat

 

I believe that you can trigger a rebuild of the file by simply deleting it, then loading any PMDG aircraft in FSX, which will re-generate the file as the aircraft is loading. It should also rebuild during the first aircraft load when the other files in the folder (the actual monthly airac data) change due to a Navigraph or NavDataPro update.

 

Perhaps the DAT file became corrupted by a previous FMS or aircraft loading error - not enough to prevent it from working completely, but enough to cause problems with certain PMDG aircraft at certain airports.

I apologize for the tone. I appreciate that you're the one here with an issue. I want to see your issues resolved probably just as much as you do. It's just quickest when we're all on the same track and same page. If I don't see my points addressed in a response - or, even more so if I see a response opposite to the guidance - I have to assume the message wasn't received and I have to repeat it in an effort to get everyone on the same path/page. I think everyone can agree that would be a bit frustrating. As you can see, the MakeRunways and scenery suggestions simply distracted us from getting to the end issue of routes and the ARPT_RWY file, which is where I was headed (thus the route mention).

Kyle....good that you apologized, but don't worry about it.....I totally understand what you mean.

 

When one feels his/her post are ignored (rightly so or not) he/she can do three things:

1) post the same again and try to get the point across.

2) disregard the whole thread and forget about it.

3) vent.

 

Usually #1 wins.....sometimes#2......and then there are days that #3 gets the better of us.

 

Been there....done that....

I previously posted this in a separate thread for the PMDG 747 but since its the same issue for the 777 I'll repost it here to ensure people are able to see the solution that worked for me for my PMDG 777. I have both PMDG 747 and 777 but have yet to test and see if I have this problem on my 747. I did encounter it on my 777 a couple days ago. I tried the suggested fix of deleting the "arpt_rwy.dat" file from the PMDG/Navdata file. It does regenerate itself as explained but it did not fix my problem. I don't have a subscription to Navigraph at the moment so I couldn't test using a newer navdata cycle. I just reinstalled my software from the download link and clicked the Repair option. This action of reloading the software even though the navdata cycle associated with the software hasn't changed, fixed the issue. My next step I would've taken if it didn't work would be to fully uninstall the software from my computer and conduct a fresh install but it never got to that point. For those of you out there that are still having this issue after attempting deleting the "arpt_rwy.dat" file, try a repair install and see if that helps. Worked for me.