Jump to content

JerryJet

Members
  • Posts

    38
  • Joined

  • Last visited

Posts posted by JerryJet

  1. Ok I finally got the Surface Pro 2 and installed EFB on it last night. It requested .Net 3.5 that I installed / activated in the device although 4.5 was already there. So I presume it requires 3.5

     

    I did not connect it to FSX or did any test yet but I will report my results when I do...

     

    However, I noticed a bug in the UI, the bottom buttons are cut by the application window border and a small portion of their top is showing... Is it something related to Windows 8?

     

    Thanks

     

    Here's from the Microsoft website, referring to .NET 4.5:

    "This version of the .NET Framework runs side-by-side with the .NET Framework 3.5 and earlier versions, but performs an in-place update for the .NET Framework 4."

     

    As for the button problem. Right click the desktop > Personalize > Display. Is the font size set to default? If not, try it.

  2. RW 19L, RW19C and RW19R

    is there any fix for RW19C and R19R

     

    no RW19C

     

    Not sure what you mean by "flightbeam" in the message subject, but it sounds like you don't have an updated AFCAD showing the new runways. Look for the file "kiad_washington_dulles_intl_v2_0.zip" by Allen Laughmiller on flightsim or avsim in their file library.

    Here's some info about the file:

     

    Airport: KIAD – Washington Dulles International Airport

    Location: Dulles / Chantilly, Virginia USA

    Airport Type: public

    Version: 2.0 (2011-12-29)

    Release Features: Excepting the main terminal buildings, this is a complete rebuild including the new runway1L/19R (with completed taxiways W2,W3, and W4), new signage, to-scale ramps and taxiways, enhanced executive aviation parking, cargo parking, and service roads.

    Creator: Allen Laughmiller (c2fspro@gmail.com)

    Hardware Requirements: fast multi-CPU system, high-end graphics card.

    Disclaimer: Freeware, not to be sold or used for commercial or real-world flight planning purposes. No warranty express or implied.

     

    Jerry

  3. Well you could do IFR flights and let ATC lead you thru the flight. I also visit FlightAware.com/live and "borrow" flightplans from real world flights taking off right now. I mostly do regional jets with a 500 mile limit so a lot of the airports I takeoff from don't have SIDs or STARs so I vector myself onto an airway.

     

    I also use REX and very rarely do I have problems with the weather disagreeing between FSX and EFB. Tiny differences in speed and direction sometimes. I have REX set to wait one minute after loading FSX, then inject weather every 15 minutes.

     

    I look forward to those times when the wind shifts right after I've setup my runway and approach. You learn how to program the FMC really fast, and EFB handles the change quite well too.

  4. This seems to be the same problem I posted about for KSTL. Runways 7L and 25R are listed twice in "wpnavapt.txt"

     

    FRANKFURT/MAIN EDDF07C13123068 50.032617 8.534631110.5506800329

    FRANKFURT/MAIN EDDF07L09186068 50.037056 8.497078110.3006800305 <--

    FRANKFURT/MAIN EDDF07L09186068 50.037056 8.497078111.7506800305 <--

    FRANKFURT/MAIN EDDF07R13123068 50.027542 8.534175110.9506800328

    FRANKFURT/MAIN EDDF18 13123178 50.034169 8.525931000.0017800326

    FRANKFURT/MAIN EDDF25C13123248 50.045128 8.586981111.5524800364

    FRANKFURT/MAIN EDDF25L13123248 50.040053 8.586531111.1524800362

    FRANKFURT/MAIN EDDF25R09186248 50.045825 8.533717111.3524800353 <--

    FRANKFURT/MAIN EDDF25R09186248 50.045825 8.533717109.7524800353 <--

     

    Jerry

  5. Here is the pertinent excerpt from "wpnavapt.txt" for KSTL showing runway 12L listed twice:

     

    LAMBERT-ST LOUIS INTL KSTL06 07607063 38.746678 -90.381231110.3006300551

    LAMBERT-ST LOUIS INTL KSTL11 09001122 38.759953 -90.409875111.9512200618

    LAMBERT-ST LOUIS INTL KSTL12L09003122 38.751781 -90.366295108.9012200528

    LAMBERT-ST LOUIS INTL KSTL12R11019122 38.753220 -90.377772109.7012200540

    LAMBERT-ST LOUIS INTL KSTL24 07607243 38.756217 -90.357506110.3024300534

    LAMBERT-ST LOUIS INTL KSTL29 09001302 38.746795 -90.383164111.9530200556

    LAMBERT-ST LOUIS INTL KSTL30L11019302 38.738078 -90.347061111.5030200583

    ;LAMBERT-ST LOUIS INTL KSTL30L11019302 38.738078 -90.347061111.7530500583

    LAMBERT-ST LOUIS INTL KSTL30R09003302 38.738608 -90.339586111.3030200605

     

    I commented out the second instance of 12L and reran the Data Provider Scenery Updater so I would not get errors about the FSX unassigned runway.

     

    Can't say when's the last time I flew into St. Louis, but I noticed this using the current AIRAC 1302 ver.1 from Navigraph.

     

    Jerry

  6. Lee

     

    EFB has some flightplan handlers written for it so that when you create a flightplan in EFB and then save it, it will also be saved in the flightplan handlers for your respective aircraft if you have set them up. For instance I have the PMDG Md11 and the level D 767 flightplan handlers setup. So the process I use is

     

    1 Start FSX, rex etc

    2 place aircraft at stand of choice

    3 Start EFB and select saved plan, ( i have loads saved)

    4 activate said plan

    5 check metars at depart airport just in case i need to change dep rwy and SIDS

    6 Log on to VATSIM

    7 Fly

     

    Simple really and of course the more you use EFB the simpler the operation becomes, all of my ifr flights are conducted with EFB. I tend to use Plan G for VFR.

     

    First off, I have EFB installed correctly and all the different windows seem to be talking and hearing one another. One computer; FSX on monitor 1; EFB on monitor 2.

     

    If I load a flightplan in EFB for the Citation Mustang (GPS plan) it will successfully import into the Garmin GPS on the Mustang. Yeah! When I follow this same procedure with the PMDG 737NGX I still have to load the flightplan into the FMC via the company route line. I understand EFB will write (save) a PMDG routeplan but not read (open) one so I'm confused by steps 3 and 4 above. You mention an MD11 in your post (also PMDG) which uses the same *.rte as the NGX so how are you doing this???

     

    Jerry

×
×
  • Create New...