lonewulf47

John, You don't need a new profile. There is a A319 profile available as default. It is however at this stage only being recognized by the CFM variant. Aerosoft decided to use a new *.air file for the IAE variant. Just open the Profile editor and select the A319 profile. In the input field "Airfile name" enter the name of the new *.air file for the IAE variant: "A319IAW". Press "apply", then close the Profile Editor and restart the Client. that's all.

Jürgen, thanks for reporting. Enjoy your EFB v2 ?

Just tried again: Server Downloadtime ~10 sec, Client Downloadtime ~20 sec, nothing abnormal. You might give it another try after clearing your browser cache(s).

Hi nameless???? The greyed-out path is the default path for simulator flightplans and is detected by EFB automatically and not used for Company Routes. Routes created by (e.g.) PFPX are to be saved into C:\Users\<Username>\Documents\AivlaSoft\EFB2\Client\Routes (default installation) or - usinge the uplink feature - directly into C:\Users\<Username>\Documents\AivlaSoft\EFB2\Client\Uplink. For this see the User Guide "6 Flightplan", Chapter "2.3 Flightplan via Uplink"

Randy, I have just temporarily disabled Aerosoft EDDF and rebuilt the database with default EDDF from P3D v4.3. I see ILS on all RWYs 07C, 07R, 25C, 25L. The new (northernmost) RWY 07L/25R is of course missing as it was not available when the stock data were compiled. I have the latest Sors Update intalled, but this has no influence on the default airport layout in APX50140.bgl.

Sorry to hear that you have problems downloading. I just did a test this minute and had no problems at all to download both Server and Client. So far it looks that from our side everything is normal. If the problems are recurring we might need to investigate. It is however difficult to find out what happened, if we are unable to reproduce the problem.

According to the Manual you should start the Server (better also the Client) ALWAYS with full Admin Rights. According to my experience this error typically occurs if the Server is started without full Admin Rights.

FSUIPC is a requirement for EFB v2. It is required to connect to the Simulator. The requirement is also stated in the manuals and Descriptions. The free version of FSUIPC however is sufficient. See also User Guide "1 Installation", Chapter "1.2 Requirements"

Funny question! Where did you point the installation to? Did you create a specific directory before you installed into another than the default path or did you just point to a specific drive? In that case the installation went into the root of that drive. Not a good idea though...?

Gremlins?? ??

Hi "unnamed" (see Forum Rules) Ok, so those are the latest builds. Difficult to say what causes your problem with RouteFinder as I can only confirm that it works normally here. The RouteFinder path is hardcoded. There is nothing changeable. Reinstalling the Client does normally not help but it's anyway still worth a try. In this case I would redonwload the Client from the "Download" section, uninstall the Client and reinstall the fresh download. In fact this doesn't change anything in the install but who finally knows about some unknown Gremlins hovering around...?

No problems here. RouteFinder wroks as designed. What are your Builds# for Server and Client?

Yes, that would actually be the idea behind those exclusions. I'm very much interested in the outcome of your testing!

Bob, Would you be kind enough to provide us with the respective information, which files need to be excluded and how you did it? We might include this in our FAQ section for other users of MyTraffic. Thank you in advance for your kind cooperation!

Hi Bob, Uhmm, that's bad! For obvious reasons we had to exclude a common "scenery" path from these exclusions!. Unfortunately we have no influence on any Add-On developer if they decide to use common path designators (which I would never do, and be it only to distinguish my scenery from any others if not ultimately required by the Sim...) Do the files within this path at last have a common part in the naming, inorder to use the wildcard "*" for an exclusion rule?

Hello Jean-Pierre, Your question is answered here: https://forum.aivlasoft.com/topic/2882-why-is-there-no-flight-plan-export-anymore/

Well, this might be a little misunerstanding. If on a current FlightPlan, you dont need to land to be able to clear the FlightPlan. Just switch to HDG Hold (in case you are on Autopilot), clear the Flightplan (use the Clear FPL Button in the FPL Window) and enter a new FlightpPlan String into the "Copy/Paste" window. You can even enter a complete string in the form of e.g. "LSZR ALAGO Z1 ETAGO HAREM UN851 KEMAD UP605 NOLGO EDDH". It then creates the new FlightPan. The only thing you need to do ist to enter a DCT TO to a resonable point in the new FlightPlan and switch the Autopilot back to NAV mode. Maybe this will ease things a bit?

Bob, as those MyTraffic BGLs are not relevant for EFB v2 display (so it seems), have yo tried to exclude them from being scanned? There is a file "BglSceneryExclude.txt" located at C:\Users\<Username>\Documents\AivlaSoft\EFB2\Server\DbBuilder\Base with a comprehensive description in the file header, how to apply such exclusions. Maybe this could be of better help?

Bob, just for my own understanding: doesn't myTraffic provide their own BGLs to manage AI traffic? At least I read about that recently, but not sure anymore. I myself keep my fingers off any AI traffic tools as this is definitely not my aera of interest, but still information about such programs can be useful.

That's an old problem which is inherent with this type of Simulator we are using. EFB knows of course all correct frequencies (provided you use the actual AIRAC cycle), however you are not able to tune any frequecy which is not listed in any of the scenery BGL's. So the easiest way is of course to change (or if available, update) the respective BGL of the scenery or to use the way you proposed. Nevertheless disabling a BGL is not a recommended method as you dont know what else is contained in the BGL and thus disabled. An updated "AFCAD" BGL from the scenery is always better. BTW Hervé Sors also provides a worldwide (except Europe) ILS update which worked satisfactorily so far, as it is based on the same AIRAC cylce that is used in Sim-Navigation, however I haven't checked it for this specific frequency. Just make sure everyone understands that EFB V2 is not able to change TUNEABLE frequencies. This is excluded by the way FSX-type Simulators are handling Navaids.

You just need to set up everything correctly and you will see every traffic that FSUIPC is able to retrieve from the simulator.

It's included in the most recent Client #76, dated Sept 3, 2018

Just to make it clear: EFB v2 does not "contain" any charts. It DRAWS all required chart in real time using the actual AIRNC data that are present on your installation. By default a set of ARINC data from a certain AIRAC cycle is included. Thus all charts are representing the state of this AIRAC cycle. By updating these data through regular updates - be it from Navigraph or NavDataPro - always the newest data from the actual data cycle are used. Navdata from the Sim (contained in the default BGLs) is not used for procedure drawing, as these data are outdated by decades.

Great to hear that you have sorted it out. Enjoy!

Hi Michael, It's actually all in the books...? Nevertheless in short: Whether vertical profile information is shown or not is dependent on the respective entry in the A/C profile, thus it is aircraft specific. By default, on all "bigger" A/C with usually highly sophisticated FMS/FMCs this option is not activated. The option is to be found in the profile under the "Options" tab, a checkbox for "vertical Guidance". This also invokes the vertical profile indication during descent. You are of course free to activate this function to your liking... See also User Guide "% Client", chapter "8.3 Vertical Guidance".