aivlasoft

Andy, what exactly do you understand when you say "further" development. Did you already see that the flight plan handler has been released in the early days of October? viewtopic.php?f=5&t=1423

Hi Maurizio, I just have replaced the file some minutes ago. Could you give it a try again? Thanks.

Mike, what you have quoted is in regard of version 2.0 of EFB. There I have it already implemented. For version 1.x I can only repeat what I have already said " ... I'm currently thinking of a small update which implements support for OpusFSX and FSGRW. Nothing is promised, but it could be. Thanks for understanding." viewtopic.php?f=5&t=1415 You might be right, but please do not forget that I'm a one man show and (also this has been already said many times) I decided to concentrate my resources for the development of version 2 and not for endless updates of version 1.x. So please be patient.

Hi Ashley, as far as I know FSInn observes the directory where FSX flight plans are saved. Usually this is the folder named "Flight simulator X files" below the "MyDocuments" folder. As soon as the latest *.pln file has been changed it takes parts of that data and sends it to VATSIM. This has been discussed in earlier threads already and I don't know whether there is any setting in FSInn to prevent this behavior.

Luke, have a look at this topic (from the FAQ page) viewtopic.php?f=3&t=1260

Hi John, the safe altitudes in EFB are based on NASA SRTM data. Unfortunately they only cover the regions from 56° S to 60° N which does not include Alaska. For version 2.0 I'm using the ASTER/GDEM data which covers the whole world. But also this data is not perfect. I have learned (the hard way) that especially the northern regions are partially very inaccurate and have many hick-ups. Therefore I cannot say or promise whether it will be more accurate in 2.0, but there will be another feature based on that data which is really nice.

Hi Tom, just have a look at the operations manual, section 7, page 35 ...

Hi Ashley, That's interesting, I don't know this function Maybe I don't know my own source code ...

Hi Luke, I just checked the cycle 1310 from both Navigraph and Aerosoft. Both of them contains SIDs and STARs but only Navigraph has approaches too. Could it be that you got an error message concerning runways which could not have been assigned?

Hi, as per the forum rule #4 (see orange box at the top of each page), please sign your posts with your real first name. Thanks. There is no explicit function to export a flight plan to send/forward it to VATSIM. Which function, or which flight plan handler did you use to do so? The easiest way, as far as I know, is to copy/paste the ATS route string which can be taken from the Route Setup page. Although you then have to fill in the remaining fields manually. For version 2.0 it will be possible to export the flight plan to VATSIM via this website: http://www.vatsim.net/fp/

Salut Jean-Louis, the batteries are reloaded at around 80-90% Unregistered version Not required

The online server took too long to reboot after a Windows update. It is up and running again now. Sorry for the interruption.

Andy, there are no STARS available for OTBD in AIRAC cycle 1310. You can easily check this by locating the folder where the navigation data is stored. There you will find a folder named SIDSTARS. Therein search for a file named OTBD. Open the file and scroll down where you will find some SIDs and some approaches, but no STARs. DirectTo is greyed out as long as no connection to FSX is established, or FSX is paused.

Graham, when reading a flight plan, EFB is trying to find a match for each waypoint in the internal database. The "problem" is that often a waypoint name exists not only once around the world but twice or more. Therefore (even if the name of the waypoint matches) EFB also calculates the distance between two identically named waypoints to verify whether it is the same waypoint at the "same" location. But often the position (latitude/longitude) of two waypoints at the "same" location is slightly different, and therefore EFB is using a maximum range within two different positions are treated as "same". From your example I can see that the distance seems to be too close and therefore the waypoint EXMOR (which is part of the SID procedure from NavDataPro) is not treated as the "same" waypoint EXMOR which comes from the MSFX flight planner.

Hi Graham, could you please provide one or two screenshots where I can see it. - At which airport does this happen? - Which AIRAC cycle and - which provider (Aerosoft or Navigraph)? Thanks.

Hi, Did you have a look at the DataProvider machine or the DisplayUnit machine? The plugin folder is located at the DisplayUnit machine.

Problem fixed (configuration issue).

Hi, according to the forum rules, please sign your posts with your real first name. Thanks. It's not easy to say what's the cause of the problem since I don't know your network infrastructure, but maybe there is a trace in the logfiles that can help to figure out where's the problem. a) do you use a wireless or a cable network? (Wireless is known to be a bottleneck sometimes) Could you please send me the logfiles from both computers to support@aivlasoft.com? They can be located as follows: C:\Users\[username]\Documents\AivlaSoft\EFB\Logfiles Concerning the PMDG flight plan folder: Most probably you have FSX installed under C:\Program Files (x86)\Microsoft Games\... and therefore the PMDG flight plan folder is located like this: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\FLIGHTPLANS Since Windows Vista the so called UAC took place in the Windows operating system which has increased security a lot. The "disadvantage" of more security often is less comfort. One of these things is that some folders like (among others) C:\Program Files ... is an area where you need more rights to write into than in other folders. Since not all developers do strictly distinguish between program files and user data, it happens again and again that user data is located somewhere below the folder C:\Program Files. This is also the case for the PMDG flight plans folder as long as FSX is installed into the C:\Program Files folder. In many forums one can read the advice to not install FSX below that folder to prevent the situation describe herein. There are two possibilities now for your situation: a) start EFB DisplayUnit with a right-mouse-click and select "Run as administrator". Then EFB should have sufficient rights to write into that directory. Install FSX and all depending add-ons into another folder or drive. Hope that helps.

Hi Henk, I just added two more lines to my post at the top of this page. The second one is interesting to read as an "answer" to your question.

Pete, I'm sorry, but I'm off too and I currently don't have access to the source code. So I can only guess but I cannot test or verify, and (the important part) I cannot reproduce it because it works here with the exactly same settings. I know that this does not help you now, but you should know that I'm thinking about a small service update which will replace this FTP download by another one which works via http.

Hi Mike, basically development of new features for version 1.x has been stopped quite a long time ago. This is because I must set the priority to work on EFB version 2. Since I have realized that version 2 will take some more time than I had expected, I'm currently thinking of a small update which implements support for OpusFSX and FSGRW. Nothing is promised, but it could be. Thanks for understanding.

Hi Pete, thanks for the excerpt from the logfile. I can see that there were 3 attempts to get weather data for EGCC, which results in 3 different errors. I'm not sure, but most probably are error 2 and 3 only the following errors of error #1. So maybe we should concentrate on #1. All the FTP handling is done by a third party DLL which comes from Chilkat (http://www.chilkatsoft.com/) Number one reads: ------------------------- 11:22:22 Cannot get host by name.. hostname: tgftp.nws.noaa.gov ConnectFailReason: 2 (DNS lookup failed) Failed to connect to FTP server. ------------------------- Does this message makes any sense to you? Maybe something with the configuration on that computer? Error number two reads: ---------------------------- 11:24:16 WindowsError: The process cannot access the file because it is being used by another process. failedToDeleteFilepath: C:\Documents and Settings\Pete\Local Settings\Temp\EGCC.txt DeleteFileError: 0x20 ---------------------------- I guess that the file is still locked because of the first error. Can you confirm this or is it possible to delete the file using Windows Explorer? Error number three reads: ------------------------------ 11:27:58 timeout waiting for connect to complete Connect function failed. SocketError: WSAEWOULDBLOCK The socket would block. For more information see this Chilkat Blog post: http://www.cknotes.com/?p=210 ConnectFailReason: 7 (Connect Rejected (or failed for some other reason)) Failed to connect to FTP server. ------------------------------- To be honest, I don't understand the meaning of this message.

Hi Pete, just a simple question, did you update to the latest version 1.3.10? Because with 1.3.8 I fixed a small but very seldom bug when downloading from NOAA.

Done.

Hi Mike, an aircraft (from the EFB's point of view) is nothing more than a 'configuration preset'. It has nothing to do with the currently selected aircraft in FSX. Apart from the descent angle it is the 'container' for the checklists. This way you can configure these two items for different aircraft types that you usually fly. The descent angle is used to calculate the required rate of descent to the next waypoint which has an altitude restriction. The default values of 3.5° above 10000 feet and 3.0° below 10000 is a good value which suits for almost all Airbus and Boeing aircraft (and of course aircraft from other manufacturers of similar aircraft categories). You can create as many different aircraft types as you like and each of them can hold a set of individual checklists. Hope this helps.