aivlasoft

Please comply with the forum rules especially 2.1. Thanks.

There is no mobile app available.

As you might have overseen, EFB is a .NET-application which only runs outside of the MSFS process.

It is not yet defined. We are still testing.

First of all, please do not send emails to support and at the same time you start a new thread at the forum. Just one of them, please. thanks. As I already replied to your email, it looks that some required folders of the simulator installation are missing. Try to uninstall the simulator and then re-install it.

Yes, it should. You can find the required name in the Server's log file (see next screenshot as an example). Just add the name which is displayed to the already listed names in the respective profile.

Obviously there are two different issues discussed in this thread. First, the name of the currently loaded aircraft in MSFS, and second, the names of AI aircraft provided by MSFS. Regarding issue #1, I have the latest version of Fenix' A320 running (v1.0.6.146) and FSUIPC7 v7.3.19 is installed. On the next screenshots you can see that the ICAO type designator is properly detected by EFB: Regarding issue #2 I can only say that the malformed names are the names of AI traffic and not the name of the own ship. Although these names are created beyond the scope of EFB, I have implemented some 'filtering code' which is trying to extract the ICAO type designator from these malformed names. It will be available with next update which is planned to be released soon. Until then I don't see a workaround except to pause the AI generation by the aforementioned third party tools.

What you experience is most probably an old story which has its origin in the BGL data structure. I had to search for this old thread where it was discussed some years ago: https://forum.aivlasoft.com/topic/2956-missing-runway-11-29-lfbd-efbv2 And here is the answer to all of this: https://forum.aivlasoft.com/topic/2956-missing-runway-11-29-lfbd-efbv2/?do=findComment&comment=18017

@dawgfan58 Did you read my post above, regarding file versions?

Negativ. As you might have overseen in the screenshots above, the cryptic names do not start with "TT:". @all: Could you please let us know the versions of the FENIX-Airbus, and also from FSUIPC7. Thanks.

I will add an exporter for MSFS with next update.

I will try to implement a fix with next EFB update. To be honest, slowly I'm getting upset because of these ongoing inconsistencies with each update of MSFS.

Thanks for the screenshots. It seems that this is a Fenix issue, not EFB. All other aircraft provide a meaningful text in the model column.

I can't reproduce it here. AI traffic, generated by MSFS, appears with correct aircraft types (EFB v2.3.136, MSFS v1.31.22.0). Are you running a third-party-tool which generates traffic? Are you running the latest version of EFB Server and Client? Have you already looked at the Server's traffic monitor? Maybe you could assign another field number for the type?

The demo is fully functional, except from the 30-days limit, so you should receive any updates. According to the change log long procedure names are allowed since v2.3.134. I also did a test to verify it again. So either your installation is not up to date, or there is another issue than the OP has reported.

The file 'A:\Prepar3D v5\scenery\base\scenery\magdec.bgl' is part of the P3Dv5 installation. If this file cannot be found then the file 'magvar.bin' cannot be created by the DbBuilder. Therefore the second error is just a subsequent error. Check your P3D installation.

Did you update both, Client and Server to the latest version 2.3.136 ?

It will be fixed with next update.

Hi Ray, it would be possible as long as a waypoint's coordinate has no minutes. But as soon as a waypoint reads like 1540N06022W the short 'five character' format will not work.

It's obviously a design problem of MSFS and unfortunately the 'registry fix' does not help. To my knowledge the only remedy for this is to re-install MSFS to a location which has a very short path (e.g. C:\MSFS).

Hi Jeff, thanks for this information. I doubt that we can do much in this regard. As you already mentioned, it's the weather data which is downloaded from NOAA. When I have a look in this file I can clearly see that there are airports which provide METAR very close to real time, and there are airports which have a delay more than 1 hour.

Checklists must be assigned to a certain aircraft profile. Please see the Client manual "5 EN Client.pdf", chapter 12.2.5 "Checklists"

Thanks for uploading the support files. For which type of simulator do you want to create a database? MSFS (Steam) or P3Dv5?

Could you please provide the support file from the Server. Thanks.

EFB reads the airport data from MSFS and creates the airport's ground layout based on this data. It's right that the navdata (SID, STAR, Approach) is depicted based on either Aerosoft NavDataPro (Lufthansa LIDO), or Navigraph FMS data (Jeppesen). EFB does not read the NavBlue navdata which is part of MSFS. This is because NavBlue navdata is not equally complete as either Lufthansa LIDO or Jeppesen, and MSFS does not update it regularly every 28 days like the r/w AIRAC cycles. EFB is provided with a old AIRAC cycle from Aerosoft NavDataPro and from Navigraph FMS data, in order to allow a fully functional program. Whether you need the regular updates or not, depends on your personal preferences. From a technical point of view it is not necessary, you can use EFB with the old, outdated AIRAC cycles which come with the installer. Yes, unfortunately this is true. EDIT: See next post below. As mentioned above, EFB does not consider the NavBlue data from MSFS. Yes, but the navdata which comes with the installer is outdated. Please also read the MSFS limitations here: https://www.aivlasoft.com/msfs-limitations.html