Jump to content
The simFlight Network Forums

ofentress

Members
  • Content Count

    62
  • Joined

  • Last visited

Posts posted by ofentress


  1. Volker...........

    After all of the trouble in installing the latest Navigraph for A 318/319, it appears that that Navigraph does not follow the "all addons or all products" that they use for QW and PMDG.  They (Navigraph) have it listed as a separate aircraft and so far I"m getting "not in the database". I don't know for sure, but it appears that Aerosoft did not make flight plans 100% compatible between the A 320 and the

    A 318/319, but for sure it's not all automatic, at least so far.

     

    Jack


  2. Terrence,

    As far as I can tell, all of my options are set correctly.  I've double checked everything.

     

    The fact that the surrounding airport's runways display properly would indicate that, I think.

    When I bring up the map, that runway graphic doesn't appear.

     

    I could be overlooking something, but I can't think what that might be.

     

    By the way, how were you able to make that pic?  I use FRAPS, but it doesn't allow pics that aren't in the Flight Simulator.

     

    Jack

     


  3. This is the first time I've run across this in a long time.

     

    I created a flight plan from KBOS to CYHZ. Added Sid & stars, plan looked fine. Saved and printed. Checked the printed waypoints with the actual plan - everything OK.

     

    Fired up FSX, loaded PMDG 777 at gate B 34.  Opened the FMC, did the usual pre-business and attemtped to enter the plan as a company plan.  Message on FSM says - Invalid Flight plan.

     

    Shut down everything, checked FSC and double checked flight plan.  No apparent problems.  Tried again - same problem. Then, I added KBOS and CYHZ indiviually and when I checked the plan, every waypoint between the end of the Sid and the beginning of the Star was missing.

     

    This is one I can't figure  out.

     

    Jack Fentress


  4. Volker..............

    The FSC Sid selection graphic shows data for Runway 14 L&R and 36 L&R, but nothing for 32L&R. These are the ILS runways.

     

    Just to make things a bit more confusing, the official Madrid charts list Runway 15 L&R and 33 L&R.

     

    In trying to make a flight plan starting at Madrid, there seems to be no way to have a Sid for 32 L&R (or 33 L&R). Is it possible to adjust this or is this a possible Navigraph problem?

     

    Jack Fentress


  5. Volker...........

    Will the situation be the same for this airport as is for Calgary?  Meaning that since this airport doesn't actiually open until sometime next year and the new runway at Calgary hasn't come on line yet that there will be no data available for flight plans to use runway 7R/25L?  I'm assuming that Navigraph won't have the data either, making it not possible for FSC to use the new aiport runway. I know we can still use the exisiting runway (7L/25R).

     

    I just wanted to be sure.

     

    Jack Fentress


  6. Michael...........

    FYI, I thought about the Airac also and checked Navigraph.  There is a newer version of 1401  (Revision 3) which I installed yesterday.  It didn't help the problem however.  At least at CYVR.

     

    I noticed just a bit ago that Airac 1402 has been released this morning.  Possibly that will fix things.

     

    Jack


  7. Otto..........

    Nope.  Didn't work.  Tried distances 50 miles up to 150 miles.  Nothing showed.

     

    Looking at your pic, I noticed that the airport Vancouver wasn't selected at the Flight Plan list.  Also my SID list shows the following:

    4 for 8L, 5 for 8R, 1 for 12, 4 for 26L, 2 for 26R, 1 for 30 = 17 Sids

     

    Your pic show many more than my list shows.  How is that possible?

     

    I'm using Navigraph Airac 1401, which is the most current and FSC 9.5.

     

    Jack

×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.