aivlasoft

Data transfer between X-Plane and EFB is done via TCP/UDP. If the aircraft symbol in EFB does not follow the position in X-Plane then it might be a network issue (or firewall). Maybe there was an update of X-Plane which altered the network (port) settings? If you could create a support file and upload it here I can have a look in the different files. Maybe there is some information which helps to find the issue.

Thanks for uploading the support files. There is nothing suspicious logged in these files (no errors, no warnings) so I have to assume that the issue must be outside of the scope of EFB. Did you do this manually or did you run the uninstaller? Manually cleaning is never a good idea because it might lead to unforeseeable issues of the installer when it runs next time for an update.

When EFB Client is being closed, all the form states will be saved in the file 'clientSettings.txt' which is located in 'C:\Users\<username>\Documents\AivlaSoft\EFB2\Client\Settings' (default installation). Upon next opening of each of these forms, the previous states (location and size) will be re-applied. Because the monitor setting has changed, the saved states, mainly the locations, will no longer match the new monitor positions. Therefore I suggest to edit the above mentioned file. Close EFB Client if running Open it with a text editor (notepad.exe or similar), scroll down to the section '[FormStates]' and remove all the lines of this section Save the file Start EFB Client Every Client form will now be opened at the default location 0/0 which is the top left corner of the main monitor. Now you can move it to the new position and then close each of these forms. Finally close the Client to make sure the new positions of all the forms will be saved. Hope this helps.

Could you successfully create a database?

The frequencies on the ATC ribbon are provided by the data download from VATSIM. The latest download is always saved in the folder 'Downloads' on the Server's side and can be used for reference. If the active frequencies in this download do not match the requirements of the VATSIM ATC controller, I suggest to ask VATSIM for help.

You first have to select the frequency on the ribbon, then choose whether you want to tune the selected frequency either on COM1 active or standby, or COM2 active or standby.

Sorry, but I cannot see anything on these screenshots because they are completely overcrowded. Could you please provide some screenshots where only the sectors are visible?

As long as the yellow caution 'Simulator' is indicated at the Status panel, there is no connection with MSFS. Zurich is the default airport which is selected after a new installation. From the Server's logfile I cannot see any issue, maybe you could create a 'support file' and upload it here?

Sorry, but this is too less information to provide some help.

Maybe this one from the FAQs will help? https://forum.aivlasoft.com/topic/2949-license-key-lost/

Thanks Ray for this information. I'm not aware of these emails and as to my best knowledge I didn't enable such a feature for this forum because it would make no sense at all. Should you receive further emails please neglect them.

Ray, I don't know what you mean. You don't have to mark the best answer herein, because there is no 'best answer', it's just an answer to your question.

You don't have to change the 'runwayMappings ...' file. This file is kind of a logfile and provides information about the mappings which have been created. You can easily define fixed mappings in the DatabaseBuilder. Please see the DatabaseBuilder's manual for details.

Hi Stas Currently we do not have plans to introduce this functionality in the near future, but we will keep it on our radar and probably reconsider our decision if we get more requests regarding this functionality.

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.