Jump to content

aivlasoft

Administrators
  • Posts

    5,929
  • Joined

  • Last visited

Posts posted by aivlasoft

  1. Elemerson,

     

    I just tried to connect to the activation server and I can say that the server is up and running. No problems on this side. Anyway I would not suggest to turn off the firewall and the AV software. Usually it works when both are on.

     

    On another occasion the activation went smoothly.
    Have you changed any system configuration, router configuration since then?
  2. Mark,

     

    I think the only way to get rid of this behavior is to delete the settings file (and its backup file).

     

    The file can be located as follows:

    C:\Users\[username]\Documents\AivlaSoft\EFB\Settings\DisplayUnit_UserSettings.bin

     

    Before deleting the file, quit the DisplayUnit.

     

    After successful deletion of the file, start the DisplayUnit and verify/set the settings.

  3. Paul,

     

    Port 13 is used to get current date/time from a internet time server. This is due to security considerations but it is only during the trial period.

     

    I first thought that it must have to do with your router or firewall, but then I re-read your post and I saw that you sometimes can connect and sometimes not. So this is very difficult to advise what to do, especially if one is not sitting in front of your computer.

     

    Any network/router/firewall specialists here in this forum?

  4. Peter,

     

    there is no "trick", just assign the runways ;-).

     

    Here is what the DataProvider shows:

     

    Navdata runway ident 08 at airport LOWL could not be assigned to FSX runway

    Navdata runway ident 26 at airport LOWL could not be assigned to FSX runway

    Available FSX runways at this airport are as follows: 09, 27, 09L, 27R

     

     

    If you open the "runways.txt" file (using any text editor) you can read detailed instructions on top of the file. You must assign the runways according to the schema "ICAO - FSX runway - Navigraph runway".

     

    For LOWL:

     

    LOWL 09 08

    LOWL 27 26

    LOWL 09L 09L

    LOWL 27R 27R

     

    You always must assign all runways, whether they have changed or not (for LOWL 09L and 27R have not changed but must be assigned too).

     

    After these changes have been applied, do not forget to reset the airport cache (DisplayUnit settings, miscellaneous), or restart the DisplayUnit.

  5. Hi,

     

    as per the forum rules, please sign your posts with your real first name. Thanks.

     

    I think that the route modify page is not the best place to create a route from scratch. Did you already try to create a new route using the ATS route description which you easily can copy/paste into the textbox (Route Setup > Select > "Enter route description"). Details see "Operations manual", section 5, page 8 ...

  6. Clive,

     

    thanks for uploading the files. I can see that the DataProvider seems to stuck when it tries to analyze some stock scenery data. Usually this means that your FSX installation seems to be corrupt. But first we should try to find out where exactly the DataProvider quits. Do you know the Windows System Event Viewer?

     

    You can open it like this:

    - Open Windows Start Menu

    - Select "Administrative Tools"

    - Select "Event Viewer". This will start the Event Viewer. After some seconds the tree in the left pane should be populated.

    - Open the "Windows Logs" branch and select "Application". Now the middle pane gets filled.

    - Scroll down until you find a row which has a "Error" sign in the colum "Level". Select this row. In the lower middle pane you see the details about this row.

    If the details are showing the name "DataProvider" as the source you have found what we're looking for. Can you copy/paste the content of the "Details tab"?

  7. Ryan,

     

    welcome aboard.

     

    The error message "Could not read 'scenery.cfg' due to following error: String was not recognized as a valid Boolean" means that your scenery.cfg is corrupt. This can happen during the installation of a scenery when the installer tries to update the scenery.cfg.

     

    You can easily fix the problem as follows:

    1) Locate the scenery.cfg and open it using any text-editor like "notepad.exe". On Windows Vista and Windows 7 systems the file can be located as follows: C:\ProgramData\Microsoft\FSX\scenery.cfg

     

    2) Every entry for a certain scenery consists of the following lines:

     

    [Area.120]
    Title=Edwards_AFB
    Local=Scenery\Cities\Edwards_AFB
    Layer=120
    Active=TRUE
    Required=FALSE
    

     

    Somewhere in your scenery.cfg one or more of these lines are mixed up and EFB cannot recognize the value "TRUE" or "FALSE" because there is some more data on the same line, which is not allowed. After a "TRUE" or "FALSE" value it must be blank.

×
×
  • Create New...