aivlasoft

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?

Current users may update their EFB installations by downloading and executing the AivlaSoft EFB Installer or Update 1.3.7 found here: http://www.aivlasoft.com/download/index.html Changelog: http://www.aivlasoft.com/download/changelog.htm

Hi David, The positions of the runways as well as the surface information are both taken from the BGL files. EFB doesn't change it. If EGSU is a third party scenery I suggest to contact the developer of the scenery.

Hi Pete, development for version 1.x has been stopped last year already. I'm working 7 days a week on version 2. If I still were spending my time for version 1 development it would result in more delay for version 2. New versions 1.3.x will only be released for bug fixes and for "easy to develop" things. I'm aware of your wish and I can tell you that it is already implemented in version 2, but because version 1 is another architecture it is not an easy task to do the same there. I hope for your understanding.

Hi, as per the forum rules, please sign your posts with your real first name. Thanks! Thank you very much for these detailed workflow lists. Would you mind if I move them over to the download page of our website? There we have a special section for such downloads. http://www.aivlasoft.com/download/index.html

Hi, thanks a lot for your good words on EFB. Much appreciated

Hi Michael, There is no specific "reset" procedure, just quit and restart it. I cannot say that a certain combination of add-ons is the cause for problems. Maybe it's a certain situation which stresses FSX.

Michael, when you experience this again, please open the "AI traffic monitor" from the DataProviders menu. This monitor will show what comes out of SimConnect. If no traffic is listed there then SimConnect doesn't provide traffic data. If SimConnect is overloaded due to other simultaneously running add-ons, it sometimes stops forwarding traffic data.

Hi Henk, could you please send me all the logfiles to support@aivlasoft.com. They usually can be located here: C:\Users\[username]\Documents\AivlaSoft\EFB\Logfiles

Hi Andrew, please check your inbox. 2013.

Hi Pietro, EFB "only" writes a flight plan to the FSX GPS.

Hi Andrew, EFB "only" needs the data files which are provided with the installation of "The Eye". You don't have to install that application. I could send you a copy of these files if you like, but I'm afraid that they are no longer up to date. I tried several times (to not say countless times) to get in touch with the people at IVAO, but until today I didn't get a reply onto my question whether there is an official download link for the FIR data files. Maybe other IVAO users here in this forum know more? It would be very very helpful ...

Carlos, I haven't received the logfiles you mentioned. When did you send them? Anyway I thought that this report has become obsolete since you wrote "Does not matter, I'm getting METAR from Active Sky". I copied the content of your post and then removed it here in the forum, just to save space and improve readability. From the content you provided herein I can only say that there is no error or warning entry from the built-in FTP service, therefore I must assume that the problem is beyond of EFB. Dave (see some posts above) also sent the logfiles but there we could find an entry which pointed in the direction of a router configuration issue.

Hi Richard, I will have a look whether it is by coincidence or whether there is a certain reason for the minimizing of the DisplayUnit. The zoom level of the chart is not assignable, it's always the latest zoom setting that will be applied.

Hi, tested and fixed. Version 1.3.7 sent to the beta testers.

Hi Marty, I cannot give you an answer on that, you must ask ATC. . EFB version 1 doesn't support removing waypoints from a standard procedure (SID, STAR, Approach).