aivlasoft

Andreas, will check this tomorrow.

Pete, I'm still not knowing what's the problem but on the screenshot from your "MakeRunways" I can see that the ILS identifier is IABB whereas on your screenshots from the charts it's IAC. Maybe this gives a hint? Would it be possible to send me that file "EIDW_ADEX_ADE.BGL" to support@aivlasoft.com for further investigations?

Hi Pete, very strange indeed. On my system with 1.3.5 installed, the correct frequency of 111.5 is shown. If you open the airport information and double click into the area left of the "close" button you see the name of the currently considered BGL file. Is that same as on my screenshot? [attachment=0]eidw.png[/attachment]

Ed, please send the logs to support@aivlasoft.com.

Hi, - did you also check the settings in your pilot client software (IvAp)? There must be a slider or a similar control to set the range of other aircraft. - do you see the traffic in FSX? - from the DataProvider's menu you can start the AI aircraft monitor. Are there any aircraft listed? BTW, according to the forum rules please sign your postings with your real first name. Thanks.

Hi Steve, If you have the program ADE (Airport Design Editor) on your computer you could have a look at the bgl file just to see whether ADE gives you the same result. To figure out the name of the BGL file you may proceed as follows: Run EFB and load EGGW. Once you have an EGGW chart active, open the Airport Information and double click in the blank area above the General Info / Communications tabs until you see a filepath and filename. If you don't have a copy of ADE, you might send the file to support@aivlasoft.com so I can have a look inside.

If you experience some strange lines in the Level-D FMC when loading a flight plan that has been created with the EFB Level-D flight plan handler, try to use the updated handler which can be downloaded here. [attachment=0]AivlaSoft.FlightPlanHandlers.LevelD.dll.zip[/attachment] How to replace the flight plan handler? Please follow the instructions below: 1) Download the updated flight plan handler to a temporary folder and unzip the file. 2) Quit EFB DisplayUnit 3) Open Windows Explorer and locate the folder "plugins" which is below the installation folder of EFB (normally this is something like "C:\Program Files\AivlaSoft\EFB\plugins"). 3) Replace the file "AivlaSoft.FlightPlanHandlers.LevelD.dll" in that folder with the downloaded file (see step 1). 5) Start DisplayUnit.

Hi Steve, is that from stock BGL or some add-on scenery? It seems that this BGL file contains some "hidden secrets".

Hi, due to the very fast help of Richard Stefan from Navigraph (thank you very much!), a new revision (Rev 2) of the AivlaSoft EFB data is available at the Navigraph FMS page: http://www.navigraph.com/www/fmsdata.asp

Hi, thanks for your reports. It's a problem that comes with 1208. I just wrote to Richard Stefan from Navigraph. I hope to get a feedback soon.

Pascal, the shortcuts that can be defined in DataProvider are shortcuts that will be recognized from within FSX only. This is meant for the purpose of handling the local EFB DisplayUnit without the need of changing the window and therefore loosing the focus on the FSX window. In EFB version 2 you will have shortcuts for the handling of the DisplayUnit itself. Shortcuts to be sent over the network could be stuff for version 3 .

Hi Clive, Unfortunately no, and it seems that I'm slowly running out of ideas what could be the cause for that.

Hi, at least it is on the 'planned features' list ...

Joe, didn't you receive my email from 2012-07-12 ?

Kai, I'm afraid that there will be no other possibility. Please read the following explanation (taken from the installation and configuration manual ...) The "full screen mode" of FSX may NOT be used in cooperation with the EFB-system if the DisplayUnit is running on the same computer than FSX is running. Why? It's a fundamental concept of the Microsoft Windows operating system that Windows “multitasks” – that it may run several programs (each of them in its own window) at the same time. All of these running programs are shown in the taskbar at the bottom of your display. But only one of them can be the program that is in the foreground (also known as “having the focus”). As long as the foreground window doesn't use the whole area of your screen, you may see the other windows behind or beside of the foreground window. But still only one program is in the foreground. However in full screen mode, FSX does not function as a multitasking Windows’ window. The "FSX full screen mode" is a special graphic mode which bypasses this standard XP/Vista/Win7-windowed mode and therefore the above described features of a windowed operating system are no longer available. You will then have a single-window operating system wherein FSX is the one and only visible program. The only way to use FSX in "Full-Screen-Mode" while simultaneously running the EFB-system is to use a network based environment where you would run EFB DisplayUnit(s) on a different computer than the computer which FSX and the EFB DataProvider are running on. I don't think that there will be a possibility (from a technical point of view) to run EFB as a gauge.

Petr, I'm sorry, but TCAS.dll is not a module which comes with EFB. It seems to be a module of FSX. So in my opinion this is not an issue that is caused by EFB.

Orest, here you can see the changelog: http://www.aivlasoft.com/download/changelog.htm

Mark, There is no possibility to change the size of the menu in EFB V1. EFB V2 will be much more user friendly in this regard.

Current users may update their EFB installations by downloading and executing the AivlaSoft EFB Installer or Update 1.3.5 found here. Update 1.3.5 is fixes the issue with the new RouteFinder data format. For details please see here: viewtopic.php?f=5&t=1054

Hi Brenden, I just wanted to say the you only have to add the entries into the runways.txt file if there is a difference between the runway identifiers from FSX (add-on scenery) and Navigraph. If the scenery you have installed, reflects the today's situation you won't have to add these lines in the runways.txt file. Let's try the following: - remove any EGLC lines from the runways.txt file - save the file - clear airport cache in DisplayUnit - select airport EGLC Now the DataProvider will show you some lines like the following: - Request for Airport [EGLC] from '127.0.0.1' received. - Navdata runway ident 09 at airport EGLC could not be assigned to FSX runway. - Navdata runway ident 27 at airport EGLC could not be assigned to FSX runway. - Available FSX runways at this airport are as follows: 10, 28 Now open the runways.txt and enter the following lines: EGLC 10 09 EGLC 28 27 If the DataProvider on your computer shows other runway identifiers than what I have listed here, you must adjust the numbers accordingly. Save the file, clear the airport cache again and reload the airport. Now the message should no longer appear.

Hi, according to the forum rules, please sign your posts with your real first name. Thanks. I'm not sure whether this VFR scenery reflects the runway numbers of today, but if this scenery is up-to-date, then you won't need to add the entries for EGLC in the runways.txt file. Please verify whether they can be removed. Just to remember how EFB acts 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.

Yes, there was a tiny change in the data format.

Hi all, I just released an update to the beta-team. If there are no problems with this new version I expect the release date by the end of this week.

Hi, same here. As a work around I can suggest the following: After pressing "Find route" on the route finder page, scroll down and manually copy/paste the route description into EFB.

Hi Richard, EFB V2 will have auto update capability .