aivlasoft

Holger, I'm not (yet) flying online with IVAO so I don't know their expectations concerning the flight plan format. Do they use others than ATS description (e.g. "NIK UM624 TOLEN UN873 JUIST UP729 DOSUR P729 LUGAS")?

Phil, thanks for your kind words. We're working hard to make version 2 even better .

Phil, thanks for the logfiles. As far as I can see you didn't have the SP4 installed yet? Could you give it a try?

Holger, sounds a bit strange to me since SP4 didn't change things around traffic items. The TRFC button is only available if: a) Settings > Charts > Traffic: AI/Multiplayer Traffic is ON (if you fly online, then you also have to tick the option below "online traffic" FSX must be connected/running

Glen, maybe this is also of interest: http://forum.avsim.net/topic/344479-why ... -with-ngx/ http://forum.avsim.net/topic/343684-simconnect/

Glen, I heard/read from others that it might be a problem of the new 737 NGX. Did you operate that aircraft?

Dave, I experienced in the past that sometimes AFCAD files are in FS9 format instead of FSX format. It seems that FSX can read both whereas EFB only knows the FSX format. Can you send this file to support@aivlasoft.com so I can have a look into it?

Eli, ahhh, now I see it 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.

As of per August 16th, 2011 a new service pack 4 is available from the download section: http://www.aivlasoft.com/download/index.html Changelog: http://www.aivlasoft.com/download/changelog.htm

Eli, a quick look into the folder "[FSX]\AivlaSoft\SIDSTARS" tells that there are no procedures for this airport provided by Navigraph (cycle 1108).

Marc, yes, an exclude function (based on wildcards) will be implemented in version 2.

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?

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?

ask him ...

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.

olé Jack, ServicePack 3 is already available. Please follow the link that has been provided by Travis. In a very short time we will release another SP4. It is still being tested by the beta testers. This will fix some minor bugs but it will not contain a new flight plan handler.

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.

thanks for reporting this. I will address this with version 2.0.

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.

Hi Pete, Does it happen all the time, or was it only a "one-time" issue? I'm asking this because from the code I cannot see how it could happen.

Fixed with SP4.

Dave, thanks a lot for this detailed report. Now I could locate the bug . SP4 is underway ...

Björn, thanks for this info. Please be aware of the fact that such manual additions will be overwritten as soon as "the Eye" updates its files. The better way would be to ask someone at IVAO to add this line to their "official" data file.

Thanks Phil, much appreciated .

Grzegorz, regarding your latest post in the Navigraph forum, I'd like to ask whether you have any third-party scenery installed for either EPGD or EPWA or for both? Could it be that the runways.txt file is not configured properly?