FSX & P3D NAVAIDS UPDATE WITH INSTALLER
Installer Version 9.21
Flying the simulator with a high degree of realism requires that the navigation data are up-todate. The provided world package is based on the latest available aeronautical information; it
includes a collection of modified BGL files that will update VORs and NDBs, affecting
instrument readings as well as map and GPS displays. A dedicated installer is provided so
as to select the regions to be updated, move the necessary files to their FSX/P3D locations,
backup the original files and restore them if needed. ILS data, runway identifiers,
approach lighting, PAPIs, enroute intersections and airways are also corrected in the
Europe area. In other regions only VORs and NDBs are corrected; correction of ILSs and
runway identifiers (as well as PAPIs and lighting systems in North America) will require you
also install my ILS/Rwy regional updates.
1 – METHODS
All changes were performed by correcting stock BGL files that contain the navaid data. In the
Europe region, ILS, runway data, approach lighting systems PAPIs, enroute intersections
and airways are also updated by correcting the corresponding ATX/APX*.BGL files.
2 – PACKAGE CONTENT
Decompress the FSXP3D_WorldNavaids zip package in any temporary folder of your choice
but outside the sim folder and check that the following files have been extracted:
A) In the root directory
FSXP3DNavaids_Installer.exe: the program that will automate the install/uninstall process,
FSXP3DNavaidsUpdate.pdf: this file,
Magdec.bgl: a new updated (2018) magnetic variation file for FSX/P3D (optional install),
Cycle.txt: the current AIRAC cycle,
World_Regions.jpg: an image file itemizing the geographical delimitation of the selectable
regions.
B) FSXNavFiles subfolder: contains all the new navaid BGL files for FSX and P3D v1.
C) P3DNavFiles subfolder: contains all the new navaid BGL files for P3D v2 to v4 (with
proper inclusion of TACAN and VORTAC facilities).
D) EuropeFiles subfolder: contains a corrected set of airport, airway and waypoint BGL files
for the Europe region as well as an internal list the program makes use of.
E) EuropeAltFiles subfolder: contains another set of airport BGL files for the Europe region
that will be used instead if the corresponding option is selected. See Chapter 4 for a
description of the differences between the “normal” set and this modified one.
F) MilitaryNavFiles subfolder: contains files for military use in FSX and P3D v1 (TACANs
providing azimuth).
After you performed the update, the provided package is not needed anymore and can be
deleted (unless you want to uninstall the updates). Each new AIRAC cycle will include a full
package as well as the installer.
3 – INSTALL, UNINSTALL and PROGRAM OPTIONS
The FSXP3DNavaids_Installer.exe program automatically checks the available simulator
versions (a choice will be proposed if several are detected), then installs or uninstalls the
necessary BGL files for it. When installing, only more recent BGL files than the current ones
are replaced in the regions that have been selected. All default sim files are saved with a
[.raxini] (FSX) or [.p3dini] (P3D all versions) extension in their initial directory. These
backup files are necessary for uninstalling the package. So, DO NOT delete them.
The FSXP3DNavaids_Installer executable is compatible with Windows XP, Vista, Windows
7, Windows 8/8.1 and Windows 10. For Vista and above, a pop up warning message will be
displayed if you didn’t disable the Program Compatibility Assistant feature. In such a case,
just select “This program installed correctly”.
Note that update will not be possible if FSX/P3D is installed in a protected folder (e.g.
Program Files (x86)) or Program Files (p3Dv4) unless user account has administrative rights
(administrator account or “run as administrator” option and UAC is fully disabled (Vista &
Windows 7; for Windows 8/10 see here) or modify/write allow permissions have been
properly set for the FSX/P3D directory and its folders (see here).
3.1 – Installer options
•
Update magvar table: will update magdec.bgl file (grayed if already set to latest version),
•
Use alternate airport files: will select for the Europe region, another set of files (see
Chapter 4 for differences between these normal and alternate sets),
•
Set military TACANs azimuth: will replace TACAN DME only data (civilian use) with
VORTAC information (military). This option is only available in FSX and P3Dv1. TACANs
and VORTACS will always be correctly defined in P3Dv2 and above,
•
Force Full Install: will update all selected files without checking date/time stamp of current
existing files (only to be used in case of confirmed lack of update of some files, preferably
on author’s request)
•
Log Install replacements: will create an [Installer_Actions.log] file in program directory on
Install action (to be used for support in case of problem, see chapter 7)
3.2 – Scenery rebuild
After install or uninstall has been performed, simulator will normally automatically rebuild its
indexes at first launch. In a few cases, it may happen this process doesn’t occur as
expected. In such cases, rebuild can be forced by going to the World/Scenery Library menu
and just clicking OK without making any change.
3.3 – Missing BGL files
Some 3rd party add-ons or other update programs may deactivate or replace some stock
BGL files. In such a case, the installer will first display a list of missing files and call for an
action. It is recommended you cancel the update and restore first the default files so as
to avoid a mix that could result in unpredictable results. In case you accept to continue,
missing files will be restored using those provided in the present package.
3.4 – Conflicts
Third party add-on sceneries may have a higher priority than the modified stock sim files
containing new navaid definitions. In such a case, they will conflict with the present update
and the new navaids in the stock sim files will be inactive. If such conflicts are detected,
a list of affected navaids will be displayed by clicking the [Conflicts] button.
Note that the scenery.cfg file is checked for active sceneries with higher priority; also all
P3Dv3-4 sceneries referenced in the ..\My Documents\..add-on.xml files are included.
4 – LIMITATIONS and ADDITIONAL INFORMATION
Replacing BGL files within the simulator cannot be done if the simulator is active. The
installation program will look at it and warn you accordingly.
The program automatically detects FSX/P3D installation directories. Sometimes, this process
may fail. In such a case, it is recommended you repair the Windows registry data. A registry
repair tool is available on the Flight1 software site.
The update will replace “stock” BGL files. Therefore, any additional scenery will have the
same priority as it had before by reference to the default scenery files.
For the Europe region an alternative set of airport BGL files is proposed. Its main advantage
is that most terminal fixes will also be properly updated for the corresponding region giving a
clean and up to date GPS and map displays. However, the following limitations will apply: all
GPS approaches will be deactivated (anyway, note that most of them are outdated). Navaid
and other updates will be identical to those implemented in the normal set.
5 – KNOWN PROBLEMS
Replacement of stock navaids BGL files (as well as airport and airway data in the Europe
area) may have side effects on generated flight plans, map display, GPS approaches using
default sim data (but not those using external providers) and possibly AI traffic and ATC
functionalities.
Due to the fact the BGLs that contain airway definitions (not updated by this project except
for Europe) may still contain invalid references to nonexistent VORs or NDBs, flight planning
usually fails outside the Europe region and may result in crashing the simulator. Loading a
sim-generated saved PLN file may have similar effects as well as switching to map view in
some areas. GPS display is not affected (except for possible problems with approaches).
Also note that, starting with AIRAC1613, this problem will not occur in the Europe region
where all airways are corrected.
Even if default flight planning is often impossible outside Europe after updating navigational
aids and approach data may be compromised, they are anyway unreliable since many
airways, navaids, intersections and approach procedures have changed (FSX and P3D
information date back several years).
Indeed, most serious simmers are more searching for an up-to-date definition of navigation
aids so as to use conventional instruments and/or GPS information from current AIPs and/or
3rd party providers; they also perform flight planning and published approaches from charts or
using 3rd party tools that include up-to-date aeronautical information. They do not use the
integrated flight planner and default GPS approaches and seldom make use of map viewing.
Loading PLN files that have been generated by any other mean than the simulator itself is
not a problem as far you do not intend to view or edit it. Such users will not have any problem
with the provided package.
For those who still wish to use the integrated flight planner editor and/or map screen or
encounter problems when loading a flight plan, avoiding simulator crash can usually be
achieved by deactivating airway depiction and intersections on the flight planner and map
screens.
1 – Before loading a flight plan, disable the drawing of Victor and Jet airways in the Edit
menu (the V and J buttons should now be red in FSX or disabled in P3D; the below flight
plan and map pictures refer to FSX settings; P3D settings are similar). In some areas you will
also have to deactivate the drawing of intersections (the triangle),
2 – Also deactivate airways drawing (and possibly intersections) in the Map view
If you cannot open the flight planner and/or map screens because of a crash, you will have to
modify the following lines of the FSX.cfg (FSX) or UISettings.xml (P3D) file before
launching the simulator:
FSX
In the [MAPVIEW_MAP] section
SHOW_VICTOR=0
SHOW_JET=0
SHOW_INTERSECTIONS=0
P3D
In all sections
<VictorAirway>false</VictorAirway>
<JetAirway>false</JetAirway>
<AirwayIntersection>false</AirwayIntersection>
In the [FlightPlanMap] section
SHOW_VICTOR=0
SHOW_JET=0
SHOW_INTERSECTIONS=0
3 – If you are still unable to load an already existing flight plan without crashing the simulator,
first locate your aircraft in another area, load your flight plan and then relocate your aircraft at
the intended departing airport.
6 – HOW TO CHECK FOR A POSSIBLE NAVAID ANOMALY
If you think that, after applying the Navaids Update, some data are erroneous or not properly
corrected, please first carry out the following checks:
1 – In the World / Scenery Library menu, first disable all third party sceneries as well as
the Addon Scenery area. Click on the OK button and relaunch the simulator,
2 – Then check again the “dysfunctional” navaid.
Know that most problems come from installed 3rd party add-on sceneries whose
priority is higher than default sceneries. Also be aware that, except for the Europe region,
a few NDBs may not be corrected by the present update (those that are contained in
untouched airport BGL files).
3 – If there is still a problem, make use of my BGL Facility Scanner to check the navaid and
provide me either a screen shot of the search results or the created log file (preferred).
Please feel free to email me in case you detect an error so as I correct it as soon as possible.
7 – PROGRAM “FAILURES” AND INSTALL LOGGING
7.1 – Program failures
In case the program warns you about corrupted files or is unable to install or uninstall some
of the provided BGL files for whatever reason, a message will warn you and a
Navaids_Installer.log file will be created in the application directory. In such a case, close
the program without performing any further action and provide me the following information:
operating system, version of the simulator and install folder, installer program version, user
privileges (standard user or administrator), User Account Control settings (for Vista and
above) and attach to your message the Navaids_Installer log file.
7.2 – Install logging
In case the installer doesn’t correctly update some files, I also may be able to check program
actions by examining a specially created Installer_Actions.log file.
Proceed according to the list below:
• First enter all wanted selections as usual (region selection, optional use of alternate
airport files),
• Check the Log Install replacements option (a warning will be issued),
• Note the resulting BGL status numbers (No change, To be proceeded, Deinstallable) or
make a screenshot of the main screen,
• Then click the Install button,
• After Install has been completed, note again the BGL status numbers or make a second
screenshot of the main screen,
• Close the program without performing any further action.
Provide me the BGL status numbers (or screenshots) as well as the Installer_Actions.log file
that has been created in the application directory.
8 – COPYRIGHT and REDISTRIBUTION
1 – Usage and distribution
This package and the accompanying installer software are released as donationware. As so,
permission is granted to distribute it unchanged on any free media. If you want to include
parts of it to your own program, package or on your web site, please ask me.
2 – Limitation of warranty
These software and package are provided "as-is" without any express or implied warranty. In
no event shall the author be held liable for any direct, indirect, incidental, special, exemplary
or consequential damages (including but not limited to loss of data or profits) arising from the
use of this software even if advised of the possibility of such damage.
Hervé Sors
20-Mar-2019
Documentation version 9.22
hsors@hotmail.com
http://www.aero.sors.fr