aivlasoft

leodirk, as already mentioned in earlier posts (see below) the exception which will be raised unfortunately is not documented. Investigations are running, hopefully a solution can be found until the release of SP4. http://www.aivlasoft.com/support/viewtopic.php?f=5&t=49 http://www.aivlasoft.com/support/viewtopic.php?f=5&t=41

Tom, the time synchronization is a feature mainly used on long haul flights when passing several time zones. On these long flights it could happen that the FSX time and the computer time drift apart. If you fly online then it is better to have the time synchronized. So it depends on your personal needs whether the time synchronization is active or not.

Tom, currently it's only possible to synchronize the UTC time (computer time) towards to FSX and not the other way round. EFB is using computer time only. I will write this on my internal list but from the today's point of view I can't say whether it will be possible or not. I will try it ...

Hi, Maybe you could send me the logfiles for further investigations? If the DataProvider crashes it can no longer send a visual warning because it has been crashed - as the description says. The DisplayUnit (or better the EFB architecture) is not designed in a way that the DisplayUnit is observing the DataProvider. The DisplayUnit only recognizes that the TCP/IP connection has been lost but it doesn't know why the DataProvider is no longer available because the only way of getting information is by the network (which then is not available).

Robert, Does it happen when you press on the OK-button on the settings dialog, or already just after selecting the shared folder? Could you please send me all the logfiles to support@aivlasoft.com? Thanks.

Ralf, there is a known bug if you close the DisplayUnit when it is minimized to the task bar (right click on the taskbar icon, then select "close window", or if it has been closed by the TaskManager or anything else). The only thing that can help in this situation is to delete the settings file which can be found as follows: C:\Users\[username]\Documents\AivlaSoft\EFB\Settings\DisplayUnitSettings.bin Please make sure that the DisplayUnit is not running when deleting the file! After this file has been deleted the DisplayUnit starts as it were for the first time and you must select your preferred settings again. Sorry for the inconvenience, it will be fixed with version 1.0.4.

Dadriel, your question reminds me of the following joke: LH 741: Tower, give me a rough time check. Tower: It's Tuesday, sir. The SP4 will coming soon. It has been sent to our beta testers and if nothing unexpected happens it will be released as soon as possible.

Dadriel, sorry for the inconvenience but it seems that this is a known bug. Should be fixed with the upcoming version 1.0.4. Thanks for reporting in detail.

Björn, today I had the opportunity to check the German Airports 2 scenery on a colleagues computer. The conclusion due to this test is that it is really a bug what you reported. I'm sorry for the inconvenience, but with the next program version this bug will be fixed. The next version is coming soon. Thanks for your patience and for the report. @ Lars: Thanks for your help, just one thing that you mentioned: After a scenery update the indexes that have been saved by the DataProvider will no longer correspond to the bgl-files. Therefore the DataProvider sooner or later will crash if you don't update.

Hi, I just changed the options as follows: Is that all right with you?

ontheair, seems to be a bug but is fixed with version 1.0.4.

Rouslan, I assume that you mean the feature of the FSX flight planer where you will be asked whether you want to place your aircraft at the origin airport from the current flight plan? The current flight plan which will be created by FSX does not include a runway position yet and therefore (if you select "Yes" from the above mentioned dialog) the plane will be placed to the airport reference point (ARP). I'm still working on a solution for this.

ontheair, sorry, no workaround possible. You must wait for the update (coming soon).

Lars, thanks a lot for this great picture. It seems to be a "very interesting" approach now. Did you send the updated LPMA.txt data to Navigraph?

Hi ontheair, seems to be a bug, I can reproduce it on my computer. I will check this later today and will post - if possible - a workaround. Thanks for reporting this.

Günter, I'm afraid that I can't be helpful concerning the Mustang "bug" because I don't have it on my machine, so testing and finding a solution can't be done. Sorry. Did you uncheck the option "Create FSX flightplan ..." from the DataProviders settings (see "Folders" tab)?

ontheair, there IS an uninstaller included in the setup but it is not placed as a menu item in the Windows menu. I assume that Win7 is running on your computer? Open the "Control Panel", then "Uninstall a program". Now you should see a list of all installed programs on your computer. Select "AivlaSoft EFB" and then "Uninstall". This will use the EFB uninstaller. Uninstall will NOT destroy the license file. I recommended to save the license file because you told about your intentions to rearrange your hard disk and/or partitions. The uninstaller will not remove any file which is your own property, like user data or the license file. Hope this helps.

Björn, are you running the Airac-cycle 0911 or another one? Could you please send me the following items to support@aivlasoft.com? a) screenshot of the AirportInformation dialog (Blue button "EDDK Approach", then "Airport Information" (select the "Runways tab"). screenshot of the ProcedureSelector dialog (Blue button "EDDK Approach", then "Select Approach", then press on "24" c) all the logfiles, which can be found as follows: Windows-Start-Menu > All Programs > AivlaSoft > EFB > Logfiles If you installed the DataProvider and the DisplayUnit on different computers, please send me the logfiles from both computers.

@ Rene: I'm not a Buendner, but I spent a lot of time in my life in that area. Therefore the company name consists of the word "Aivla" which means "Eagle" in Rhaeto-Romanic. Rhaeto-romanic is one of the four official languages in Switzerland (besides Italian, French, and German). Have a great time in Mexico.

ontheair, all our beta-testers have been flying hundreds of approaches into several airports with different types of aircrafts but none of them has ever crashed or complained about missing data (to my knowledge). If you talking about "correct" approaches, then I would like to remember that we are not flying in a correct (means "real") world and nothing is perfect. I know that MSA - apart from other things - is an important information when flying an approach and - believe me - I'm personally interested in getting more detailed charts, but we have to wait for this data. Every AIRAC-cycle costs approx. 2 EUR which is not for free but it's a very favorable price. I can imagine that an AIRAC-cycle in real-life (with much more information) costs much more. I think that we never should forget that our beloved hobby takes place in a simulated world which has its advantages and - of course - its disadvantages. So let's find a good balance between simulation, imagination and reality.

ontheair, I would recommend the following procedure: 1) Make a backup of the "UserData" folder to save your aircrafts, checklists, routes, flightlogs, and library contents. The folder can be found as follows: Windows 7 / Vista: C:\Users\[username]\Documents\AivlaSoft\EFB\UserData Windows XP: C:\Documents and Settings\[username]\My Documents\AivlaSoft\EFB\UserData 2) Make a backup of your personal license file (AivlaSoft_Efb_V1.dlsc) which can be found as follows: Windows 7 / Vista: C:\Users\[username]\AppData\Local\AivlaSoft\EFB\ Windows XP: C:\Documents and Settings\[username]\Local Settings\Application Data\AivlaSoft\EFB 3) Reorganize your hard disk(s), partitions, but don't delete your backups 4) Re-install your EFB software using the latest version (or ServicePack, if you installed from CD). The latest version can be downloaded from the AivlaSoft website http://www.aivlasoft.com/download/index.html 5) Restore the license file to its origin folder (which must be created manually before) 6) Run "DataProvider" 7) Run "DisplayUnit"

Björn, EFB gets the ILS data from FSX and Navigraph. FSX provides all the earthbound data whereas Navigraph provides the procedure data. If FSX has ILS data and Navigraph doesn't list an appropriate ILS procedure then EFB doesn't show the ILS in its procedure selector. The other way round, if Navdata has an ILS procedure but FSX doesn't have an appropriate ILS navaid, EFB also doesn't show the ILS procedure. As you described you already entered the additional lines in the "Runways.txt" which should be as follows: EDDK 14L 14L EDDK 32R 32R EDDK 07 06 EDDK 25 24 EDDK 14R 14R EDDK 32L 32L Due to performance reasons EFB will hold every loaded airport in its internal cache until either EFB will be restarted or - if the option "Always request airport data" is checked - the airport will be requested again. Did you set this option? Did you restart EFB since the runways have been added?

Harry, the folder on the DataProvider computer is as follows: Windows7 / Vista C:\Users\[username]\AppData\Local\AivlaSoft\EFB\AivlaSoft.Efb.DataProvider WinXP C:\Documents and Settings\[username]\Local Settings\Application Data\AivlaSoft\EFB\AivlaSoft.Efb.DataProvider This folder must be shared before it can be accessed from the DisplayUnit's computer. Hope this helps.

Rene, you certainly must be an Appenzeller, with this name . Any relations to the famous "Alder-Buebe"? Sorry, for all who are not familiar with the Swiss "internal affairs". We not only have famous Banks , we also have some really good musicians. One of the famous bands here in Switzerland are the "Alder Buebe" (means "Alder Boys"). Re EFB: if the connection between the DisplayUnit and the DataProvider has been established and FSX is running (the status view must show a green "LED") then you only have to activate the "moving map" button, as already explained by GG_Flyer.

Martin, thanks for sending me this flightplan. This flightplan is an FS9 flightplan (not a real FSX data format) and therefore it cannot be read by EFB. See also: viewtopic.php?f=5&t=3 Workaround: The workaround to use FS9 flight plans in EFB is as follows: - open flightplan in FSX flight planner - save the loaded flight plan by the FSX flight planner to get a valid XML file - open the flightplan in EFB