I have no problem entering company routes except at KBOS for some reason (Fly Tampa v 3.2). As a check, I used the same flight plan, KBOS - CYHZ, with the 737 NGX and the plan loaded properly. I've checked other flight plans with the 777 and found no problems. The flight plan was created  using Flight Sim Commander and no problems were found with that.  I'm using Airac 1406.

 

A mystery to me why this only happened at KBOS. Otherwise, no problems with the aircraft's FMC.

 

If anyone has an idea about solving this, I'd sure be very appreciative.

 

Jack Fentress

 

 

If anyone has an idea about solving this, I'd sure be very appreciative.

 

Could you be a little more specific?

 

Instead of trying to enter the file name via COROUTE, have you tried ROUTE REQUEST instead?

Enter KBOS at the top left and CYHZ at the top right and then click ROUTE REQUEST.  It should then show a list of all KBOSCYHZ plans.  Select it from the list and try to load it that way.  If it's not showing up in the list, then that's probably why you're getting the error.  It might be hanging out in the wrong folder (the 777 SP adjusts how it looks for FP information and makes it more flexible).

 

Future reference: your scenery is completely irrelevant in situations like this.  It's not like the FMC is running a check for something like that.

Kyle......

Thanks for the quick response.

As a matter of fact, I saw the video on "Route Request" just a few days ago but it never occurred to me to try in this case.

 

I knew that the scenery played no part, but I thought I'd include that id in case someone was curious.

 

I'll give your suggestion a try.

 

Jack

 

 

Thanks for the quick response.
As a matter of fact, I saw the video on "Route Request" just a few days ago but it never occurred to me to try in this case.

 

Welcome - let me know how it goes.

 

For what it's worth, you might also want to have a look at your PMDG > FlightPlans folder to see what's in there.  Report back what you see (folder structure and files in the main folder and subfolders).

Kyle......

In the flight plans folder here's how it looks -

 

FSX\PMDG\FlightPlans\various flight plans

 

KBOSCYHZ is there as follows: KBOSCYHZ.rte.  as a 2kb RTE file.

 

About the route request, I entered KBOS 1L and CYHZ 1R.  Then entered runway. Problem again.  At that point CYHZ dropped out of 1R.  I re-entered it and then pushed Request 3L.

 

Up comes KBOSCYHZ 1L as it's supposed to.  I pushed KBOSCYHZ 1L,  but instead of  Request showing up in the lower right, execute, on the FMC panel was lit.

 

Out of frustration and to see if the same problem would happen at another airport, I moved the aircraft to KBUF and brought up a flight plan for KBUFCYUL. I entered it in the co route area and it loaded perfectly.  Since it did, I saw no reason to use the route option.

 

Bottom line seems to be that the co route entry seems to work OK everywhere but at KBOS - at least on my system. Just as a reminder, I loaded the 737 NGX and loaded the flight plan with no problems. So, just the 777.

 

By the way, I followed the steps on the video just to make sure I was doing it correctly.  At least as far as I was able to.

 

Jack

Then entered runway.

 

Why are you entering the runway?  I only specified KBOS and CYHZ for a reason  :wink:

(Plus, avoid calling a runway from the RTE page unless it's absolutely necessary - use the DEP/ARR page instead to avoid database errors)

 

Try again without - following my directions to the letter this time  :wink: :

Dep Airport

Dest Airport

Route Request - no more, no less

 

Report back.

 

EDIT: Nevermind - I misread what you had mentioned about "re-entering it."

 

What video are you referring to, by the way?

Kyle............

The video is Froggle's youtube.  I found it on a forum post yesterday - SP data link. The specific post reference is 9 down.

 

I'm going to try your last suggestion but not until tomorrow. I'm an hour ahead of you (Atlantic Daylight  Time) and it's getting close to "cocktail time".

 

Tomorrow morning, as soon as I'm back from the gym I'll be on it.

 

Surely there's a solution to this rather than manually installing waypoints.

 

Be back at you tomorrow.

 

Thank a bunch for your help.

 

Jack

 

 

The video is Froggle's youtube.

 

That's why you're running into issues.  It's behaving differently because it's a beta software that you don't have...

 

 

 

Surely there's a solution to this rather than manually installing waypoints.

 

There is.  You're relying on "bad" information.  It'll be good information once you get SP1, but for now, you're trying to follow his example on a software version you don't have yet.  Pay a little more attention to the video title next time 

 

PMDG 777 DATA LINK BETA

 

Your version won't go through the whole REQUEST procedure.  Just hit EXEC (the button lit up for a reason  ).  Done.

Kyle..........

Well, that makes sense.

 

After looking at your video today and reading R. R.'s release yesterday, I guess the best thing is to wait for SP 1 and that will, hopefully, solves this minor problem.

 

I do appreciate the time you've spent on this though.

 

Jack

 

 

and that will, hopefully, solves this minor problem.

 

Not sure where the problem is...

 

Earlier, you wrote (I crossed out the step that was unnecessary):

 

 

About the route request, I entered KBOS 1L and CYHZ 1R.  Then entered runway. Problem again.  At that point CYHZ dropped out of 1R.  I re-entered it and then pushed Request 3L.
 
Up comes KBOSCYHZ 1L as it's supposed to.  I pushed KBOSCYHZ 1L,  but instead of  Request showing up in the lower right, execute, on the FMC panel was lit.

 

You entered KBOS in 1L and CYHR in 1R and then pressed REQUEST at 3L.

 

KBOSCYHZ showed up in 1L as it was supposed to.  You then pressed 1L, and EXEC lit up.

 

You should've then hit EXEC, and the plan would've loaded.

 

This is the correct behavior for the pre-SP1 build.  The post SP1 build just simulates datalink more accurately.  The current behavior isn't wrong/incorrect/problematic.

Kyle............

Enough already.

 

I think we can close this until SP 1 is out.  Then, we'll see! 

 

I suspect you're right, but I have to  see to be sure.

 

Nothing personal, but I have had enough experience since Sub Logic to want to wait until things are settled.

 

Jack

I think this is the negative airport altitude bug - fixed in SP1.

Ryan..........

Thanks for that. By the way, you most likely won't remember the exchange we had last year regarding 2D vs 3D panels.  You said that I'd get used to it. 

 

Right you were.

 

The 777 3D is really "a piece of cake" after a short learning curve for 2D guys like me.

 

Also, Kyle has been a big help regarding this problem. The guy never gives up and that's a good thing (as Martha would say).

 

Jack

 

 

Also, Kyle has been a big help regarding this problem. The guy never gives up and that's a good thing (as Martha would say).

 

haha - glad to help!  If you've ever watched the show House, that's essentially me (except with computers / flight simulators and not people).  I don't like loose ends.  I like solving the "case."  I go through that process, usually, with a heavily sardonic/sarcastic approach.

 

Thanks for sticking with me.  You're right - regardless of if you think it's correct or not, currently, it'll be changing in a bit anyway.

Kyle.............

While we're waiting for SP 1, I'm still kind of curious about a couple of things.

 

1. Using your 1L and 1R, request etc., when I hit execute, actually, nothing showed up. No legs.  Nothing. Why?

 

2. After adding sids and stars to the flight plan and following the same steps as in 1, the sids and stars showed up but no other waypoints.  I manually added them to see if it would work that way and it did. Why?

 

Since you and Ryan have indicated that SP 1 would handle this issue, I'm just curious about the difference in 1 and 2.

 

No hurry on this.  Just whenever you've got the time.

 

Jack