Jump to content

aivlasoft

Administrators
  • Posts

    5,903
  • Joined

  • Last visited

Posts posted by aivlasoft

  1. Richard,

     

    I just ran a couple of tests and as it seems there might happen a situation where behind the splash screen a message box is waiting for the users input (OK Button). Please try the following: Start up the DisplayUnit and when the splash screen is in front and all seems to be stopped just press the enter button on your keyboard. Since the message box already is having the focus it should listen to that keyboard input.

  2. Dave,

     

    I think that I see what you mean. This would need something like an alternative to the currently available save dialog, or at least a dialog that appears before the save dialog.

     

    If you were entering a text like "STN-NCE-XA" in this new dialog, then this would be taken as the file name for all the ticked flight plan handlers, and if you don't enter a text (or even if the dialog doesn't appear according to the users settings), the filenames would we applied as defined in the today's save dialog.

  3. Dave,

     

    I'm not sure whether I understand the idea. Do you think of an additional text that should be added to the flight plan name or should it replace the name? Should it replace all the names if there are several flight plans that will be saved?

     

    Let's assume that you fly from EGKK to LFPG and you have 3 flight plans that will be saved when pressing "Save". According to the save dialog (and the current settings on my computer here) this will create the following file names:

     

    a) EFB plan: Gatwick (EGKK) to Charles-de-Gaulle (LFPG).efbr

    B) FSX plan: IFR Gatwick to Charles-de-Gaulle.pln

    c) PMDG rt2: EGKKLFPG01.rt2

     

    Would you like to have a dialog which appears before the save dialog where you can enter some text and then this text will be added to the file names like this:

     

    a) EFB plan: Gatwick (EGKK) to Charles-de-Gaulle (LFPG) {added text}.efbr

    B) FSX plan: IFR Gatwick to Charles-de-Gaulle {added text}.pln

    c) PMDG rt2: EGKKLFPG01 {added text}.rt2

  4. Eli,

     

    ahhh, now I see it :shock:

     

    So we have the situation that FSX has a ICAO code which doesn't match the r/w code from Navigraph ... A situation we hadn't before. It seems that this must be set on the "to-do-list" for version 2 (renaming of a airport code).

     

    Another idea would be to get some revised AFCAD files?

     

    Renaming the Navigraph files and their content could also be done, but this is a very inelegant, complicated and long-winded solution ... and all is lost with the next cycle.

  5. Alex,

     

    I just had a look into the source code to see when the runway-buttons are greyed-out. They are greyed-out whenever there is no match between the runway identifier from the BGL data and the runway identifier from the Navigraph data.

     

    Some questions:

    - before the re-install, have you had a "runways.txt" file in use?

    - are you using third-party airports for all these locations?

  6. Hiram,

     

    from what you describe it could be that some parts of the installation are missing.

     

    Did you first run the FULL installation package which you can download here:

    http://www.aivlasoft.com/download/Aivla ... p_v131.zip

     

    After this installation, please apply the latest service pack

    http://www.aivlasoft.com/download/Aivla ... P3.exe.zip

     

    If you are still not able to run the application could you please take a screenshot from which I can see the error message?

  7. Karl,

     

    if the flight information system loses track of your aircraft and it takes the latest passed waypoint as the next, the distance on the panel for the destination increases although it should be decreased. In such a situation simply open the "blue button" on the main menu bar (e.g. KSEA Departure), select "Direct-To" and select the next waypoint manually. This way you can "tell" the system which is your next waypoint.

  8. Phil,

     

    there is another easy way:

     

    1) navigate to the installation folder of EFB (e.g. C:\Program Files\AivlaSoft\EFB)

    2) below this folder you will find a folder called "plugins"

    3) remove the file "AivlaSoft.FlightPlanHandlers.iFly.dll" (or if you intend to use it at a later time then save it to another directory)

    4) restart DisplayUnit

     

    Hope this helps.

  9. Hi Glen,

     

    from my point of view it's a Navigraph related issue. If you have a look into the file "EGKK.txt" (in folder "[FSX]\AivlaSoft\SIDSTARS") you will notice that four SIDs (HARD5M, HARD5V, KENE2M and KENE2V) are described like " ... TRK 259 UNTIL 10.5 FROM FIX MID ...". In my opinion it should be " ... TO FIX ..." instead of "... FROM ...".

    If you change these 4 items, then reset the airport data cache (System -> Settings -> Miscellaneous -> Reset airport data cache) and reload the airport.

×
×
  • Create New...