lonewulf47

Wolfgang, Changes are generally not transferred to the A/C. The fact that it worked partially so far is just a coincidence. There is no connection to any A/C's navigation system except for the standard EFB-Flightplan transfer, if the respective checkmark is set in the A/C's profile. For any advanced Flight Management System we recommend to remove the automatic transfer and use both systems in split mode. This is the way it was used also with PMDG or FSL A/C. We have no possibility to transfer a flightplan directly into any advanced FMGC or FMS. I personally use the development version of the FBW bus in exactly this way.

Well, it's absolutely impossible to say what kind of issue is happening there. First thing would be to do a complete reinstall of both EFB Server and Client and then set it up exactly according to the Manuals. If the issue still persists, it is absolutely mandatory to create a set of Support Files. This is the only way we can start evaluating any issues on the Install. It would also be helpful right at the beginning to state the type of simulator and the database(s) used.

What database are you using? Did you properly update the database by running DbBuilder? This all sounds so completely weird as I have NEVER EVER neither seen nor heard of such a strange behviour. BYT; what do you refer to by stating "efb sends me to SAM" ?? EFB is not "sending" you anywhere...

Sorry Lukas, I can't help you on that. In my install the aifile name is properly indicated as mentioned. Have you restarted MSFS AND EFB? Try to start FSUIPC, then EFB and when all is fully loaded, start MSFS.

???

???

Gentlemen, The new profiles for the CRJ700, 900 and 1000 are now available in the "Contribution/Profiles" section. Be advised again, that for the CRJ550 there is no own profile neither possible nor available, as the Airfile Name "crj7" is equal for both. Please also re-download the CRJ700 and 900 Profiles and replace the ones already available in your Client. Make sure to restart EFB after installing the new profiles.

Thank you, Peter, I found more or less the same figures😀. I'll use them for the new profiles.

Hi gentlemen, In the meantime I have conquered myself and installed the CRJ bundle. The following facts regarding profiles have surfaced: There is no profile for the CRJ550 possible, because the airfile name according to the manucafturer is the same as for the CRJ700 -> "crj7". There is no possibility to overcome this. Therefore the MTOW and MLW warnings for the CRJ550 will not be triggered correctly and even with the CRJ550 the Profile for the CRJ700 will be loaded. We will create 3 profiles for the CRJ700, 900 and 1000. They will be published in the respective Forum Section "Contributions", Subsection "Profiles", as soon as the are finished. We have yet to find out whether the Airfile names wil properly work or whether they will need to be amended. This is something that MSFS is not always properly handling. Changes therein are however beyond our possibilities.

Make sure FSUIPC4 is properly endend before starting up MSFS and make sure FSUIPC7 is loading properly. Showing the previous situation is normal as long as the (new) simulator is not connected yet.

Hi Lukas, perhaps you might have a look here: https://forum.aivlasoft.com/topic/5684-profile-for-the-aerosoft-crj-1000/ Peter obviously is seeing the airfile name "crjx" for the new model. Maybe you can contact him and create a suitable profile together?

Hi Lukas, No, not for the time being. MSFS must have returned a wrong AirFile name during start-up. First thing you could do: Check your last ServerLogfile for an entry named "airfile name" (see example below). This should return the proper name for the aircraft loaded at present. Check whether this name is entered in the <AirFiles> section of the requested profile. If not, then enter the name exactly the way it is shown in the ServerLog. Best way to do this is the Profile Editor in the Client.

Hi Damian, Why do you select the database which is already selected? (item 5) You need to tell the DbBuilder WHAT to do: Click the Tab "Update Navdata". This is always the case at each new AIRAC cycle. It then updates ALL databases. See also Manual 4 Database, Chapter 2.4 "Update Navdata"

Hi Brian, Not sure what you mean. If you refer to VISIBILITY, the indeed all DEFAULT values are metric as we don't distinguish between countries when applying DEFAULT minima. ALTITUDES (or HEIGHTS) however are in feet MSL (or feet AGL respectively). AIRPORT SPECIFIC minima are listed in ft, altitude/height in meters(kilometers outside the US. The files containig the respective values are just an additional service and not aleays official values. You can edit them to your liking and furthermore update here after each new AIRAC Cycle. A tutorial is included in the Manuals.

Indeed. The Updates available through Herve Sors will acount for these changes. That's the only possibility to keep the "internal data" of P3D current with the actual AIRAC cycle. I must admit that I was of the impression that Hervé Sors' Navdata Updates would be "daily business" for FSX/P3D users...

I'm sorry, Ray, I wasn't aware that you were still using P3D. In P3D things are a bit different. It is well possible that this VOR is still in P3D, but not in the AIRAC database anymore. In all FSX/P3D-type simulators the navaids are not in an updateable database but in the simulator's scenery. As long as it is tuneable, it will be shown. If my memory still serves me right, it would be greyed out if it were only in the AIRAC-Database but NOT in the Simulator, as it would not be tuneable. This whole thing is not an inconsistency but a direct consequence of the way navigation data are presented in FSX/P3D-type simulators. I have asked Urs to shed some light into the P3D database(s), if necessary. At present I'm a bit out of practice when it comes to P3D as MSFS has taken over pretty dominantly. In MSFS and X-Plane the VOR in question is definitely not showing anymore in EFB.

Ray, I have no idea what you are talking about... With the proper (actual) database NORTEL VOR is not shown in EFB2 (as it is decommessioned, as you mentioned). EFB2 cannot show any data which is not included in the AIRAC update. It has no "own" data... Whatever is in the database is shown. I have no idea as to when this VOR in question was decommissioned.

Ed, Please see manual "4. Database", Chapter 2.2

Did you install with full Admin Rights as per Manual? (rightclick and "run as admin")

Sorry, I have no idea what causes this bug. I have just downloaded and unzipped the installer and all runs normal. I have to call-in the developer to take care of this.

Plese check the editing feature in this forum. Nevertheless your report is not very clear. How did you uninstall? What files did you use for reinstall? Where do the error messages appear?

AivlaSoft EFB ALWAYS needs its own database. No matter whether you use the default (outdated) database supplied upon purchase or a regularly updated database (Navigraph or NavDataPro). It does not work without. This is for EFB. MSFS uses its own database, more or less regularly updated by MSFS updates (next to come with Update 6 next week) or Navigraph, which overrides MSFS Default database. You cannot override EFB database by any simlator's database.

Hi Terblanche, I'll try to answer your questions in the same order: NZQN Final approaches are simply not contained in the database for EFB2, neither in NavDataPro nor in Navigraph. The problem here is the designation convention used. There is e.g. an RNAV Final Approach "y" but not assigned to a specific RWY in the ARINC dataset. Therefore it cannot be assigned to a RWY and is considerd a "circling approach". At a leater stage we still hope that hose will be included in the dataset, but for the time being we have to stand put with the present situation. Generally SID's and STARs are not dependent on the installed Add-On. Only ground layouts are derived from there (if available). Why e.g. KORD does not show any procedures in your installation is unknown to me. In my installation (I use the NavDataPro database for EFB) all procedures are available, however only ONE single SID, the KORD6, which is quite common in the US. All data visible in EFB are derived from the AIRAC Database installed FOR EFB. Some Add-On A/C from Asobo (especially the ones with FMGCs and AFAIK also the FBW A320neo) use the (default) ARINC database from MSFS. This one is to be found in "..\official\OneStore\fs-base-nav" and is updated in irregular intervals. All other A/C also use the (default) ARINC database, AS LONG AS NO NAVIGRAPH database is installed. Installing the latter deactivates the mentioned (default) ARINC Database for A/C with G1000/g3000 and similar navigation systems. Concerning the missing Green Banana there is a known issue with the FBW A320neo which uses a non-standard altitude output. ATM we are not able to display the Green Banana for this A/C. Our means for digging into the secrets of Add-On A/C are somewhat limited, especially when it comes to MSFS A/C...

Hi Bill, The only weights that are checked/observed by EFB2 are to be found under the "cautions" tab, see attached screenshot:

Hi Stephan, To alter existing or create new profiles, please use the Profile Editor as described in manual "5 Client, Chapter 12.2"