lonewulf47

Honestly, I have no idea. I fly the A320neo regularly without the effect described by you. However I use he FBW A320neo with flighplans created through SimBrief und inported into both the A320 and EFB. This works flawlessly. Using EFB flight plans in an A/C with FMGX or similar is never a good idea as we do not know how MSFS processes the EFB flight plan (*.pln format) internally.

EFB does not interact with MSFS. If you transfer a route into MSFS it only copies the routing into C:\Users\User\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState for reading by MSFS. No further interaction is taking place.

Sorry, unable to read chinese writing...

Difficult to say. Maybe connection problems? At a similar setup I see an active ATC zone over GB and some active airports in build #131. As for a rollback to a previous version: similar to MSFS there is no rollback possible for EFB.

Thanks for your feedback. Enjoy EFB...😀!

Great to hear. Thanks for feedback!

Hi, This is not due to the new AIRAC Cycle but due to the fact that Asobo/MS have decided to change the datapaths for the default airports in SU9. As we were not informed about such changes, we have to start our own investigation on the what's and whereabouts of these changes. In the meantime we have identifed the problem and an update will be available shortly.

Yes, I have seen that these data are relocated to D:\MFS\Official\OneStore\fs-base-genericairports\scenery. ATM we will have to reprogram access to the default airport database. Update is online now ! Please note that after updating Server and Client a Database Rebuild is mandatory to have full functionality back

Yes, I see the same, but this seems to be a problem with this update. There is no more default scenery in fs-base !! This must be resolved by Asobo/Microsoft ! Apparently all Add-On sceneries still work. Maybe the whole fs-base dfault airport database has been relocated from it's former location. In any case we have no information about that. We need to wait for more information.

See here, last post: https://forum.aivlasoft.com/topic/5280-no-profile-fslabs-a320sl/

Hi George, As for the first part of your question: I have never used the PMDG DC-6 with a Flight Plan, so I can't answer this one as it seems a purely technical question related to the DC-6. When it comes to profiles, I must assume that you are talking of MSFS. This issue has been discussed previously here: https://forum.aivlasoft.com/topic/5207-ms2020-aircraft-profile/#comment-27531

Hello Rolando George, Please follow our Forum Rules, especially item 3.

Well, yes, the you need to find the location of the \community folder in your installation. I can't hlep you on this one. Maybe someone using a Steam Installation can throw in some help. You might also search for the "UserCfg.opt" file by means of a freeware serach tool like Agent Ransack. The last line of this file contains the path to your \community folder.

Not sure what you mean. The altitude restrictions for vertical guidance are usually laid down in the AIRAC procedures and therefore cannot be changed.

Hi Damian, Difficult to say in which way JustFlight updates the taxiways. EFB reads the ground layout from either the default "APXxxxxx.bgl" or the BGL from an installed AddOn. If the default BGLs are updated, then of course EFB ground layout will also reflect the updated taxiways. But please note that an updated taxiway sign alone does not change a ground layout. The change must be incorporated in the respective ground polygon BGL.

Seems to be a small misunderstanding. The path shown should be the path where the \community folder is located. Normally EFB finds this path automatically by looking at the "UserCfg.opt" file. The correct installation path is to be found in the last line of this file. If automatic location of this folder fails, you should try to locate the "UserCfg.opt" file with a search app like "AgentRansack" or similar file and look for the last line in this file. It should read: "InstalledPackagesPath "your installation path"" I'm not familiar with the Steam installation, however AFAIK even for a Steam installation the mentioned file should be in "C:\Users\Username\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache" The fact that the installation folder has a yellow background means that EFB was not able to locate the \community folder in this path.

To be a bit more accurate: Hovering over the station designator (1) shows the controller's name or ID whereas hovering over one of the two small squares (2) on an ATIS frequency shows the whole ATIS. I can however not confirm your observation. In the following example I have selected the ATIS frequency on COM2 and still have the full ATIS message when hovering over the small squares.

I think you mix up two different things. When you mose over an ATIS frequency you will be presented with the ATIS message. Mousing over a "common" controller frequency shows the name of the controller plus his actual time on duty. Lastly more and more controllers are not showing their name anymore but ony their ID Number, but this depends in the controllers personal preference. AFAIK IVAO controllers never show their real name.

Hi William, As you mentioned, it can be found in the Client's "Settings" Menu. Press the Menu Button:

Hi Brian, As a first remedy I would rebuild the database and check again. If still no result please send a set of Support Files to support@aivlasoft.com

Sorry Lukas, That only confirms my opinion. I want to know whether the fs-base directory is present in your "e:\MSFS\Official\OneStore\" path. EFB reads all basic information from fs-base. If it is not present, it cannot read any default information, and that's exactly what is missing.

Lukas, It looks as if the fs-base folder were not present. That's where the default airport layouts are read from. Usually airports bought through marketplace are stored in the OneStore subfolder and have encrypted airport information which cannot be read by EFB. Nevertheless the default ground layouts from fs-base should be decoded. Please check whether the fs-bae folder is available. Other than that I have no idea what could be different with your Beta Installation. I do not hope that MS/Asobo have made major changes in the file system...!?!?! fs-base information is being read under all circumstances, even with add-ons installed. EKCH should have an entry like "E:\MFS\Official\OneStore\fs-base\scenery\0601\APX51120.bgl(#0)Base" in your airport information page.

Did you use the connect version of FSUIPC? (FSUIPC6 is required for P3D 5.3) If no connection to the Simulator is present, the location LSZH is default after an update.

Hi Robert, A quick search in our forum reveals the following thread: https://forum.aivlasoft.com/topic/6013-how-to-put-a-fixed-point-in-fpl/#comment-28990

Hi Robert. Yes, of course this is easily possible. EFB reads all pertinent data from a simulator, be it default or add-on. The way these data are compiled by the sim manufacturer is vastly differing. MSFS airport database is at its present state - although not yet complete - far more extended that e.g. P3D - even v5.3.