Jump to content

aivlasoft

Administrators
  • Posts

    5,930
  • Joined

  • Last visited

Posts posted by aivlasoft

  1. Salut Jean-Louis,

     

    the position of the horizontal splitbar that you mention should be saved when the program terminates.

     

    Try the following:

    Open each chart type (Arrival, Approach, Ground, Departure, Enroute), re-position the splitbar to the desired position and then close the application by using "System" -> "Switch off". After restart of the DisplayUnit the splitbar should appear at the last saved position.

  2. Hi Andy,

     

    I just had a look into cycle 1010 using version 1.1.0 and everything seems to be OK. All approaches for EGCC are available.

     

    when rebuilding the database
    Did you install a new scenery or is there another reason for the rebuild? Could you please send me the logfiles to support@aivlasoft.com. The logfiles can be found as follows: Windows-Start -> All programs -> AivlaSoft -> EFB -> Logfiles. Please send all the files you can found within this folder. Thanks.
  3. Salut Jean-Louis,

     

    I think that the problem is due to a simultaneously try to write the "same" file (flight log) into the same folder. I assume that both settings for the flight log's folder are pointing to the same physical location? Try to change the flight log's path from one DisplayUnit to another folder.

  4. Hi Michael,

    yes, you're right. When you press the "Activate" button, EFB creates an FSX flight plan in the folder which must be defined in the DataProvider settings (Miscellaneous - Folders). You also have to tick the checkbox above the directory name.

     

    BTW: FSC writes the plans in FS9 format. FS9 flight plan format is a pure text file, whereas FSX plans are formatted as XML files. Since FSX is capable of reading both formats normally no one cares about what format it is. EFB 1.1.0 can only read FSX XML files. The upcoming version 1.2.0 will be capable of reading both formats.

  5. Jean-Louis,

     

    the path you mentioned is only used either from within the library module when accessing the flight logs, or at the moment when the flight log is being written to the hard disk. The latter one happens at the moment when the engines are shut down. Can you give me some further information about the moment when the problem happens? If the dialog "Unhandled exception ..." is presented, could you please send me the content of the text which is attached to the box?

  6. Hi all,

     

    thanks for contributing all these information. From my point of view there are only some small additions:

     

    - the IVAO Cozumel chart shows a magnetic variation of 1° E and is from March 2008, whereas FSX (I guess) is from around 2005 with a magnetic variation of 0.9 W. This is a difference of about 2 degrees.

     

    - the chart shows a final course of 099° whereas the Navigraph procedure is not giving you a course but two fixes. So EFB has to calculate the course considering the magnetic variation. As a result of this EFB shows a final course of 102°.

     

    - Real charts are representing the data from a certain time, EFB is representing the data from the time where the data for FSX has been collected.

     

    ... just my two cents

  7. Hi "eli",

     

    it's hard to give you the "right" answer to issue #1 because I don't know your equipment. At least there seems to be a possibility to connect to the activation server, although it's only after several attempts. It's the first time that I "hear" such an issue. Do you run other applications on your computer which might to control or have an impact on the internet traffic?

     

    According to issue #2 I just have created a post in the FAQ section concerning the topic "Which folders must be shared". Please see http://www.aivlasoft.com/support/viewtopic.php?f=3&t=217

     

    Best regards,

    Urs

     

    BTW: According to the forum rules, please sign your posts with your real life first name (maybe by adding a signature). Thanks.

  8. The following steps are meant to be applied on a Windows 7 or Windows

    Vista computer if you want to run EFB on a two computer setup.

     

    A) Overview

    ===========

    On a two-computer-setup you must first share two folders which are

    located on your FSX machine.

     

    Folder #1)

    C:\Users\[username]\AppData\Local\AivlaSoft\EFB\AivlaSoft.Efb.DataProvider

     

    Folder #2) C:\Users\[username]\Documents\Flight Simulator X Files

     

    (Please replace [username] by your username on your computer)

     

     

    After these two folders have been shared they must be selected from the

    DisplayUnit's settings dialog (Folders and Links tab):

    Folder #1 -> Provider data folder

    Folder #2 -> FSX Flightplans

     

     

    B) If Folder #1 is not available/visible

    ========================================

    If folder #1 is not available (= not visible) in the Windows Explorer,

    then you must proceed as follows. If it is already visible then you may

    go forward to C).

     

    1) Start "Windows Explorer", not Internet Explorer.

    2) On the top left corner you see a menu item called "Organize"

    3) Open the menu item, then select "Layout" and check whether the item

    "Menu bar" is selected. If the "Menu bar" is not yet selected, please do.

    4) At the "Menu bar" select "Tools -> Folder options ..."

    5) Select the second tab, called "View"

    6) Search for the option "Hidden files and folders"

    7) Select "Show hidden files, folders and drives"

    8) Press "OK" and close the Windows Explorer

    9) Start Windows Explorer and you should find the folder:

     

    C:\Users\[username]\AppData\Local\AivlaSoft\EFB\AivlaSoft.Efb.DataProvider

     

    10) Now share this folder for "Everyone, Read & Write"

     

     

    C) How to share the folders

    ===========================

    1) Please navigate to

    C:\Users\[username]\AppData\Local\AivlaSoft\EFB\AivlaSoft.Efb.DataProvider

    using the Windows-Explorer

    2) in the left pane of the explorer right-click on this folder to see

    the context sensitive menu.

    3) Now choose "Share with" > "Specific people". A dialog with the title

    "Choose people to share with" should appear.

    4) From the "drop-down-menu" (press the "down-arrow" beneath the "Add"

    button)select "Everyone" and press "Add"

    5) On the row "Everyone" in column "Permission level" select "Read/Write"

    6) Press "Share"

     

     

    7) Do the same (step C1 to C6) for the "Flight Simulator X Files" folder

  9. Hi,

     

    EFB requires the Microsoft .net-framework installed on the target computer. Since the .net-framework is not running on any Apple products, EFB will not run on an iPad. Sorry.

     

    I fully understand that the iPad is a nice tool for many things, but I guess that a second monitor for EFB is much cheaper than an iPad ;-).

  10. Hi Swordfish,

     

    according to the forum rules, please sign your posts with your real life first name. Thanks.

     

    Whenever you press "Activate" from within the Route-Setup module, an FSX flight plan will be created/saved automatically into the folder which holds FSX flight plans. Per default this is "C:\Users\[username]\Documents\Flight Simulator X Files" whereas the naming of "Flight Simulator X Files" is depending on the FSX-language.

  11. Hi Vic,

     

    maybe you didn't see the explanation at the top of the runways.txt file?

     

    here it is:

    // Aivlasoft EFB, Runway assignment table: FSX runway to Navdata runway
    // Copyright by AivlaSoft - www.aivlasoft.com
    //
    // *** %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    // *** it is important to always define ALL runways from an airport, 
    // *** whether they have changed or not! 
    // *** %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    //
    // General)
    // Column 1: ICAO 4-letter code of the affected airport
    // 
    // A) if the designator of an existing runway in FSX has been replaced/changed:
    // Column 2: Designator of the FSX-Rwy
    // Column 3: Designator of the corresponding Navdata-Runway
    //
    //  if a runway in FSX does no longer exist in reality (and therefore is no longer listed in Navdata)
    // Column 2: Designator of the FSX-Rwy
    // Column 3: 'nil' (without quotation marks)
    //
    // C) if a runway in reality (and in Navdata) is existing, but is not available in FSX
    // *** this case is not possible to assign ***
    // 
    // ICAO FSX Navdata
    CYHZ 06 05
    CYHZ 24 23
    CYHZ 15 14
    CYHZ 33 32
    PAOM 09 10
    PAOM 27 28
    PAOM 02 03
    PAOM 20 21
    EDDP 08 08L
    EDDP 26 26R
    EDDP 10 nil
    EDDP 28 nil
    
    

     

    BTW: If the runway identifiers are grayed out (when you opened the procedure selector) means that no procedures are available for these runways and therefore they cannot be selected.

  12. mhazy,

     

    I just had a look into the webshop administration and the PayPal account too. I can't see a customer like "mhazy" who has bought an activation key (maybe it might be helpful to know your real name?)

     

    I suggest that you send me any receipt about your purchase so I can start the investigation why you didn't receive the key, ok?

  13. Richard Stefan from Navigraph told me some months ago that they are currently working with only a subset of the whole Arinc 424 dataset and therefore such information is not yet provided to the several add-ons. But they are in discussion with EAG to get a more detailed dataset. Since Richard is still on his motorbike tour I don't know when and how more information can be provided through EFB. I hope that it will be soon.

  14. Hi Paul,

     

    as to my knowledge the server is running since a long time without having problems again. I just did some maintenance today ...

     

    As described in the "installation manual" the firewall has to allow port 80 and port 13 for outgoing traffic. Maybe this is the problem?

     

    Edit 13:48z

    Seems that there is a problem with a Windows update ... I'm working on it ...

     

    Edit 14:15z

    Server is running again. Sorry for any inconvenience.

  15. Hi Jean-Louis,

     

    it took me some time to figure out what the reason for this problem is. But finally I found it: It's the fix name "CLE" in the Navigraph procedures for LEBL. At the beginning of this file a list with all used fixes can be found. There is a fix called "CLE". As per definition a fix with 3 characters must be a navaid (VOR, VORDME, DME). But unfortunately FSX doesn't have a navaid with the identifier "CLE". As a workaround I can only suggest to rename CLE to CLE99. Then it will be treated as a fix and no longer as navaid. But please be carefull in renaming because there are also transitions named "CLE" which should not be renamed.

     

    Hope this helps.

  16. Jean-Louis,

     

    it's the symbol that makes the difference. Please see the picture below where the most left navaid (1CD 111.4) is a DME only, the middle one (YVR 115.9) is a VORDME whereas the most right (YPK 112.4) is a VOR without DME.

     

    D means that a DME is available

    H means 'high altitude'

    L means 'low altitude'

     

     

    Hope this helps.

  17. Mark,

     

    could you please (temporarily) disable the wireless network interface? Maybe this has a side effect on the performance of the network layer.

     

    Micro XP Home Edition 32bit? Is "Micro" a special version of Win XP Home? I'm not sure about the network performance of the "Home" edition but this might be also a point to go indepth if the problem still occurs.

  18. Hi Mark,

     

    thanks for the logfiles. It seems that the network traffic locally on your computer is a bottleneck. Some further questions:

    1) Are there any AntiVirus programs active which might hamper the network traffic?

    2) Computer spec's: Operating system, CPU, Memory?

    3) Does your computer have more than one network card installed?

     

    The DataProvider often detects a timeout when sending data to the DisplayUnit. If the DisplayUnit is not sending a receipt back to the DataProvider within a certain time then the DataProvider drops the connection.

     

    I would recommend the following steps (all of them must be accomplished in the settings, most of them must be done on both programs, DataProvider AND DisplayUnit:

    a) increase the value for "Timeout Sending" from 5 up to 10. This value must be changed on both programs.

    B) uncheck the option "Synchronize UTC time" in the DataProvider settings.

     

    Hope this helps

×
×
  • Create New...