Some FAQ and answers related to navaid updates
May 24, 2013 9:28:45 GMT
Post by Herve Sors on May 24, 2013 9:28:45 GMT
Here is a list of answers to questions frequently asked by users regarding the installation and use of my FS9/FSX/P3D navaid updates. If you have some more let me know
1) When launching the installer, I've got the message "Flight Simulator is installed in a protected system directory, not enabling update and uninstall processes. Administrator accounts with UAC fully disabled may still use the program to update.."
It means Flight Simulator/P3D (and its associated files) has been installed in a Windows system protected directory (usually Program Files (x86) that, unfortunately, is the default installation option) where files can only be modified by members of the Administrator and Power Users user groups. Starting with Vista, Microsoft has implemented additional security mechanisms to prevent file or folder modifications via the User Account Control (UAC).
Consequently, addons that directly replace some core sim files (such as this Navaids installer) will fail if user doesn't have administrator rights or UAC is enabled.
Users with administrator rights and UAC fully disabled via the control panel may still be able to use the installer. In Windows 8, 10 and 11, UAC cannot be fully disabled unless performing some changes to the registry: see www.computerperformance.co.uk/win8/windows8-uac-disable.htm
As a general advise (shared by many addon developers), simulator installation should preferably be performed in a dedicated unprotected folder (e.g. C:\FS9, C:\FSX, etc..) so as to avoid this problem. You may also change permission rights on your sim folder so as to be able to update (see documentation for how to do that). Sometimes, runing the installer with administrator rights (run as administrator) may also be successful. For some installers, I propose a /forcepermissions command-line argument that may solve some problems but also raise install errore.
2) Why updating simulator "stock" navaids and not just adding missing or modified navaids in a dedicated BGL file?
Many 3rd party scenery editors allow you yo create new BGL files in which you can define navaids that are new or have been modified; however they cannot remove obsolete "stock" navaids or even change them. Consequently, there will be "duplicates" and "fakes" and GPS/map navaid display will still show that.
3) I already have updated up-to-date FMC data for my aircraft. Do I need to update navaids as you propose?
Yes..FMC data will enable you to plan routes (including SIDs and STARs), display calculated flight paths and a lot more. Such tasks are performed internally from the integrated FMC database. However VORs, NDBs and ILSs information on simulator instruments (VOR receivers, ADF, RMI) are still based on what internally the sim provides. The same is true for the integrated GPS and map view. For advanced FMC users, not updating internal sim database will often result in "disagreement warnings" while performing ILS approaches and approach mode not engaging until you manually correct the ILS frequency.
4) Does your updates apply to ILS? After I installed them, ILS data are not properly corrected in my Sim
Yes and no, depending on your sim version, what you installed and the active addons you have.
If you just installed the World Navaids package (FSX/P3Dv1-4 users), only Western Europe ILSs are corrected.
Updating ILSs in other regions requires you also install the World ILS/Rwy package (FSX and P3Dv1-4 only).
FS9 users will only be able to update ILSs in the Western Europe region.
In all cases, a 3rd party scenery - that has a higher priority - may supersede some changes, depending on scenery coverage (see FAQ 8)
5) What's the problem with flight plan/map view after replacing stock navaids?
Replacement of stock navaids BGL files has known side effects on sim generated flight plans, map display and AI traffic.
Due to the fact the simulator also uses BGLs that contain airway definitions (by now only updated in the Europe region) and that some other BGL files may still contain invalid references to nonexistent VORs or NDBs, integrated flight planning usually fails and may result in crashing the simulator outside Europe. 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.
Even if default flight planning is often impossible after updating navigational aids, most airways, and many navaids and intersections have changed and flight planning is anyway unreliable.
Indeed, most serious simmers are more searching for an up-to-date definition of radioaids so as to use conventional radio navigation instruments and/or GPS information from current AIPs; they also perform flight planning either from charts or using 3rd party tools that already include up-to-date aeronautical information. They do not use the integrated flight planner and seldom make use of map viewing, so in my opinion this problem remains marginal for them.
Loading a PLN file 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.
For those who still wish to use the flight planner editor and/or map screen or encounter problems when loading a flight plan, avoiding crashes can be achieved by deactivating airway depiction and intersections on the flight planner and map screens. See the documentation for a detailed way of how to do that.
6) Could the update kill my 3rd party sceneries or fail updating data due to 3rd party sceneries ?
Usually no, since 3rd party sceneries do not change stock simulator files.
It could happen for the very few addons that change the default navaids or airport BGL files (those called AP*.BGL in FS9 and APX*.BGL or NV*.BGL in FSX/P3D).
7) Are all navaids corrected ?
It depends on what you installed and the options you set in the installer
a-You just installed the World Navaids package
All navaids will be corrected in the Western Europe area if you use the "Alternate airport files" option (but you will lose approach data). In other cases and in other regions, a few NDBs may be left uncorrected (although main navigational data will be corrected) and a few inaccuracies or duplicates may remain.
b-You installed both the World Navaids package and the World ILS/Rwy package
Everything should be corrected.
8a) The "XXX" VOR,ILS,NDB is still on the wrong (old) frequency or doesn't appear after I updated or is still there although it doesn't exist anymore. Did you make a mistake?
Could be but in 99.9% of the cases it is due to a scenery you installed that has priority on the default sceneries. In such a case use the [Conflicts] button and you will usually have the answer. Alternatively, you can check for a particular conflict using my BGL Facility Scanner. Confirmation will be obtained by disabling 3rd party sceneries that cover the same area in the Settings/Scenery Library menu. See the documentation I provide (chapter 6) for more details and screen shots.
Understand I cannot correct data that are provided by scenery developers even if my BGL Navaids Editor and Airport Inspector and Editor (AIE) can usually do that. Use them at your convenience but the normal way is to ask the developer
8b) The runway identifiers are not updated after I installed your ILS/Rwy updates
Again it could be I missed some changes but in 99.9% of the cases it is again due to a scenery you installed that has priority on the default sceneries. Look at your Scenery library to find the culprit and temporarily disable the responsible scenery addons to obtain a definitive confirmation
9) Where do my data come from and how can you check them?
I usually build the navigational aid database from available AIP'ss and Jeppesen updates I receive every month (I'm a registered customer). Jeppesen navaid databases are "hardcoded" and cannot be converted. It will also be a copyright infringement to do so. Consequently information is entered by "hand" and converted to the proper format. When possible, I always check the provided information against country AIP's. Interim releases are based on published Jeppesen Notices & Alerts (https://ww2.jeppesen.com/notices/) but information is fully rechecked every month. It's still a long work as far as there is around 4,000 VORs, 6,000 NDBs and 4,000 ILSs worlwide with a 1-2% change rate at each AIRAC cycle. Globally, even if my database is not 100% error free, it should be nearly 99.9% ;-)
10) What about navaid "station declination"?
All navaids that provided an azimuth (TO/FROM) i.e. VORs, VORDMEs, military TACANs are "calibrated" to a specific station declination value that is not necessarily the current magnetic variation (as an example, many US VORs are still calibrated to 2005 values or even earlier, some are 2010, others have been recalibrated to 2019 values). This calibration value is included in the navaid record; it is changed from time to time by aeronautical authorities. It is important this value is correctly set for each navaid even if station declination may differ from the current magnetic variation at station position so as following a given radial matches current chart information. Hopefully, in most cases, station calibration is very near actual magnetic variation, so that it will not affect so much your navigation. Note that this concept also applies to ILSs but in such a case, it will only affect the ILS magnetic course on chart view. See a more detailed discussion on the subject in this forum threads and a few others
aerosors.freeforums.net/thread/112/magnetic-variation-problems-airac-data
aerosors.freeforums.net/post/218/thread
www.askacfi.com/3857/true-course-compared-to-vor-radials.htm
flightlevelsonline.com/2013/summer-2013/garmin-tips-and-tricks-gps-and-magnetic-variation/
See also, a summary document here: www.aero.sors.fr/documentation/UnderstandingMV.pdf
11) What about using "Alternate airport files" option in the World Navaids Installer
I recommend advanced simmers use this option considering, in covered areas (Europe), (i) it will update all navaids (without any missing or duplicate navaids) (ii) it will also perform a "clean" update of terminal intersections. However it has some drawbacks especially regarding inactivation of default approach procedures (but who cares considering most - if not all - are now outdated..).
12) Although I'm 110 nm from a VORDME, I do not receive the signal? What's going on?
Most default FS navaids have "unrealistic" ranges. My updates define designated operational coverages of navaids as provided by AIPs. In case they are unavailable, I use standard ICAO service volumes according to navaid type. I carefully check this information but in case you think I'm wrong, let me know and provide me the reference documentation so as I correct it.
13) This ILS is not correctly aligned with runway heading
Usually, it means it is an "offset" ILS.
Check with my Airport Inspector and Editor software. It provides current status of Sim ILSs as well as real AIRAC data (with offsets from rwy centerline) so it should be easy to compare and provide an unequivocal answer.
14) ILS frequency has changed and is wrongly defined in the update you provided
Ensure you have the latest update cycle and compare it to the corresponding AIRAC information (including amendments). Normally, ILS information I provide is up to date at the time it is online on my site. See also FAQ 4.
15) How do you update ILSs?
Using published coordinates of the different parts of the ILSs without any correction (LOC, GP and DME) is not the right way doing that, just because some runways in the simulator may not precisely match the real ones (as regards geographical position of thresholds, length and bearings). Consequently the best way is to calculate longitudinal/lateral offsets of ILS components from real data and apply them to sim runway data. I automated the process in my design software. Also ILS magnetic variation and beam width are precisely determined and defined in the updates as well as associated scenery objects. Offset ILSs are designed the same way. PAPIs positions and characteristics are corrected using either AIP information and/or Google Earth pictures (nearly all PAPIs are wrongly positioned in default sim sceneries). ILSs with DME reading 0 at runway theshold are also correctly set in my updates.
16) Should I check "Do not update airport files" to solve problems I could have?
This option was removed in the latest installer version
17) Is it possible to add/change/delete an existing navaid without installing the global update you provide?
Yes, using either the BGL Navaids Editor (VORs and NDBs) or Airport Inspector and Editor (ILSs). These softwares work at the BGL level without any need for decompiling/recompiling files and everything can be changed. However, it is a complicated process (due to the complex reindexing of BGL sections that is sometimes needed) and, although I carefully tested the code in all aspects, I cannot ensure all BGLs will be properly patched. If you make a copy of the original BGL you intend to modify, you could give it a try as far as - if you backup first - it is a zero risk process ;-)
18) What about markers?
All updates I provide also correct OM,MM,IM according to provided data. The way I did that is similar to the way ILSs data were adjusted (see 15)
19) Could your updates crash my simulator?
Definitely not at the exception of Flight plan/map view problems (see FAQ 5).
20) I have another problem. May I ask you?
For sure..but please ensure it is not already covered in the present list and you also read the complete documentation I provide (both on my site and as part of the installer packages). Many don't!
21) Now about some warnings, you'll find here and there repetitively (I presume from those who don't mind using massively outdated airport information without corresponding charts because they are not available anymore)
- Your updates break integrated flight planning: Only outside Europe but in other regions, in many cases they do. But, as far as integrated fligh planning is completely outdated (most airways & many navaids have changed since FSX release, FSX-SE and P3Dv1-4 didn't change that), it's not much worse
- Integrated approaches do not work anymore: many will not indeed (and for some updates, I removed them completely). As far as 90% are also outdated, it is the same. Better use your current charts and it will do it. Also consider your third party FMC data (Navigraph or Aerosoft for those who use them) will provide up to date data that will not fit sim data unless you update them,
- Why not making corrections with ADE for each airport (rather than changing stock files)?: Because, (a) You're not necessarily an expert (b) many scenery designers do not focus on accurate navaid/ILS data and/or do not update their sceneries when a change is effective (c) ADE has limitations regarding the possibility to update stock navaids (d) and, finally, because there's about 4150 ILSs approaches worldwide and you, probably, will not find an up to date and accurate scenery for each of them,
Finally, some simmers prefer to stay with older (2007) data for training purpose. At the condition you also have the corresponding charts, it's perfectly OK doing that. Unfortunately such old charts are not readily available.
1) When launching the installer, I've got the message "Flight Simulator is installed in a protected system directory, not enabling update and uninstall processes. Administrator accounts with UAC fully disabled may still use the program to update.."
It means Flight Simulator/P3D (and its associated files) has been installed in a Windows system protected directory (usually Program Files (x86) that, unfortunately, is the default installation option) where files can only be modified by members of the Administrator and Power Users user groups. Starting with Vista, Microsoft has implemented additional security mechanisms to prevent file or folder modifications via the User Account Control (UAC).
Consequently, addons that directly replace some core sim files (such as this Navaids installer) will fail if user doesn't have administrator rights or UAC is enabled.
Users with administrator rights and UAC fully disabled via the control panel may still be able to use the installer. In Windows 8, 10 and 11, UAC cannot be fully disabled unless performing some changes to the registry: see www.computerperformance.co.uk/win8/windows8-uac-disable.htm
As a general advise (shared by many addon developers), simulator installation should preferably be performed in a dedicated unprotected folder (e.g. C:\FS9, C:\FSX, etc..) so as to avoid this problem. You may also change permission rights on your sim folder so as to be able to update (see documentation for how to do that). Sometimes, runing the installer with administrator rights (run as administrator) may also be successful. For some installers, I propose a /forcepermissions command-line argument that may solve some problems but also raise install errore.
2) Why updating simulator "stock" navaids and not just adding missing or modified navaids in a dedicated BGL file?
Many 3rd party scenery editors allow you yo create new BGL files in which you can define navaids that are new or have been modified; however they cannot remove obsolete "stock" navaids or even change them. Consequently, there will be "duplicates" and "fakes" and GPS/map navaid display will still show that.
3) I already have updated up-to-date FMC data for my aircraft. Do I need to update navaids as you propose?
Yes..FMC data will enable you to plan routes (including SIDs and STARs), display calculated flight paths and a lot more. Such tasks are performed internally from the integrated FMC database. However VORs, NDBs and ILSs information on simulator instruments (VOR receivers, ADF, RMI) are still based on what internally the sim provides. The same is true for the integrated GPS and map view. For advanced FMC users, not updating internal sim database will often result in "disagreement warnings" while performing ILS approaches and approach mode not engaging until you manually correct the ILS frequency.
4) Does your updates apply to ILS? After I installed them, ILS data are not properly corrected in my Sim
Yes and no, depending on your sim version, what you installed and the active addons you have.
If you just installed the World Navaids package (FSX/P3Dv1-4 users), only Western Europe ILSs are corrected.
Updating ILSs in other regions requires you also install the World ILS/Rwy package (FSX and P3Dv1-4 only).
FS9 users will only be able to update ILSs in the Western Europe region.
In all cases, a 3rd party scenery - that has a higher priority - may supersede some changes, depending on scenery coverage (see FAQ 8)
5) What's the problem with flight plan/map view after replacing stock navaids?
Replacement of stock navaids BGL files has known side effects on sim generated flight plans, map display and AI traffic.
Due to the fact the simulator also uses BGLs that contain airway definitions (by now only updated in the Europe region) and that some other BGL files may still contain invalid references to nonexistent VORs or NDBs, integrated flight planning usually fails and may result in crashing the simulator outside Europe. 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.
Even if default flight planning is often impossible after updating navigational aids, most airways, and many navaids and intersections have changed and flight planning is anyway unreliable.
Indeed, most serious simmers are more searching for an up-to-date definition of radioaids so as to use conventional radio navigation instruments and/or GPS information from current AIPs; they also perform flight planning either from charts or using 3rd party tools that already include up-to-date aeronautical information. They do not use the integrated flight planner and seldom make use of map viewing, so in my opinion this problem remains marginal for them.
Loading a PLN file 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.
For those who still wish to use the flight planner editor and/or map screen or encounter problems when loading a flight plan, avoiding crashes can be achieved by deactivating airway depiction and intersections on the flight planner and map screens. See the documentation for a detailed way of how to do that.
6) Could the update kill my 3rd party sceneries or fail updating data due to 3rd party sceneries ?
Usually no, since 3rd party sceneries do not change stock simulator files.
It could happen for the very few addons that change the default navaids or airport BGL files (those called AP*.BGL in FS9 and APX*.BGL or NV*.BGL in FSX/P3D).
7) Are all navaids corrected ?
It depends on what you installed and the options you set in the installer
a-You just installed the World Navaids package
All navaids will be corrected in the Western Europe area if you use the "Alternate airport files" option (but you will lose approach data). In other cases and in other regions, a few NDBs may be left uncorrected (although main navigational data will be corrected) and a few inaccuracies or duplicates may remain.
b-You installed both the World Navaids package and the World ILS/Rwy package
Everything should be corrected.
8a) The "XXX" VOR,ILS,NDB is still on the wrong (old) frequency or doesn't appear after I updated or is still there although it doesn't exist anymore. Did you make a mistake?
Could be but in 99.9% of the cases it is due to a scenery you installed that has priority on the default sceneries. In such a case use the [Conflicts] button and you will usually have the answer. Alternatively, you can check for a particular conflict using my BGL Facility Scanner. Confirmation will be obtained by disabling 3rd party sceneries that cover the same area in the Settings/Scenery Library menu. See the documentation I provide (chapter 6) for more details and screen shots.
Understand I cannot correct data that are provided by scenery developers even if my BGL Navaids Editor and Airport Inspector and Editor (AIE) can usually do that. Use them at your convenience but the normal way is to ask the developer
8b) The runway identifiers are not updated after I installed your ILS/Rwy updates
Again it could be I missed some changes but in 99.9% of the cases it is again due to a scenery you installed that has priority on the default sceneries. Look at your Scenery library to find the culprit and temporarily disable the responsible scenery addons to obtain a definitive confirmation
9) Where do my data come from and how can you check them?
I usually build the navigational aid database from available AIP'ss and Jeppesen updates I receive every month (I'm a registered customer). Jeppesen navaid databases are "hardcoded" and cannot be converted. It will also be a copyright infringement to do so. Consequently information is entered by "hand" and converted to the proper format. When possible, I always check the provided information against country AIP's. Interim releases are based on published Jeppesen Notices & Alerts (https://ww2.jeppesen.com/notices/) but information is fully rechecked every month. It's still a long work as far as there is around 4,000 VORs, 6,000 NDBs and 4,000 ILSs worlwide with a 1-2% change rate at each AIRAC cycle. Globally, even if my database is not 100% error free, it should be nearly 99.9% ;-)
10) What about navaid "station declination"?
All navaids that provided an azimuth (TO/FROM) i.e. VORs, VORDMEs, military TACANs are "calibrated" to a specific station declination value that is not necessarily the current magnetic variation (as an example, many US VORs are still calibrated to 2005 values or even earlier, some are 2010, others have been recalibrated to 2019 values). This calibration value is included in the navaid record; it is changed from time to time by aeronautical authorities. It is important this value is correctly set for each navaid even if station declination may differ from the current magnetic variation at station position so as following a given radial matches current chart information. Hopefully, in most cases, station calibration is very near actual magnetic variation, so that it will not affect so much your navigation. Note that this concept also applies to ILSs but in such a case, it will only affect the ILS magnetic course on chart view. See a more detailed discussion on the subject in this forum threads and a few others
aerosors.freeforums.net/thread/112/magnetic-variation-problems-airac-data
aerosors.freeforums.net/post/218/thread
www.askacfi.com/3857/true-course-compared-to-vor-radials.htm
flightlevelsonline.com/2013/summer-2013/garmin-tips-and-tricks-gps-and-magnetic-variation/
See also, a summary document here: www.aero.sors.fr/documentation/UnderstandingMV.pdf
11) What about using "Alternate airport files" option in the World Navaids Installer
I recommend advanced simmers use this option considering, in covered areas (Europe), (i) it will update all navaids (without any missing or duplicate navaids) (ii) it will also perform a "clean" update of terminal intersections. However it has some drawbacks especially regarding inactivation of default approach procedures (but who cares considering most - if not all - are now outdated..).
12) Although I'm 110 nm from a VORDME, I do not receive the signal? What's going on?
Most default FS navaids have "unrealistic" ranges. My updates define designated operational coverages of navaids as provided by AIPs. In case they are unavailable, I use standard ICAO service volumes according to navaid type. I carefully check this information but in case you think I'm wrong, let me know and provide me the reference documentation so as I correct it.
13) This ILS is not correctly aligned with runway heading
Usually, it means it is an "offset" ILS.
Check with my Airport Inspector and Editor software. It provides current status of Sim ILSs as well as real AIRAC data (with offsets from rwy centerline) so it should be easy to compare and provide an unequivocal answer.
14) ILS frequency has changed and is wrongly defined in the update you provided
Ensure you have the latest update cycle and compare it to the corresponding AIRAC information (including amendments). Normally, ILS information I provide is up to date at the time it is online on my site. See also FAQ 4.
15) How do you update ILSs?
Using published coordinates of the different parts of the ILSs without any correction (LOC, GP and DME) is not the right way doing that, just because some runways in the simulator may not precisely match the real ones (as regards geographical position of thresholds, length and bearings). Consequently the best way is to calculate longitudinal/lateral offsets of ILS components from real data and apply them to sim runway data. I automated the process in my design software. Also ILS magnetic variation and beam width are precisely determined and defined in the updates as well as associated scenery objects. Offset ILSs are designed the same way. PAPIs positions and characteristics are corrected using either AIP information and/or Google Earth pictures (nearly all PAPIs are wrongly positioned in default sim sceneries). ILSs with DME reading 0 at runway theshold are also correctly set in my updates.
16) Should I check "Do not update airport files" to solve problems I could have?
This option was removed in the latest installer version
17) Is it possible to add/change/delete an existing navaid without installing the global update you provide?
Yes, using either the BGL Navaids Editor (VORs and NDBs) or Airport Inspector and Editor (ILSs). These softwares work at the BGL level without any need for decompiling/recompiling files and everything can be changed. However, it is a complicated process (due to the complex reindexing of BGL sections that is sometimes needed) and, although I carefully tested the code in all aspects, I cannot ensure all BGLs will be properly patched. If you make a copy of the original BGL you intend to modify, you could give it a try as far as - if you backup first - it is a zero risk process ;-)
18) What about markers?
All updates I provide also correct OM,MM,IM according to provided data. The way I did that is similar to the way ILSs data were adjusted (see 15)
19) Could your updates crash my simulator?
Definitely not at the exception of Flight plan/map view problems (see FAQ 5).
20) I have another problem. May I ask you?
For sure..but please ensure it is not already covered in the present list and you also read the complete documentation I provide (both on my site and as part of the installer packages). Many don't!
21) Now about some warnings, you'll find here and there repetitively (I presume from those who don't mind using massively outdated airport information without corresponding charts because they are not available anymore)
- Your updates break integrated flight planning: Only outside Europe but in other regions, in many cases they do. But, as far as integrated fligh planning is completely outdated (most airways & many navaids have changed since FSX release, FSX-SE and P3Dv1-4 didn't change that), it's not much worse
- Integrated approaches do not work anymore: many will not indeed (and for some updates, I removed them completely). As far as 90% are also outdated, it is the same. Better use your current charts and it will do it. Also consider your third party FMC data (Navigraph or Aerosoft for those who use them) will provide up to date data that will not fit sim data unless you update them,
- Why not making corrections with ADE for each airport (rather than changing stock files)?: Because, (a) You're not necessarily an expert (b) many scenery designers do not focus on accurate navaid/ILS data and/or do not update their sceneries when a change is effective (c) ADE has limitations regarding the possibility to update stock navaids (d) and, finally, because there's about 4150 ILSs approaches worldwide and you, probably, will not find an up to date and accurate scenery for each of them,
Finally, some simmers prefer to stay with older (2007) data for training purpose. At the condition you also have the corresponding charts, it's perfectly OK doing that. Unfortunately such old charts are not readily available.