Johannvr

What a way to discover a little error. Who would ever have noticed this? Thank you Roy for sharing this and Dan, for the "dead leg dead engine" lesson. I don't think many of us "armchair pilots" know about this method.

Vernon Did a test flight with the NGX at payware LPPT airport (Aerosoft), ILS rwy03 and the MCP shows 026, same as FMC. I have AIRAC 1501 with magvar.bgl of 2010 from http://www.aero.sors.fr/navaids.html Then, same here, what else can I say? It makes no sense why your MCP shows 025.

Very nice scenery indeed, considering it's free. And do not forget the freeware FSX scenery from Max Kraus, Mauritius FIMP, Gantly Adams TBPB, Gold Coat YBCG and Paphos LCPH. All available at Avsim's library.

Ron, that is not my username and has never been. I still have had no response to e-mails send to [email protected] to be able to login at the support forum and get help with issues I have.

I am having a similar issue there. Unable to login at their forum. An error message says my username is inactive and I should contact a board administrator. Send 2 e-mails to support and also no reply yet.

Ron, scenery for FAOR and FALE here: https://shop.nmgtrading.com/. Not in the same class as Fly Tampa, FSDreamteam, Aerosoft but it's the best available I know of. At least the afcads are correct.

Ron, we all "suffer" these airport name changes. As Kyle has said, you have to update your sim by installing new scenery for FALE, King Shaka Intl. that will be added to FSX. FADN can not be deleted in FSX. We just "abandon" it. There will be no reference to it in the new AIRAIC procedure files. The same applies to Johannesburg Intl, FAJS that became OR Tambo Intl, FAOR. You have to install new scenery that will add a new FAOR airport where FAJS is. Again FAJS can not be deleted in FSX. You will still see the reference to it in FSX. After you have installed the scenery in FSX, run FSCommander's FSCDbManager to update it's airport database. You will then see all airports as it's in your sim and the applicable procures as per AIRAC will match.

You can add "patchsim1friction=Yes" (without inverted commas) in your fsuipc.ini file, under the "General" section. It's working for me.

I thought I was the only one a bit disappointed in GSX's pushback. For me the pushback itself and the time it takes is fine and seems realistic enough. It's the time after the "set parking brake", you have sit and wait for the wing walker's "dance", who then climbs onto the towtruck which then sometimes cannot make up it's mind where to go and get out of the way, that's frustrating. Until now I have taxied over many of GSX's towtrucks taking to long to get out of the way, screaming "set parking brakes immediately!" behind me. :P FS2Crew's announcement is thus good news to me.

Yes, I too enjoy the many public holidays we have here, it's just those working days between them that's troublesome.

Keep in mind we don't know what week Robert was pointing to when he said "this week". It could be any week. We just, as usual, have to be patient. Well, I have a 777 on the apron waiting, have to go.

I think this hug is long overdue, now may I ask when will it be released?

Yes, agree. You all should be glad Kyle didn't see this. He will give it to you all for not reading the manual first! :rolleyes:

Thank you, Ryan, this is good news!

This is a bit off topic, but I had a similar expierience with the PMDG 777 wandering off course in LNAV and thought it was just a little random bug that might be fixed in SP1. Now I understand how well PMDG similated the real one. I can now live with this "bug", knowing it's in the real 777 too. :rolleyes:

I am not sure if it is your problem, but could it not be the elevation issue with the 777 FMC? There is still this flightplan import issue on all departing airports with an elevation of less than 1ft. (VHHX elevation is 0ft on my scenery.) I just change the flightplan .rte file in ...\pmdg\Flightplans\ folder, using notepad and for me problem solved. See: http://forum.avsim.net/topic/420277-aivlasoft-efb-imported-flightplan-from-eham-trouble/

I think, if you take in account this aircraft has been out of production for many years, the PMDG staff could be having a hard time finding all the necessary parts to make one. They are probably traveling the world in searching for spares to finish it. :rolleyes:

Can someone please explain why we import wind data to the FMC? Is it really effecting the performance prediction accuracy, seeing it only display 4 flight levels (usely FL300 FL340 FL390 FL440, depending on entered cruise altitude) What If we fly FL360 or FL370 for example? I have experienced the predicted wind data entered completely differs from wind data display on a flight (Online flying, IVAO). Sometimes its seems accurate but other times not. On a recent flight RJAA to KSFO (Initial FL330, step to final FL370) the flight time predicted was 8H46 and the flight eventually was 10H18 due to winds aloft completely different to predicted ones. (tailwinds predicted turned out to be headwinds, fortunately I had ETOPS fuel loaded :rolleyes: )

Kevin, SimBrief does have the weather export function. In the Despatch Output page under Tools and Links, Download Flightplan, select "PMDG WX", then select Download Flightplan and then copy the downloaded .wx file to your ....\PMDG\WX folder and you are good to go. You then just have to select REQUEST in CDU RTE page. Works like a charm.

I feel the same. FCOM1 and FCOM2 are 1000+ pages with info that might be interesting but is not applicable to the 777 as modeled by PMDG. I have lost interest in reading it, sifting through all the revision history, bulletins and about equipment that are obviously not simulated in MS FSX and just figure out things as I carry on flying. Reading all the posts with issues and question in this forum I think I am not the only one that has lost interest (and lazy) in studying the manuals. A structured manual with info applicable only to the FSX modeled equipment would be most appreciated.

We should be just clear on this. The FMC is not a fuel planner in the real sense. It will only give you an (accurate) fuel figure in the PROG page to indicate you have loaded enough fuel for the planned route. You have to start with an estimated fuel figure, enter the route, departure rwy, SID, FL, etc only to find in the PROG page you either have over - or under loaded fuel, do the maths, re-load fuel and then to discover the CG, trim, V-Speeds and sometimes even the initial optimum FL has changed due to different weight figures. For me, not good fuel planning. For those who do not have PFPX or any other purchased software or do not want to go online and use Simbrief, a good excel spread sheet for fuel planning, as we have for the NGX, will be most welcome. Then at least we can start off with a more accurate fuel plan/estimation, check with the FMC to confirm we have more or less adequate fuel on board and if necessary do small adjustments.

Yves, I already submitted a ticket at PMDG concerning this issue. The team apparently will investigate. We can only wait on their feedback. I see Steve's Ideal Flight has no problem importing routes to the CoRoute, so now it could be a FSC9 problem?

Departure (on 125.05) at KIAD flying to Leesburg?

Peter, yes, I am aware this. The OP problem is his route EHAMLEBL cannot be imported, as I found all routes from either EHAM or EHRD. Even a simple direct route EHAM to LOWW, with no wayponts, SID and/or STAR's can be imported to the Co Routes. All other routes imports fine, only ones starting at either EHAM or EHRD gives Invalid Entry error. What is strange is these routes from EHAM works fine in the NGX and the 747-400. Just finished a flight EHAM to ENGM with the NGX with the same route generated in FSC and imported to the Co Route. No issues, only I cannot import the same route to the 777. I have to enter it in manually.

I did a few test with this Issue. I created a few DCT routes in FSC9 (AIRAC 1309 in both FSC and PMDG) from EHAM to LOWW, EHRD to LOWW, EHGG, EHBK, EGLL all to LOWW. All routes imported fine in the 777. Only the ones from EHAM and EHRD could not be imported. All "Direct To" routes, no waypoints. Very strange.