Jump to content

aivlasoft

Administrators
  • Posts

    5,924
  • Joined

  • Last visited

Posts posted by aivlasoft

  1. Hi Franck,

     

    thanks for the logfiles. It seems that somehow the data files could not have been read.

     

    Would it be possible to send me the following 4 files in a zip file:

    E:\Program Files (x86)\IVAO\IvAp v2\data\countries.dat

    E:\Program Files (x86)\IVAO\IvAp v2\data\firs.dat

    E:\Program Files (x86)\IVAO\IvAp v2\data\airports.dat

    E:\Program Files (x86)\IVAO\IvAp v2\data\fir.dat

     

    From the files path I can see "IvAp v2". Is "v2" a new program version?

  2. Hi Franck,

     

    Please do the following:

    - If a route is already activated, open RouteSetup, press "Clear"

    - Restart DisplayUnit

    - Go to "System - Settings - Online"

    - Check "Log data requests", then press OK

    - goto "Route Setup"

    - press "online network - check button", select IVAO and then "Start"

    - after the connection has been established, even if you don't see any controller, press "Close"

    - Shutdown the DisplayUnit

     

    Please send me all the logfiles which can be found as follows:

    Open "Windows Start Menu" > All Programs > AivlaSoft > EFB > Logfiles

     

    - Restart the DisplayUnit and goto the Online-Settings

    - Uncheck the Log Requests checkbox

  3. As per today (April 2nd, 2011) a new installation package version 1.3.1 is available from the download area. For all new installations please use this package.

     

    Installations made prior to April 2nd, 2011 based on binaries with versions equal to or lower than 1.3.0.* can be upgraded to 1.3.1 using the Update 1.3.1, which is also available from the download area.

     

    Quick link to the download area:

    http://www.aivlasoft.com/download/index.html

    It is recommended to upgrade to this version 1.3.1.

     

    For all questions concerning this update feel free to contact us either by postings in this forum or by e-mail to support@aivlasoft.com

  4. William,

     

    there are several items to be checked:

    1) EFB DisplayUnit Settings "Online"

    - IVAO data folder (seems to be set according to your report)

     

    2) EFB DisplayUnit Settings "Charts" > "Traffic":

    2a) Did you check "Show 'online' traffic"?

    2b) Did you define a horizontal or vertical range "filter"?

     

    3) Route setup: "Check" for online traffic and select your provider (IVAO or VATSIM). Then press "Close"

     

    4) Activate the route

     

    5) Do you see the chart-options-buttons "TRFC" and "OTPV" (the latter is only available on ground charts)?

     

    6) Does your pilot-client-software have a slider where you can set the range for traffic? Maybe this range is too small?

     

    Hope this helps.

  5. Hi Dave,

     

    there is a simple "TURN RIGHT" missing in the Navigraph data for the transition "L". Since the difference between current track and next track is 180° EFB cannot determine to which side the turn goes. In such a situation EFB takes the "left side" turn as a default which is unfortunately wrong in this situation.

     

    Before: " ... HDG 113 INTERCEPT RADIAL 158 TO FIX DME09"

    After: " ... TURN RIGHT HDG 113 INTERCEPT RADIAL 158 TO FIX DME09"

     

    See the result below.[attachment=0]EFKT_LLZ16_L.jpg[/attachment]

  6. Kevin,

     

    a closer look into the file "firs.dat" shows that e.g. no positions like "_E_" or "_W_" are defined for EHAA:

    EHAA::NL:Amsterdam:Radar:52.8:4.6

     

    Whereas other FIRs/ARTCCs like EDGG (Langen Radar) have explicitly defined their sub-positions like "_W_" or "_N_" etc:

    EDGG:N:DE:Langen:Radar:51.30:7.4:EDGG NORTH

    EDGG:W:DE:Langen:Radar:49.8:7.28:EDGG WEST

    EDGG:S:DE:Langen:Radar:49:8.91:EDGG SOUTH

    EDGG:E:DE:Langen:Radar:50.35:9.44:EDGG EAST

    EDGG:NW:DE:Langen:Radar:50.7:6.76:EDGG NORTH-WEST

    EDGG:SE:DE:Langen:Radar:49.6:8.9:EDGG SOUTH-EAST

    EDGG::DE:Langen:Radar

     

    Therefore EFB cannot recognize the active services from a sector if the controllers are logged in with an ID that is not known due to the definitions in the file "firs.dat".

     

    For the airports it seems to be a bug that they are not show correctly. Should be fixed with 1.3.1.

  7. Hi Jack,

     

    thanks for pointing at the "NY_" situation. From the information given in the two files "fir.dat" and "servinfo.dat" it is not possible to exactly determine whether the oceanic area is staffed or not. I will try to explain how.

     

    Let's assume that the following two controllers ("callsigns") are logged in:

    NY_KND_CTR

    NY_JBC_FSS

     

    The two letters "NY" are the key for the area. I assume that "KND" means "Kennedy", I don't know what "JBC" means. "CTR" means "Center", "FSS" is somehow similar to a "Center".

     

    Because the endings of two callsigns are CTR/FSS, the service must be a control area (not an airport). In the file "servinfo.dat" we must now look for a "control area" with a key "NY" or an alias "NY". There is one area in the [Controls] section which has an "NY" alias and "KZNY" as a 4-letter ICAO key:

     

    [Controls]

    KZNY/New York/NY/

     

    It seems that this is the area that we searched for. Now the 4-letter ICAO code points to the FIR/ARTCC boundaries which are listed in the file "fir.dat". Unfortunately there are two boundaries and each of them has "KZNY" as a key:

     

    [FIRs]

    KZNY,32,18.000000,-77.000000,45.000000,-40.000000,K+ oo,31.500000,-58.500000

    KZNY,72,37.227500,-78.127778,42.941667,-67.000000,KZ255dd,41.000000,-75.500000

     

     

    If it were clearly defined in some papers I could "hard-code" that "NY_JBC_FSS" means the oceanic sector whereas "NY_KND_CTR" means the New York area, but as always "hard coded" items are dangerous and not really flexible ;-).

     

    Any other ideas?

    Are there other "secret" definitions that we must be aware of?

  8. There are two places where one can define whether and how much traffic should be displayed:

     

    - Pilot client software (FSInn, SB3/4, IvAp): Most of them have a slider or a similar control where the range around your current position can be selected. This value is somehow the "master" value.

     

    - EFB settings: "Charts" - "Traffic": Herein you select

    a) whether you generally want to have the traffic depicted (checkboxes at the upper area of the dialog), and

    B) you may set a horizontal range (which obviously cannot be higher than the "master" value set in the "pilot client software") or a vertical range in feet, or both of them.

     

    - If the values a) and B) are set then you can switch between "traffic visible" and "traffic not visible" using the chart option for traffic "TRFC".

     

     

    Independent from the "pilot client software" value the biggest range is approx. 100 nautical miles, which is a limit that is defined by the AI/Multiplayer-traffic system from FSX.

  9. Hi Haris,

     

    I used this export function very often in the past (when I had the time to fly the 744 :roll:). Meanwhile I'm only programming ... ;) but I don't want to complain ... I like this job very much, really!

     

    I don't want to make a secret about the source where I finally found the information that helped me. Especially not if it's a website that provides in-depth and professional information. It also provides a flight plan converter into the rt2-format.

    http://www.bleedair.de/company-route-generator.html

×
×
  • Create New...