aivlasoft

You have to distinguish between 'static' data and 'dynamic' data. 'Static' in this regard means the database which contains information about the airports and navaids, while 'dynamic' data means position and attitude data provided by X-Plane via UDP. Both are required for proper operation. The dynamic data exchange seems to work with XP12 already with EFB 2.3 #134, while the database can only be created after the next EFB update 2.3 #135.

As I already mentioned here, the current EFB version 2.3 #134 does not yet support XP12. To fully support XP12 some code changes must have been done. Please be patient, EFB 2.3 #135 will be released asap after the official release of XP12 (except there will be some last minute changes in XP12 which have to be adapted first in EFB).

Good news, forwarding the flight plan is also working with XP12. It seems that the file format did not change. Let's hope that it will not take too much time until the official release.

As mentioned earlier, here is a first state about the integration of X-Plane 12: Some code changes in the DataBuilder's code were required, because the 'global scenery airports' got a new location. Finally we are able to create a new XP12 database. Also the UDP connection is now working and the Server is receiving the aircraft position and other aircraft data. So far so good. Next we will test are the flight plan features and then we will inform again here. BTW, do not except the new version 2.3. #135 BEFORE X-Plane 12 will be released. EFB does not support 'early access' (aka Beta) versions for obvious reasons. Thanks for reading.

After several tests we came to the finding that something must have changed on Asobo's/MS' side. The waypoint type 'User' seems to no longer be treated the same way as before SU10. One can easily test this as follows: Create a simple flight plan in MSFS, from one airport to any other airport and add one or two user waypoints. This flight plan will now be displayed properly. Then save this flight plan and close MSFS. Now restart MSFS and try to load the flight plan which have been created before. You will see that the airports are still displayed properly while the user waypoints between the airports are now depicted at the Northpole. The legs between the airports will be depicted 'straight upwards' to the Northpole. However, it seems that a flight plan which contains only 'official' waypoints such as airports, navaids and/or fixes, can still be created and forwarded by EFB. Such a flight plan will also be depicted properly in the G1000 NXi from Working Title. As long as MSFS cannot read or interpret the user waypoints it creates itself, there is nothing we can do from our side to remedy the situation.

Maybe the option button "ACFT". These option buttons are depending on the chart type, which means you can have it ON on the ground chart, but OFF on the world map and vice versa.

It seems that it has to do with the recent SU10. We are investigating ...

It seems that it has to do with the recent SU10. We are investigating ... Please see also here: https://forum.aivlasoft.com/topic/6907-efb2-is-not-forwarding-the-flight-plan-to-msfs-on-g1000-equipped-aircraft-after-su10/

Hi Ray, From my point of view there is no need to do some programming because changing the unit of weight is just one item among others when doing flight preparation. According to the region where a flight takes place one has also to change other units like pressure, or the unit of altitude etc. All these changes can be done easily in the Clients settings dialog.

For several reasons EFBv2 will only use waypoints (fixes, navaids) in a flight plan which are part of the currently loaded database. A database (in terms of EFB) is a merge of simulator data and AIRAC-Cycle data.

We have not yet installed X-Plane 12 but we will do so in the near future. As soon as we have tested this new version we will inform on this forum.

Did you select another data folder than the default data folder, when you ran the Client installer?

Thanks for reporting back. I'm glad that it works now.

Try to temporarily deactivate your AntiVirus program. On some devices running Kaspersky AV we have experienced that the update was blocked. If this does not help, you may download the latest full installers as usual from the AivlaSoft website: https://www.aivlasoft.com/download.html

Hi Bill Apart from the Windows-Full-Size-Mode the Client has its own full-size mode, let's call it 'real full-size'. When this mode is active, the window title bar is no longer visible and also the Windows-Taskbar will be hidden. The idea of this mode is to allow the Client to use the entire screen area when running on smaller monitors like notepads etc. This full-size mode can be toggled by double clicking onto the airports name on top of the Client's window.

The ATC ribbon lists all manned ATC stations along your route in the right sequence. Without a route/flightplan there are no ATC stations to display. It's as simple as that.

After several tests we came to the following conclusion: Due to the AI-based recognition of aprons, unfortunately many additional areas are defined as 'apron', which have nothing to do with aviation. This leads to the fact that the database is unnecessarily inflated without providing a benefit in terms of aeronautical requirements. The size of the database is almost twice as large as without the aprons, and therefore the loading time and the time needed to synchronize the database between the server and the client(s) takes much longer. So overall, there are too many disadvantages. Here are just two examples. Please see the comments below the images. Airport Megève (LFHM): The entire road and parking space on the south/east/north side of the airport is defined as 'apron'. The green areas are also 'apron'. Airport Gibraltar (LXGB): Many areas around the airport are defined as 'apron'. An 'interesting' one can be seen on the north-west side of the airport. It is the pier of the ship harbor. The different surface materials have been intentionally colored this way. Dark grey means 'asphalt', Light grey means 'concrete', Blue means 'water', Green means 'grass', Red means 'unknown', Yellow means 'other', such as bituminous, sand, clay, etc. All of these areas are defined as 'apron'.

This is the error which is causing all the problems. Het opgegeven pad, de bestandsnaam of beide zijn te lang. De volledig gekwalificeerde bestandsnaam moet minder dan 260 tekens bevatten en de mapnaam minder dan 248 tekens. (English) Either the specified directory name, or the filename, or both are too long. The length of a fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. Due to the fact that the default installation path of MSFS 2020 is given as follows ... c:\users\<username>\appdata\local\packages\microsoft.flightsimulator_8wekyb3d8bbwe\localcache\packages ... the absolute path of an add-on might become too long, depending on the relative path names of the add-on. Even some of the folder names of MSFS itself become too long. e.g. C:\Users\<username>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\community\aig-aitraffic-oci-beta\SimObjects\Airplanes\AIGAIM_HTAI_C208B_SuperCargomaster\model.IRO-CSA Air_Old Titles Black Leading Edge Dark Cargo Pod This can only be solved by a clean new installation of MSFS into a separate folder which has a short as possible name, e.g. E:\MSFS

These links seem to be broken. At least on my machine I cannot see them. But anyway, I will have a look at this.

Currently EFB can only depict the FIR boundaries of either VATSIM or IVAO (depending whether they are active or not). Unfortunately I don't know where to get a file which provides the boundaries of the r/w FIR boundaries as x/y-values (Lat/Long coordinates). Maybe you know of such a source?

It cannot find the path to the so called 'generic airports'. Therefore the database cannot be built. I don't have an installation of the steam-version of MSFS so I'm unfortunately unable to advise whether the proposed path 'C:\Users\<username>\AppData\Roaming\Microsoft Flight Simulator\Packages\official\steam\fs-base-genericairports' is the correct path to the generic airports. Maybe there are other users having a steam version on the computer and can help?

Sorry for the inconvenience. Should work again in a few hours. Try it again tomorrow.

If the aircraft begins to start turning backwards to the first waypoint of the flight plan when you enter your flight plan in the EFB, then from my point of view, the autopilot seems to be engaged already. Make sure the autopilot is not yet engaged BEFORE you load the flight plan. The flight plan from EFB is always forwarded to the default GPS of the simulator, as soon as it is created or updated, or deleted. If you don't want to automatically forward the flight plan to the simulator's Default-GPS you should deactivate this option in the respective aircraft profile settings. When your aircraft is airborne already and you are loading the flight plan which you created while you were on the ground, your aircraft is already ahead of the first waypoint of your plan. So after loading the flight plan you should use the 'Direct-to' function to select the next waypoint in front of you and then activate the autopilot.

Today we released the new update 2.3 (build #134). This update contains some minor improvements and bug fixes: Improvements: Procedures: FM/VM-Leg depiction improved Procedures: 'ALT between' values right aligned Long procedure names are recognized as a valid element in ATS route (e.g. when downloading a FPL from SimBrief using the built-in download function in EFB) Named Taxiways function slightly improved (see also this post: https://forum.aivlasoft.com/topic/6617-choosing-taxiways-never-seem-to-work/?do=findComment&comment=30091 Splash screen is now no longer displayed again after pressing 'Hide'. Scanning BGL-files logic improved. If you are using a BGL-file based database like for P3D, or MSFS you might want to rebuild the database using the DbBuilder function 'Update Simulator'. Bug fixes: DbBuilder allows to create a database which already exists. A 'database' in this regard means a combination of 'simulator + navdata' (e.g. 'MSFS + Navigraph', or 'P3D + Aerosoft'). For details please see the manual '4 EN Database.pdf'.