aivlasoft

Hi Ken, thanks very much for reporting back. I'm glad to see it works as it should.

Hi Ray, the shaded area is just the vertical view of the glideslope. It has nothing to do with a distance where you have to let down the gear.

I have checked the server and it is working properly. Please check your local security settings and try again. Thanks.

Hi Ray, although I have an idea of what you might talking about, could you please upload a screenshot so we can have a look at what you mean?

Hi Ken If the traffic is disappearing as soon as your aircraft is airborne then I assume it has to do with the map options of the world map. Ground map has different (better said, individual) settings and therefore it might be that traffic is visible on the ground chart but not on the world map. Please check the traffic options on the world map. If the Client window's width is less than approx. 1400 pixels, the map options get compressed. Then the traffic options are behind the TFC button.

Please create a support file and upload it here, thanks.

This might be a result of the automatic assigning of simulator runways to AIRAC runways. You can check this in the file 'runwayMappings_P3Dv5-NG.txt', which is located in 'C:\Users\<username>\Documents\AivlaSoft\EFB2\Server\Logfiles'. To make a temporary fixed assignment you can add such in the DataBuilder's "Enhance / Update Runways" tab. For details please see the manual "4 EN Database.pdf", chapter 2.5. Do not forget to rebuild the database after adding a fixed assignment, and also do not forget to remove it whenever the resurfacing in r/w is done.

If 04C/22C is a temporary renaming of the runway identifiers in the AIRAC cycle, then EFB cannot find the relevant SIDs, STARs and Approaches for a certain runway because internally (in the underlying BGL-file) it is still having the identifiers 04/22. Due to several reasons the runway identifiers in the AIRAC cycle data must match the runway identifiers of the MSFS airport scenery file. As long as there is a mismatch between them, procedures cannot be assigned to the proper runway.

I do not have plans to release it as freeware, nor have I plans to sell it again because In both cases I would have to maintain the source code to keep it running in the future but I don't have a P3D installation and license anymore.

Bill, Windows paths are restricted to a total length of <260 characters. Obviously, the developers of MSFS 2020 were not aware of this limitation. When creating add-ons, such long path names are even suggested. This may work for flat hierarchies, but for deeply nested paths the total number of characters then exceeds the allowed maximum length, e.g. C:\Users\wmccr\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\official\onestore\microsoft-aircraft-pilatus-pc6-g950-wheels-livery-xbox-aviators\SimObjects\Airplanes\Microsoft_Pilatus_PC6_G950_Wheels_Livery_Xbox_Aviators\texture.aviators EFB development is based on the Microsoft .Net framework and is using many of the built-in functions/methods which are provided by this framework. When the DataBuilder is scanning the files and folders, it is one of these built-in functions which is throwing the following exception: 'The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.' Not EFB is complaining, it's the Microsoft .Net framework function. In other words, when such an exception occurs EFB Databuilder cannot read through the relevant directory and therefore some important information might be missing to build the database properly. I know that there is a possibility to override the limitation of <260 by changing a registry key (or a policy), but I do not recommend such because I don't know whether this might have some unwanted side effects at other places in Windows. Therefore from my point of view it is the better way (more robust) to install MSFS to a shortest possible path as mentioned in my earlier post above. At least it would save all the characters at the beginning (e.g. C:\Users\wmccr\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages). But even then no one can guarantee that it works forever. As long as such path names are suggested it can happen again and again.

Hi Bill, it's still the problem with the too long paths. The only remedy for this is to uninstall MSFS and then reinstall it to a 'shortest path as possible', e.g. "C:\MSFS" or similar.

I guess this was done unintentionally because the default path points to the 'MyDocuments' folder and this folder might be synchronized with OneDrive, depending of whether the OneDrive service is activated or not. Yes, you can uninstall and then reinstall EFB to fix it. When doing the new installation you will be asked where to allocate the data directory. Select a path which is not synchronized with OneDrive.

Hi Bill there are two issues logged in the file: Too long paths. EFB data folder is located on a path which is synchronized with OneDrive. Please read these two posts: https://forum.aivlasoft.com/topic/7100-db-build-after-update-to-135-pathfilename-too-long/ https://forum.aivlasoft.com/topic/2951-win10-onedrive-cloud/

Hi Ulrich, There are currently no plans to implement such a functionality. As already stated in the manuals, the creation of contour lines is a very time-consuming process, therefore an extension of this dataset is currently not planned. Please keep in mind, even if the coverage is "only" 50% of the globe, the percentage is much higher in the regions where most flights in flight simulators take place.

Not resolving means that the IP-address for the domain 'faa.gov' and its subdomain 'notams' could not be resolved from a DNS server. I guess that this is just a temporary issue which is far beyond of our scope. Just check on your computer whether the EFB Server settings (C:\Users\<username>\Documents\AivlaSoft\EFB2\Server\Settings\serverSettings.txt) are properly set for the NAT download page which is as follows: https://www.notams.faa.gov/common/nat.html

See the manual "6 DE Flugplan.pdf", chapter 2.3 "Flugplanung über Uplink"

Hi Claus, according to the forum rules, please write any further post in English, thanks. The so called 'ATC ribbon' lists all active stations along your current route. If there is no ATC listed, then either no route was created, or along this route no ATC is active.

Hi Wolfgang all available shortcuts are listed in the Client settings dialog. As to my knowledge there is no shortcut for the DONE button.

Hi Wolfgang Press "Add Sibling", or "Add Child", depending on which kind of a new line shall be added. Make sure you have selected the proper element from which the "sibling" or "child" will be determined. There is no limitation of the line count and there are no basic settings to be changed, just press the above mentioned buttons and make sure the entire dialog is visible on your screen. Please also read the manual "5 DE Client.pdf", chapter 12.4 "Checklisten Editor".

EFB detects the closest airport based on the distance between your aircraft and the ARP of an airport. As far as I know ZMIA is not a real or valid airport and therefore I don't know the purpose of this 'shadow' airport which must be located very close to KMIA. Maybe the developer of the scenery can help. The only remedy which EFB can offer is described in this post: https://forum.aivlasoft.com/topic/6506-error-message-ac-is-not-located-at-nearest-suitable-airport-switch-profile-filter-off/?do=findComment&comment=29845

Did you select the map option ACFT from the map option buttons on the bottom edge of the map?

Today we released the new update 2.3 (build #136) which contains the following improvements: X-Plane 11/12: Support for 8.33 kHz COM frequencies MSFS: Aircraft type 'TT:AIRCRAFT.UI_MODEL' converted into meaningful name

Hi Erdal, please do not use 'LSZH' again as the title for this thread because it has absolutely nothing to do with what you report. A more meaningful name would be helpful also to other users reading this forum. Thanks. The above error message might happen if the flight plan in SimBrief was created with another AIRAC cycle than the currently active cycle.

Unfortunately the time period where the issue most probably happened, is not covered in the Client's logfile. Logfile #2 ends at 2022-08-11 17:21:20.818 while the next logfile #1 starts at 2022-11-28 18:56:05.348 which is more than 3 months later. Are you running any 'auto-backup' software or any other utility which might have replaced some of the logfiles on this computer?

Thanks for the files. Unfortunately there is no time period logged where both computers are running simultaneously so I cannot say why the Client is not connecting. Another issue which I see is that you have the Client's data folder at a location which is synchronized with OneDrive. According to the installation manual, please do not select a location which is synchronized with OneDrive or any other cloud service. Please see also here: https://forum.aivlasoft.com/topic/2951-win10-onedrive-cloud/ It is recommended to uninstall the Client using the uninstaller. Then download the latest complete installer, run the installation and when being asked for the data folder, select a location which is NOT synchronized with OneDrive.