Jump to content

jimihendrix272

Members
 View Profile  See their activity

  • Posts

    24

  • Joined

  • Last visited

 Content Type 

Posts posted by jimihendrix272

    Write procedures grayed out for PMDG RTE

    in EFB v1 (Read only, no longer supported)

    Posted

    Thanks Travis. I just thought it was some kind of error, as it worked ok before.

    I don't see that entering the procedures at "flight time" with Aivlasoft EFB or entering it on the FMC would effect PMDG. It kind of makes having to enter the route twice rather a waste of time, and the route has to match exactly as well (?). Puts you off using EFB.

    You can save the route from the FMC and then use it again on another day anyway...

     

    John

    How to save active route which include SID/STAR to FSX Fln?

    in EFB v1 (Read only, no longer supported)

    Posted

    Ok, thanks. If I go to a virgin FMC and just enter a Co Route file it will put in (for instance) EGSS and EGGW, but not the route.

    Previously, before I reinstalled the file links in Aivlasoft EFB after a change, it used to save the airports and all of the route (write procedure box not greyed out) but I think the SID and STAR you had to do again. I will try to save it from the FMC and see if that works (and where it is saved).

    John

    How to save active route which include SID/STAR to FSX Fln?

    in EFB v1 (Read only, no longer supported)

    Posted

    When I try to save a PMDG Boeing 737-800 routing, the "write procedures" box is ticked for Aivlasoft EFB and Microsoft Flight Sim, but not for PMDG RTE because it is greyed out. Which means when I try and load the file into Co Route in the FMC it just loads the Dep and Dest but not the routing.

    It did work in the past but I must have changed something, and I don't know what to do now. The RTE files are being saved in the same place as when it worked before.

    Hope someone can help :)

    Thanks, John

    Stansted runway 22 displaying 23

    in EFB v1 (Read only, no longer supported)

    Posted

    I didn't buy UK2000 Stansted until after I couldn't get it to work the without it. But UK2000 didn't work either..

     

    Just now I discovered that Stansted Extreme didn't install properly so reinstalled it is and after "updating the data" it displays runway 22/04 in EFB!!  Hurrah :).

    I would love to know why updating "runways.txt" didn't work before; maybe one day some clever geezer will tell me.

    Anyway many thanks for your help, Brian.

    Stansted runway 22 displaying 23

    in EFB v1 (Read only, no longer supported)

    Posted

    Thanks Brian. I will check out what you suggest.

    What I don't understand is why they say to correct the problem here:

     

    The "Runways.txt" file

    Depending on your installation the 'Runways.txt'- file can be found within the following folder:

    VISTA/W7C:\Users\[user Name]\Documents\AivlaSoft\EFB\UserData WinXP C:\Documents and Settings\[user Name]\My Documents\

    AivlaSoft\EFB\UserData
    This file contains information about the correct assigning of FS-runway identifiers and navigation

    runway identifiers. 

     

     

    Nothing about "the only way you're going to get this to work is to buy UK2000 stuff."

    Stansted runway 22 displaying 23

    in EFB v1 (Read only, no longer supported)

    Posted

    The uk2000 was setup a couple of weeks ago. It's "UK2000 Stansted Xtreme, version 4.00"

    I have done the data update that you suggested.

     

    Could you do the thing that Travis suggested (above) to compare your scenery files that you have?

    "Open EFB, load EGSS, click the Airport Information icon, and once that dialog opens, double click in the blank area above the General Info / Communications tabs until you see a filepath and filename."

     

    Although I can't get that same thing to work today :(   When I press the "Airport Information icon" I get a map of Stanted's runway.

     

    Mine is attached.

     

    Thanks, John

     

     

     

     

     

     

    Stansted runway 22 displaying 23

    in EFB v1 (Read only, no longer supported)

    Posted

    Hi Brian

    Your up-to-date maps look soo much better; there might be 15 years from the old to the new though. This problem was happening before I bought uk2000 Stansted; it was just that one the guys that answered this topic (above) said that there his worked fine using uk2000.

     

    Wish I could get mine working. I need someone who understands how the system works to sort it out for me. It is just too much for me to know what to do next...

     

    Not sure if there is something like 'customer service' with the software to whom you can contact directly.

     

    Thanks

    John

    Stansted runway 22 displaying 23

    in EFB v1 (Read only, no longer supported)

    Posted

    Thank you Urs, it's great that you get to see all the questions asked on here!

     

    I have done all the steps that is suggested in the FAQ section. After doing as suggested I'm not getting the error message from the data thingy, but still getting "Favors runway(s) 23 / 05" instead of the correct runways and boxes greyed out (in the "Modify" section).

     

    On the METAR page I didn't see the  "Weather Provider" tab and to change it to "NOAA", so now that is working beautifully thanks.

     

    John

    Stansted runway 22 displaying 23

    in EFB v1 (Read only, no longer supported)

    Posted

    Check in the manual on reassigning runways using the 'runways.txt' file. It talks about this very situation.

    Thanks both.

    As suggested, I put "EGSS 04 22" in that file but no change to the problem. When I press "Departures" in EFB the runway box is still greyed out and it displays "Favors runway(s) 23 / 05". I'm using OrbxFTXGlobalBASE130 scenery, if that has anything to do with it...

     

    Also, just about to look here for this: When I press the METAR button in "Modules" I get METAR is not available (for EGSS and EGAA) even though on the weather setting page http://www.aviationweather.gov/adds/metars/ is set and it the meter for those airfields is available directly.

    But I doubt if this has anything to do with the other problem.

    Stansted runway 22 displaying 23

    in EFB v1 (Read only, no longer supported)

    Posted

    The up to date navdata gives the runway at Stansted as 22 but the EFB displays the runway as 23. Which might be the reason the  departure runway box is greyed out and displays "runway assignment warning for EGSS - STANSTED. Please see the DataProvider's window". That window gives the warning "Navigation data runway ident 22 at EGSS could not be assigned to simulator runway." 

     

    As far as I can see, the nava data seems to be up to date everywhere. Going round in circles...

     

    Thanks

×
×
  • Create New...