aivlasoft

Hi Glenn, the runways.txt file cannot contain different runway settings for a certain airport. If the entries in the file don't match the requirements of your installation, then feel free to overwrite or even remove them. There are some default entries (e.g. PAFA) which are coming with the installer. So maybe they are already outdated and can be removed/replaced. Maybe this viewtopic.php?f=3&t=1260 will help too.

Jean-Louis, I don't know where you have this cycle from but that one that I have downloaded some minutes ago doesn't list FADN. If you have a look at the header of the file that you have posted and then compare it to any today's header you will see that there is a difference. So from my point of view this file must be very old and I don't know how this file came into that cycle which is installed on your machine. I suggest to remove the currently installed cycle from your harddisk, then download the latest AivlaSoft EFB data format from the Navigraph website and try again. I cannot imagine that Navigraph lists

Jean-Louis, indeed, it's very confusing. I just downloaded the latest AIRAC cycle 1303 from Navigraph and I still cannot find a data file for FAJS, but for FAOR. Very confusing that your 1303 cycle contains data from 1213 I had a look now into the archive and would like to let you know the following outcome: Cycle 1213 lists FAJS but not FAOR Cycle 1301 lists both, FAJS and FAOR Cycle 1302 lists FAOR but no longer FAJS Cycle 1303 lists FAOR but no longer FAJS to be continued ...

Jean-Louis, ... you're kidding I had a look at the current cycles from Aerosoft and Navigraph and it's like I already said: They are not providing navigation data for FADN.

Salut Jean-Louis, The ICAO code FAJS has been changed to FAOR in real world. That means that navigation data from Navigraph and Aerosoft does no longer provide data for an airport using FAJS as ICAO code but for an airport with ICAO code FAOR. Your FSX airport is still using the ICAO code FAJS. Therefore EFB cannot find a match between the ICAO code used in navigation data and the ICAO code used in FSX. The only way to solve such an issue is using an (up-to-date) add-on scenery which is already using FAOR as the ident of the airport.

Hi Glenn, I'm with you 100% ... Unfortunately you have to download the Navigraph database for each of your add-ons individually. If you have a look at the Navigraph FMS data page (http://www.navigraph.com/FmsDataDownload.aspx) you can see that in the mean time there are around 50 add-ons listed. Most of these add-ons are using an individual data format. BTW, same is necessary for Aerosoft's NavDataPro, but once you know their installer software, it's a bit easier to accomplish.

Salut Jean-Louis Please read this: viewtopic.php?f=5&t=1237

Hi, as per the forum rules, please sign your posts with your real first name. Thanks. You may paste the files in a folder at your discretion. Then open the DisplayUnit settings, go to the tab "Online" and reference the files. In the first text box select the "fir.dat" and in the second text box select the "servinfo.dat" file.

Iain, there are some settings to "play" with: DisplayUnit > System > Settings > Charts > Traffic > "online traffic", there you can select whether the pilot client software is providing the speed in Km/h and another setting where you can select whether the speed is given in IAS or GS. Is this the first time when you see the difference or maybe you have changed the pilot client software?

Hi Richard, no, I couldn't find a certain reason why this happens. I can only imagine that it has something to do with a previously saved window mode? No other ideas, sorry.

Firas, the DisplayUnit saves its position and window mode on exit. Try to exit the program when it is in windowed mode (neither minimized nor maximized).

Firas, you will not lose any user data when installing the update. If you have already installed a previous version, use the update. If it's a first time installation, use the full installer.

Thanks Axel for your reply. From my point of view there is no explicit sequence to follow when starting up FSX and EFB. At least I don't follow a certain sequence. Anyway I'm glad to hear that you can use the program now and you can enjoy flying the Citation .

Salut Patrick, the demo version is not limited in functionality, only in time. What error message do you get when you try to save the plan?

Axel, could you please send it to support@aivlasoft.com, along with all the logfiles from EFB? The logfiles can be located at C:\Users\[username]\Documents\AivlaSoft\EFB\Logfiles. If you run a network installation, please attach the logfiles from both computers. Thanks.

Hi Tom, I know that attaching is not possible, that's why I wrote "... send to support@aivlasoft.com" From the flight plan that you have posted I can see that there are no enroute waypoints in it. From my point of view therefore it is nothing wrong when you only get the origin and the destination airport in the iFly FMC. The SID and STAR information is not read from the FMC, only enroute waypoints. The SID and STAR must be selected manually using the FMC keyboard.

Tom, there is no flight plan attached Could you please send the flight plan KDAL-KMSY (as EFB plan, *.efbr) to support@aivlasoft.com? I will try whether I can reproduce what you describe.

Hi Max, please check your inbox.

Hi, I'm really sorry but I don't speak French. Please, according to the forum rules (at the top of each page): 1) Since this is a worldwide support forum please write your posts in English. 4) You have to sign your posts with your real first name. Thanks.

Hi David, thank you for sending the files. I have had a look at them and from my point of view it is an issue that must be fixed by the developer of that scenery. He should try to achieve one single file which contains both runways, the grass and the asphalt. Currently there are two files (EGSU and EGS2), the first one contains four runways which seems to be wrong (see image below), the second file consists of only the grass runway. [attachment=0]egsu_four_runways.png[/attachment]

Firas, please read this: viewtopic.php?f=3&t=1260 Hope this helps.

Purpose of the file Due to the fact that navigation data is 'up-to-date'(if you are using the latest AIRAC cycle) but FSX data is some years old, it might happen that the runway identifiers between navigation data and simulator data do not correlate. There are several reasons for this such as new runways in real world, no longer used runways in real world, or simply because the runway identifier has been changed due to shifting of the earths magnetic field. Where to find the file Depending on the operating system on your computer, the 'Runways.txt' file can be located on the DataProvider computer as follows: Windows VISTA, Windows 7 C:\Users\[user Name]\Documents\AivlaSoft\EFB\UserData Windows XP C:\Documents and Settings\[user Name]\My Documents\AivlaSoft\EFB\UserData Content of the file The runways.txt file contains information about the correct assigning of FSX runway identifiers and navigation data runway identifiers. The data format is as follows: Column 1: ICAO 4-letter code of the affected airport Column 2: FSX runway identifier Column 3: Navigation data runway identifier Warning messages Whenever you experience the following exception message on the screen of the DisplayUnit, you must pay attention to the DataProviders window. There you can see the details of the assignment problem at the requested airport. runway_assignment_warning_DataProvider.png[/attachment] Request for Airport [KTPA] from '127.0.0.1' received. Navdata runway ident 01L at airport KTPA could not be assigned to FSX runway. Navdata runway ident 01R at airport KTPA could not be assigned to FSX runway. Navdata runway ident 28 at airport KTPA could not be assigned to FSX runway. Navdata runway ident 10 at airport KTPA could not be assigned to FSX runway. Navdata runway ident 19L at airport KTPA could not be assigned to FSX runway. Navdata runway ident 19R at airport KTPA could not be assigned to FSX runway. Available FSX runways at this airport are as follows: 18R, 36L, 18L, 36R, 09, 27 --------------------------------------------------------------------------------- What to do now? Step 1: For each FSX runway (see the line "Available FSX runways ...") you have to add a line to the runways.txt file: KTPA 18R KTPA 36L KTPA 18L KTPA 36R KTPA 09 KTPA 27 Step 2: Then you have to determine which runway identifier of the navigation data must be assigned to each of the FSX runways: KTPA 18R 19R KTPA 36L 01L KTPA 18L 19L KTPA 36R 01R KTPA 09 10 KTPA 27 28 Step 3: Save the file. Step 4: Go to the DisplayUnit's settings dialog, tab "Miscellaneous" and press the button "Reset airport data cache". Step 5: Reload the airport by pressing "Airports", then "Last selected ..." Note: 1) Sometimes, especially if new runways have been built at the real world airport, it is required to get some more information about the airport to figure out the correct assignment. The internet is a good source for such information. If you have navigation data for a new real world runway but this runway is not available in FSX you don't have to add a line. 2) If a runway in real world has been closed but is still available in FSX, you will no longer find navigation data for such a runway. In such a situation use the word "nil" for the third column, e.g.: ABCD 22L nil 3) If you experience a runway assignment exception message, it is important to always define ALL runways from an airport, regardless whether they have changed or not! 4) The content of the runways.txt has priority over the current BGL file content. Whenever EFB finds some lines for a certain airport in this file, these lines will be considered as the runway assignments which have to be used. If the assignments are not properly defined, or if these lines are not (no longer) needed due to new scenery data or new/changed navigation data, it can cause problems too. In other words, if you have the latest scenery of a certain airport installed and you have installed the latest AIRAC cylce and you find some lines of this airport in the runways.txt file, then these lines most probably can be removed.

Hi Charles, the workflow lists are available now from the download page. Thanks again for your great work!

Hi David, You explanation was OK, at least for me . EFB does not use the data from the Airac cycle when it depicts a runway on the ground chart. This data is only taken from the BGL file which has been created/compiled by the developer of the scenery. Therefore the cause for drawing the runways superimposed on top of each other must have another cause than the Airac cycle or the runways.txt file. The runways.txt file is only used to make the assignments of the (old) FSX runway identifier to the (new) navigation data runway identifier to show the corresponding procedures for a certain runway. When you open the airport information dialog for EGSU, you can make a double-click into the free area above the two tabs "General Info" and "Communications". This will show the name of the BGL-file which is used for that airport. You may send that bgl-file to support@aivlasoft.com, so I can have a look inside of it.

@William, Some days ago I just finished an algorithm which will do that. But it is only for version 2 (It would result in too much work doing the same for version 1). @Firas, - At which airports do you have a problem? - Are these airports stock scenery or third party add-ons? - What is not clear to you when you have read the manual?