Is this a one time only thing or do we need to delete it before every flight from now on?

 

I think it is a rare issue that happens for unknown reasons.  I have never experienced this issue myself. It may have to do w/ switching between the NGX and 777, which as you know share this file (even though it can cause problems w/ one aircraft and not the other, as you found out).  But this is just a guess.

 

So no, I wouldn't delete the file every time unless the problem happens repeatedly, in which case please file a support ticket w/ PMDG, and let us know what they say.

 

Mike

Ah yes, I am sorry I forgot this little gem otherwise I certainly would have mentioned it.  It is a file used by RAAS, which is not included with the B737 product so a mismatch there will not impact it.  There is also a MakeRunways utility that rebuilds the RAAS files, free from here: http://www.schiratti.com/dowson.html

 

I think a problem arises when a location changes runway identifiers. Deleting arpt_rnwy.dat forces a redo by B77X or you can run the make runways utility. Not sure why this is a problem, but I've seen at least one other thread regarding this.

 

Full names here please gentlemen.

I renamed the ARPT_RNW.dat to .bak so the T7 would build a new file (which it did) but I still get this error when I type TTPP (Piarco Int) into the DEST line on the route page.

My coroute TLPLTTPP01.rte from PFPX does not contain any STARS as neither airport actually has any.

 

 

 

 

My coroute TLPLTTPP01.rte from PFPX does not contain any STARS as neither airport actually has any.

 

That error isn't related to the route file. It's the airport file (note the reference to the RNW, or "runway").

That was just additional info as it was mentioned earlier in the thread (or a similar thread).

Found this on Navigraphs forums

 

http://www.navigraph.com/forum/viewtopic.php?f=30&t=1995

You can fix this with any text editor, it helps to have one that counts lines. File is sidstart ttpp.txt (sorry Kyle this error is almost always the sidstar file).  Line 54 reads as follows:

 

APPROACH ILS10 FIX SHARK 4100 FIX SHARK AT OR ABOVE 4100 FIX FI10 1400 FIX TRINB 1400 RNW 10 RNW 10 TRK 104 UNTIL 2200 TRK 104 UNTIL 2200 TURN RIGHT DIRECT FIX POS AT OR ABOVE 4100

 

Delete the second RNW 10 that I have made bold.

Eagle eye, well spotted Dan! I was looking for a duplicate line in the file TTPP.txt in FSX\PMDG\SIDSSTARS.

 

It then creates a new error LN:18 ERR at FIXES error  .

 

16 //AIRAC Cycle : 1501 (08/JAN/2015 - 04/FEB/2015) - Ver.1

17 //------------------------------------------------------

18 FIXES

19 FIX 144AT LATLON N 10 43.3395 W 61 12.34134

20 FIX 160AT LATLON N 10 44.09232 W 61 11.50482

 

line 18 just says FIXES?

(sorry Kyle this error is almost always the sidstar file)

No need to be sorry for being right. I made an assumption based on what I know, which is limited. Thanks for getting them pointed in the right direction!

Navigraph are working on a fix. Either in rev 2 of 1501 or in the next AIRAC cycle. It's also happening at FSIA

 

 

line 18 just says FIXES?

 

Yeah, that happens with the error is a forward reference and the interpreter, which acts like a single pass interpreter, cannot resolve the error. I've had to comment out large blocks of the file to track these down.

So there is no short term fix?

So there is no short term fix?

 

You can always look at another SIDSTAR file and see what the difference is and emulate that change.

So there is no short term fix?

Oh, I didn't realize you'd asked me to debug the file. Line 55 that reads:

 

"APPROACH ILS10 TURN RIGHT DIRECT FIX POS 4100"

 

Delete that line.

The next is not a error that stops the file from working but notice the two CURRY transitions are duplicated. You can safely delete the two duplications too.

 

Happy contrails.

I wasn't asking for you to all the leg work. Just to point me in the right direction B) but thank you both none the less. I will try when I finish my current flight.