aivlasoft

Hallo Wolfgang, I tried to install the scenery but somehow I was not successful ... Please open the Airport Information dialog for LKPR. Then double-click in the blank area above General Info / Communication (see picture below). This will show the filename and path of the currently loaded airport-bgl file. Is the filename same as on the picture below, or is it different? [attachment=0]lkpr_filename.png[/attachment]

Hi Mark, thanks for the bgl files and many thanks to the link to this great scenery. After some investigation I could find the issues in EFB (cargo places, jetways and tower position). I sent you a email concerning the technical items yesterday. I will fix it asap, but it takes a little time since there is another item which I would like to integrate in the next upgrade 1.3.3.

Hi Petr, Most probably it's a matter of the "runways.txt" file. Please have a look at this thread: viewtopic.php?f=5&t=995 In this thread it is explained how the "runways.txt" file is used by EFB. I think that what you describe will be available in version 2.

Mark, since you are the developer of this scenery, would you mind to send me the required files for further investigation? You may send it to support@aivlasoft.com. Thanks. I must have a look into the source code files. It's quite a long time ago when I wrote this code, but I'm sure that I do not interpret the name somehow.

Hi Jack, thanks for the good news. When I did some research today I also stumbled over this KB article but I didn't want to recommend it since you wrote that you have Win 7 and the article is for XP, Server 2003 and Vista. Anyway, I'm glad to know that everything now works.

Jack, please check your inbox.

Jack, I'm afraid that screenshots will not help me either. The exception has been thrown from the underlying .net framework (SocketException) and therefore it's beyond the scope of EFB. It might sound hard to you but sometimes the only way to fix such a problem is to do a clean re-install of Windows 7.

Marc-Andre, I did some tests now and it seems that the problem only exists if you try to get the METAR data for an airport which is not listed at NOAA. Here for example I tried to load data for SPNP which is not available: 2012-06-10 18:09:15,473 [17] WARN AivlaSoft.Efb.DisplayUnit [(null)] - File SPNP.TXT not available for download. 2012-06-10 18:09:15,784 [17] WARN AivlaSoft.Efb.DisplayUnit [(null)] - MetarRequestService: (threaded) FTP connection aborted with error 2012-06-10 22:02:47,774 [16] WARN AivlaSoft.Efb.DisplayUnit [(null)] - File SPNP.TXT not available for download. 2012-06-10 22:02:48,316 [16] WARN AivlaSoft.Efb.DisplayUnit [(null)] - MetarRequestService: (threaded) FTP connection aborted with error 2012-06-11 08:59:03,421 [6] WARN AivlaSoft.Efb.DisplayUnit [(null)] - File SPNP.TXT not available for download. 2012-06-11 08:59:03,731 [6] WARN AivlaSoft.Efb.DisplayUnit [(null)] - MetarRequestService: (threaded) FTP connection aborted with error If I try to get METAR for LSZH it works (no entry in logfile).

Pete, from the source code I can see that the frequencies are enabled as soon as the connection state is "green", which means the connection to FSX is up and FSX is running (not paused nor any menu item is open).

Hi Don, thanks for your feedback. I'm glad to read that you have sorted out the problem.

Andreas, thanks for the good news. I just realized that when I wrote my post I forgot to mention that you should try to remove the lines, but I see you already did it .

Jean-Claude, did you already read this: viewtopic.php?f=3&t=217

Jean-Claude, EFB needs the .net framework to be installed, at least version 3.5 SP1. Could you please verify this?

Hi, according to the forum rules, please sign your posts with your real first name. Thanks. Does it happen at all airports or only at certain airports. Does it happen with all approach procedures at a certain airport?

Hi Andreas, are you using stock scenery or third-party scenery? If you are using a third-party scenery you may check the content of the "runways.txt" file. With the default installation some entries for LFSB are already in there. By default the "runways.txt" file can be located in the following folder: C:\Users\[username]\Documents\AivlaSoft\EFB\UserData

Florin, just a guess from my side: If you can read these flight plans into FSX then it might be that the data format is FS9-style. Did you already try to load it into EFB using the FS9/2004 import module?

@all, please do not rename "AivlaSoft.Efb.DataProvider.exe" to "Fsx.exe", because it will not work in certain situations, especially when a restart of the application is needed. As I already described above, the DataProvider connects to SimConnect and not to Fsx. It only watches for a running process named Fsx so as not to continuously try to connect to SimConnect when Fsx is not (yet) running. To make sure that the scenery update is scanning the "Prepar3D bgl-files" you also must update the registry key for the Fsx installation path. But if you do so, bear in mind that a next EFB-installer might no longer run since it also reads this key from the registry. Please don't forget that Prepar3D is not yet supported by EFB. Please wait for version 2. I cannot guarantee that all this tinkering will work in every circumstances. You do it on your own risk.

Gary, thanks for the files. The route that you sent to me loads perfectly into the 737NGX FMC and the 744X FMC (I do not have the J4100 and other aircraft from PMDG). Please verify whether you saved the route for the 737NGX in the path "..\flightplans\NGX". The NGX requires the flightplans to be found in that folder and not only "Flightplans". The 744X is using the folder "Flightplans". It seems that this is not the problem (Windows filesystem is not case sensitive). Can you please verify whether the following settings are set:DataProvider: "Folders" tab, then "Create FSX flight plans" and select the folder where the FSX flightplans must be saved. If you have an English version of FSX then it is most probable the following folder: C:\Users\[username]\Documents\Flight Simulator X Files DisplayUnit: "Folders and Links" tab, then "FSX flightplnas". Select the same folder as above described. DisplayUnit: "Miscellaneous" tab, then "Create Garmin GPS Flight plans" DisplayUnit: "Charts" tab, then "Traffic" tab -> "Show AI / Multiplayer traffic". What product for AI traffic do you use?

Gary, could you please send me the following files for inspection: - C:\Users\[username]\Documents\AivlaSoft\EFB\Settings\DisplayUnit_UserSettings.bin - the EFB route (*.efbr) which you used to create the PMDG rte-file - the resulted and saved *.rte file itself Please sent them to 'support@aivlasoft.com'

Allan, I'm glad to hear that you have sorted out the issue and that the registration worked. Thanks for your feedback.

Hi, According to the forum rules, please sign your posts with your real first name. Thanks. FSX allows a maximum range of approximately 200 km (~ 108 NM). This is used internally in EFB. If you don't set any further filters in the DisplayUnit settings then this is the range that airplanes will be considered. If you fly online (IVAO or VATSIM) you should not forget to check the respective filters in the corresponding 'pilot-client-software' (Squawkbox, FSInn, IvAp).

Joe, as far as I know the problem has been solved by installing the latest version of EFB (1.3.2 SP1) AND installing the latest service pack for the 737NGX (IIRC this must be SP1c).

Salut Jean-Louis, I also had a look at this first and couldn't find an entry for LFOB. So I decided to "dig" a bit deeper . I must assume that the situation here is the same. Maybe it helps to explain how the "runways.txt" file is used by EFB. Whenever a FSX runway identifier is used in conjunction with a Navigraph runway identifier, EFB looks first whether there are some assignments for the related airport in the "runways.txt" file. If an assignment has been found it will always be considered to determine the identifier. EFB doesn't verify whether it is right or wrong. Done, but I just realized that it must be shortened because of the limited space for a thread title ...

Jean-Louis, I just have had a look into the replaced file "APX48140.bgl" and I must say that the runway identifiers have changed. With the "RadioAids" file they are now in accordance with the Navigraph data. In other words, just remove the LFOB lines from your "runways.txt" file and the approach procedures will be available again. BTW, would you mind if I were changing the title of this thread to "EFB does not show approach procedures after installing 'RadioAids'"

Hi, According to the forum rules, please sign your posts with your real first name. Thanks. EFB reads the taxiway information from the BGL files. If the information is not found in the BGL file then it cannot be depicted. I don't have this scenery file(s) so I cannot say whether this information is available there or not. Sometimes it's also a problem that scenery designers compile the files in FS9 format instead of FSX. Since EFB has been developed according to the BGL-file definitions of FSX it cannot read FS9 formatted files. I'm not a scenery designer, but I heard of possibilities to show some items in the scenery without having the data for the item in the BGL file. A question to other users of UK2000 EGLL: Is the issue described above something that also happens on your system?