aivlasoft

Hi Marconi, I did some quick tests and I think that you're right, the sentence "..but not remove the selected procedure from the viewer." is not correct. Pressing the "cancel" button removes the procedure from the viewer.

Hi, as per the forum rules (4), please sign your posts with your real first name. Thanks. The only way to get rid of this exception message is to delete the settings file. 1) exit DisplayUnit (if running) 2) Locate the file C:\Users\[username]\Documents\AivlaSoft\EFB\Settings\DisplayUnit_UserSettings.bin 3) Delete the file 4) Start the DisplayUnit 5) Enter your preferred settings

Ivan, thank you for your kind words on EFB. Much appreciated! According to the license agreement (Point 3.1) it is not allowed.

Marconi, I'm not aware of that the frequencies are NOT shown in the flight log (Only waypoints that are type of VOR or NDB have a frequency shown in that column). Can you provide a screenshot where I can see the missing frequencies?

Thanks to you too, Marconi.

Marconi, it's already implemented in version 2.0. You will like it

Hi Andy, thank you very much for your help. I just updated the forum rules and I hope that this will help all the members who have not yet created their signature.

Ivan, - do you experience any messages on the DataProvider's window when selecting LEMD as your airport? - did you make any changes to your runways.txt file? - did you already read this from the FAQs: viewtopic.php?f=3&t=1260

Hi David, Please read this post: viewtopic.php?f=5&t=1177

Henk, You "have" to wait for version 2.

Hi David, one must distinguish between 'saving' a route and 'activating' a route. If you save a route, the current EFB route will be saved to the folder of each of the currently selected flight plan handlers. Saving does not affect the FSX GPS engine. Whatever you are doing with these saved plans it's up to you. There is no further activity taken by EFB. If you activate a route, the current route (including procedure waypoints) will be saved as an FSX flight plan and this flight plan will be loaded into the GPS engine. The flight plan itself gets the generic name "EFB_current_garmin.pln". Loading this flight plan into the GPS engine allows the auto pilot (if properly set) to fly along the route. Note: Complex aircraft like the PMDG 737 NGX have their own auto pilot functionality and therefore they will not follow the FSX GPS flight plan. As per the error message, I just did a search on the internet and found this answer: http://answers.microsoft.com/en-us/wind ... 73c699e505 Hope this helps.

Patric, thanks for your inquiry. Development for version 1.x has been stopped many months ago because I'm working on version 2.0. I will have a look at this program (I don't know it yet) and if technically possible will add it on the 'to-do-list' for version 2.

Hi Tim, you don't have to run "the Eye", you only have to have the data files of "the Eye" available. On the download page you can download these files, then copy/paste them into a directory at your discretion. In the DisplayUnit settings dialog, go to the online tab and reference the corresponding folder.

Tim, thanks for the good words on EFB. Of course, EFB also shows the traffic of IVAO. What exactly do you miss? Have you already checked the settings and carefully read the manuals?

No problem, David. I'm glad you could have sorted out.

David, thanks for the update. Will have a look at this.

Marty, you cannot hide it completely, but you can configure the position of the toolbar and which buttons are available. Please see the "Installation and Configuration manual", section 3, page 19.

Hi Marty, yes, you're right. Except from the flight plan and the COM frequencies, EFB doesn't set any values in FSX. EFB is only reading and showing data.

Hi Marty, I'm not sure what you exactly mean with "how to setup the gradual arrival altitudes". From my point of view you don't have to set the altitudes. They will be read from the current procedure data. The descent angle is taken from the 'aircraft' (usually this is a 3.5° angle above 10'000 feet and 3.0° below 10'000 feet). Using these two items, EFB calculates the required descent rate to reach the next altitude constraint. Maybe you are still confused

Hi Dirk, According to the forum rules, I would like to encourage you to use the search function. Your question has been discussed already and not too long ago. I did the search for you: search.php?keywords=Johannesburg ... or with the ICAO identifier search.php?keywords=FAJS

Henk, this is very kind of you. Thanks a lot.

Richard, this seems to be an AIRAC releated error message. Which cycle are you using? In the past there was a version of an AIRAC cycle with a lot of problems. But Navigraph fixed it really fast.

David, can you see traffic with the 'AI aircraft monitor' (starting from the DataProvider's menu)?

Pete, thanks for posting the event log entries. Unfortunately they don't tell me what's the problem. Sorry. Some time ago I stumbled over these three links, maybe they can help a bit? http://blogs.msdn.com/b/astebner/archiv ... 04493.aspx http://blogs.msdn.com/b/astebner/archiv ... 99004.aspx http://blogs.msdn.com/b/astebner/archiv ... 79928.aspx

An updated version of the ProSim737 flight plan handler is available for download. The updated version only adds a new route if the routing itself has changed. Details can be read here: viewtopic.php?f=5&t=1292 How to replace the flight plan handler? Please follow the instructions below: 1) Download the flight plan handler to a temporary folder and unzip the file (download link is below). 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.ProSim737.dll" in that folder with the unzipped file (see step 1). 5) Start DisplayUnit. [attachment=0]AivlaSoft.FlightplanHandlers.ProSim737.dll.zip[/attachment]