lonewulf47

Hi ??? (please observe the forum rules) Did you set the path for AS-XP in the Server Settings dialogue?

Nope, you don't need to share the *.acf file 😃. The only thing we need to know s the ICAO-Code used for this A/C model, which is obviously B737. That's all. We will add it to our default profile collection for the B737-700 and I'm sure you have added it already to your B737-700 profile by using the Profile Editor. Don't forget to restart the Client after a change within the profiles.

Hi Kyle, Please check the Manual "5 EN Client" page 94, the Remark about X-Plane. This is common behaviour if the respective ICAO-Code is not contained in the Profile in question. I don't have the Ultimate B737-700. Maybe you could retrieve the Code from the *.acf file and publis here? So we could add it to the present set of profiles.

Hi Andrea, That sounds strange. As you can see in the attached screenshot, there are no such problems with both FSX/P3D and X-Plane. Both show all STARs correctly.This is with the newest Navdatapro Database Cycle 1905 .

Thanks Alex, for the update. Great to hear that it works now.

Thanks Alex, It seems that you did not update both Server and Client the same way. You obviously downloaded the Full Client Installer and updated the Server. This way two different TCP Port numbers are used which makes a connection of course impossible. What I see from the Support Files: Server TCP Port Number: 51748 Client TCP Port Number: 57892 We have changed the Port Numbers with the latest update for several reasons. This implies however that either BOTH Server and Client are UPDATED (this will not change the TCP Port Number) or BOTH Server and Client are NEWLY INSTALLED (this will change the TCP Port Number). Using Update on one component and Full Install on the other just results in what you have got. Easy remedy: Close both Server and Client. Start the server, go to the tab Settings/System and change the TCP Port Number to 57892. Then restart the Server and the Client and you should be fine.

Hi Alex, Please post the Support Files.

Plase submit a set of Support Files.

Hi ??? (please observe the forum rules) Pleache check your issue against my answer in this thread: https://forum.aivlasoft.com/topic/3555-update-21/

Yes, Update to 2.1 is fully compatible with P3D V4.5. Works flawlessly on my computer. Please confirm, that you have updated both Server and Client in the same manner (e.g. for both automatic update, or for both new installer). Please check that both Server and Client use the same TCP Port Number. See below:

Derek, No, you're mixing up two things. What you describe is the IP-Address of the Server, in case you use the Client on a Network. The TCP port number is something different. It is accessible through the Settings/System dialog. But still, whether working in a network configuration or not, the TCP port number must be equal on both Server and Client(s).

Me neither...

There is no need to re-install everythig from scratch. Just make sure that ALL Servers and the Client use the same TCP Port Number.

Do you refer to the checklists in the \checklist folder or to the entries in the respective profile? You might note that with this #106 update two the contents of \profiles and \minima in the Client's document path have been updated and the former (possibly customized) content copied into two new folders \profiles.bak and \minima.bak.

It seems that the unzipping process on the Client is not running properly. Did you try to run the Client as Admin? Although not expressively necessary, it might help in some cases.

Hi Edwin, Did you run the normal updates on your entire system or did you use the Installer on one of your Client Systems? Check on both Server and Client that they use the same TCP Port Number. You can find the TCP Port Number under Settings/System on both Server and Client. Make sure all show the same Port Number. If you need to change the TCP Port Number make sure you restart The Server and all Clients.

No, the input window marked in yellow should point to your X-Plane folder ! Change it to your X-Plane folder (apparently G:\X-Plane) and continue. The yellow markig points to the fact that the selected folder is not a valid folder for X-Plane ! That's why you don't have the "next" button activated. I does not need to find any AIRAC folder in X-Plane. Where do you have this information from??

Why do you point to the installation folder of EFB when the system is asking you for the installation folder of X-Plane ??? In the picture above the line below "installation folder" is asking for the installation folder of X-Plane !

Hi Michael, No need to worry. Have a closer look at the file structure within the documents folders of the client (default path: "C:\Users\User\Documents\AivlaSoft\EFB2\Client"). You will notice that there are two new folders \profiles.bak and \Minima.bak. They contain all data from the previous install. So all your customized files are still available in those folders. Not sure about the checklist folder. This one should remain untouched. So if you restore a profile from the mentioned Profiles.bak folder, the Checklists should still be attached to your customized profile.

Well, yes, that might be a good idea. EFB will only be able to depict procedures if they match with the real world RWYs. To check this in EFB you may use the CTRL+ALT+R combo to show ARINC (Real World) RWY layout overlay.

Hi Ray, Pretty simple. Whatever airport GBL you use, EFB is trying to assing the proper identifiers to a RWY. In this case - although RW28 only exists in your airport BGL, - there are NO procedures for RWY28, but only for RWY28R at this position. That's why WFB changes the identifier to 28R which is the proper identifier for this particular RWY, no matter whether the remaining RWYs 28C and 28L exist in your airport GBL. The procedures are for RWY28R. See KORD airport diagram here: https://aeronav.faa.gov/d-tpp/1904/00166ad.pdf#nameddest=(ORD)

Hello ??? 1. Please follow the forum rules 2. Prease poduce a full set of support files and post it here

Hello ??? 1. Please follow the forum rules 2. Have you tried to correct the issues creating a warning? (1 of a wrong access path and 3 of inadequate airport specs)? 3. Without at least the server logfile no error tracing on the server's side is possible. I would recommend to produce a full set of support files and post it here

Torsten, As I wrote earlier in this thread, our initial goal was to depict the entire taxiway system as completely as possible - as we do in FSX/P3D. Unfortunately this goal cannot be achieved by the "traditional" means in X-Plane i.e. all available surfaces and lines as the information derived from these items is not distincitve enough. At a later stage we will certainly go for the Taxi Routes which in most cases will also provide Taxiway Names and more. However it will not provide the entire Taxiway Network on the airport as the taxi routes are - depending on the designer - not covering all possible Taxi Routings. On the positive side there are already a large number of gateway airports "equipped" with Taxi Routes. Time will tell...😃

EFB is not designed to work on Windows XP!! It requires Windows 7 or higher. See para 1.2.1 of the Installation Manual.