hervesors

Hi, I presume you installed the FSX Navaids update that is referenced here https://www.aero.sors.fr/navaids3.html As per the included and online documentation Note that embedded approaches referencing decommissioned navaids or intersections are removed and this will affect AI traffic as well as automatic ATC. Indeed, the update package includes updated navaids, ILSs, en route intersections, terminal intersections and airways that deactivate most of the automatic ATC functions. Consequently, I will suggest you do not use (and uninstall) this update package, if your main interest is to keep the automatic ATC facilities that are based on the stock sim files. Hervé

That's correct. Now, if you like to keep your 3rd party scenery (because it provides some enhancements), a possible way is just to change runway numbering inside your KFLL.bgl (for your personal use) using the ILS/Runway inspector and editor tool you'll find on my site. Many scenery editors do not provide updates at the time such changes occur. A backup of the original file is automatically done by the software, so you don't have to worry about that. Taxiway signs and associated approaches (if any) will be updated accordingly. You can give it a try

Guys, just take the time to read what is provided Consequently KFLL runway numbering is corrected in North America ILS/Rwy regional update..but not in FSX/P3D World Navaids package Hope it will clarify

Don't know Jaap..but there's something that still defines ILS IKEN on the wrong 109.70 frequency. Seems to be the case considering the altitude problem you have can't occur IMO if the stock FS scenery alone is active. You should have a look to all installed sceneries on your sim and may also use my ILSNavaid debugger (see the doc I provide for the link) to find it out. Fell free to email me privately (my email contact is on my web page) if you need further help Hervé

No..EDDK ILS/DME 32R is on 111.10 since a long. If you still have this ILS on 109.70 it means it is provided by another scenery with a higher priority or you didn't install airport updates properly. I've no problem at all with the 3 EDDK ILSs (IKEN 111.10 - IKES 110.90 and IKOW 109.10) Hope it will help

Agree..presumably it has been the reason why AOPA put a little bit the pressure..situation is even more critical in many countries where GA pilots cannot afford it (relalively) :Shame On You:

Probably not so soon and not to this extent. There is at this time 1130 active VOR, VORDME, DME & TACANs in the US. A few (around 10) are already in a shutdown status. Indeed, many will also been decommissioned starting in 2020 but only a very few since then. See here http://www.aopa.org/News-and-Video/All-News/2015/November/24/FAA-begins-decommissioning-VORs Also, around 5-10 NDBs are decommissioned each month but there's still around 1070 active NDBs in the US, among which 35-40 only are in a shutdown status..so most are not yet decommissioned and will probably not be in the next few years. Still some room for conventional radionavigation Hervé

It should be so there is definitely another "airport scenery" that prevents a proper display of the modified airport, as shown below on my sim (I only have Orbx FTX Global Base installed) and/or you checked the "Do not update airport files" option.

Hi Marian and Chris, Just to clarify For Western Europe, "navaids" update also correct (in addition to VOR, NDBs and ILSs) all runway identifiers, PAPIs, runway & approach lighting systems as stated in the documentation (1st page, 1st paragraph). I suspect FTX Global openLC Europe includes its own airport updates and not only landclasses (to be confirmed). Consequently, with a higher priority over stock BGL files, there's no chance provided changes to stock files could be active, likely the reason why you didn't see any change in LRIA runway identifiers (that are indeed included in the changes I performed since it has been published)..unless you didn't correctly install the navaids update and/or check the "Do not update airport files" Regards Hervé

Note that most of them do not apply to ILS/Rwy regional updates, but only to VOR/NDB regular navaid updates as provided in the World navaids package . Will have to clarify the FAQ. Thanks for pointing that.

Sorry but there's none..but I'm pretty sure you'll find your way with the functions it provides quite easily :wink: Hervé

Thanks Bill. I'm still a novice on these aspects ;-) Highly appreciated. Hervé

Thanks a LOT..It works nicely although I had to find the steps to implement it. For those interested: 1) First I had to extract all files from the default fs9gps.cab (using winrar on my side but I presume other unzip software will work nicely) 2) Considering my aircraft is using the GPS_500 (gauge00=fs9gps!gps_500), I changed the following gps_500.xml file section (addition is in bold) I have still to experiment with different RGB values 3) Then I rebuilt the cab file, using Makecab.exe and a bat script I found on a site http://www.dostips.com/forum/viewtopic.php?t=1977 Curiously file size decreased from 551 KB to 527 KB..but without apparent problem in the sim Now I can see my terminal intersections Wonderfull! Thanks again for that Hervé

Hi guys Not absolutely sure, it is the right forum, but I'll try here. Does anyone know if it is possible to change the display color of fixes on GPS windows (both default and 3rd party ones that behave similarly)? Light pink for en route intersections is OK, but dark blue for terminal intersections is hardly visible (seems however it may depend on graphic card, NVidia driver and/or monitor settings). What is your experience about that? I know there's no option inside the sim for that. However, may be there is a workaround I didn't find. Hervé

Not really, considering that what will be used by the simulator for instrument following (ILSs & other navaids) is what the sim provides in its internal database. In case you tune an updated frequency that does not match the sim one, you'll have a "discrepancy" warning on your FMC and any automatic approach mode will not work. More details in my FAQ list (N°3) here http://aerosors.freeforums.net/thread/5/faq-answers-related-navaid-updates Hope it will clarify Hervé

Jim, the quoted packages also correct airport runways Ids, at least those for which there is a LOC,LDA, SDF or an ILS..Not all airports of course. It includes corrections of some associated data, e.g. taxiway signs, approach data, some terminal waypoints. Hervé

LEPA ILS magnetic course (both 24R and 24L) is indeed 239°. After checking the last update I provided for LEPA, ILS magnetic heading is 238.52. Since ILS magnetic variation is defined to 0°E (real actual value), world map will indicate 239° (and it is what I have on my FSX map). So I suspect (i) either you didn't install airport updates (APX48170 should be dated 18-Sep-2014) (ii) or you have an addon scenery that incorrectly defines these data. Anyway, ILS following should be independant since it uses what FSX provides and not any panel or FMC setting. Feel free to email me directly if you like we investigate the problem further on Regards Hervé

Hi Scott Except for some Europe files, the proposed updates did not make use of any decompiler. There were build by direct changes to the relevant BGL sections (and there's quite a lot when building or correcting an ILS or a runway identifier taking into account all necessary changes including several indexes, some scenery ojects, etc) but nothing else is changed. But of course, backup oif original files is anyway mandatory. Hervé

Sure Bill..let's wait and see ;-)

In regions where ILS are updated by the project (Europe area), it doesn't happen considering ILS data are corrected for sim runway position (the way it is done is explained in FAQ 15) so there is no chance you land on grass unless it is a grass runway ;-) http://aerosors.freeforums.net/thread/5/faq-answers-related-navaid-updates For other regions (those where ILS were left untouched), nothing is updated at all (except VORs and most NDBs) so you'll get the default sim configuration. Of course, I agree a new and updatable worldwide database would be the ideal solution but I'm not so optimistic regarding that considering the information is disseminated in numerous files

You could also have a look to ILS Inspector/editor editor part. It will give you full details on current ILSs in any BGL selection (file/folder or even full sim folder) and also provide you a direct comparison with current up to date AIRAC data It is a portable application (no install) http://www.aero.sors.fr/navaids.html

Which install configuration did you use? 1) Included European waypoints from FSXP3D installer with "alternate set" checked? 2) Manual addition of the WordlINT or EurINT.bgl files ? May be you can mail me directly at hsors(at).hotmail(dot)com so as to sort it out Regards

Yep..enjoy flying in Europe in a realistic environment

Yes except that worlINT is not appropriate if you use "alternate airport files" as far as it already includes updated Europe fixes..(see doc). You may install some additional regional INT files instead (except Europe one) but have a look as it is. It shouldn't be a big problem

You should read "except for all European airports" (in fact for them, much more is corrected including navaids, ILSs, runway identifiers, PAPIs and approach lighting systems, as indicated in the documentation if at least you didn't check the "Do not update airport files") Even if I understand it will not satisfy non Europeans, I still hope you will enjoy it if you don't have any replacement sceneries for them This is only for installer program use depending on the options you selected (Alt or regular), so don't worry about that. Also understand that you can install/uninstall with different options whenever you want so as to have a look to what is changed/available. It will not hurt. Everything is reversible