hervesors

I note that P3D is not dead here for many. This is good news. I am also happy with it (and sometimes even FSX) considering my simulator practice is mainly a substitute for real flying I do not practice anymore since a couple of years. I build my flight plans manually using available tools I previously used for planyfing real flights. I only use a few medium range piston or turboprop aircrafts (Baron 58 and PMDG B1900) and occasionally a high-performance business jet aircraft (Citation X from Carenado) I modified a bit for a more accurate handling, performance and fuel burn data. I prefer short duration flights (1-3 hours is enough for me) and perform all my flight (departure, cruise, intermediate and final approach) using current charts and updated navigational aids, usually at night or in poor weather conditions since it is the most challenging. An accurate ground scenery is not a priority for me and I usually exit the sim as soon as I successfully lande at destination. I don't have any addons (except Active Sky and FSUIPC) In the past I flew on IVAO and it was an interesting practice since it reenacted real ATC communications and instructions (at least when controllers were skilled). That's fine with me and P3D/FSX do a great job in this context.

Received today from the support team So, don't expect any missing features to be available soon..and maybe LIDO won't be the chart provider

Agree..nor was the discontinued Aerosoft NavDataPro, considering LIDO chart/data provider (Lufthansa) does not and probably will not cover these smaller airports.

In July, I also purchased a 1 year subscription. Three months after, I feel a bit disappointed - Despite being announced within 1-2 months, NavData are still unavailable, - Numerous airports are not included, even those with precision approach procedures, - Airport search is very impratical (only full ICAO code with no partial search nor any alphabetical order), - The developement team does not post news on their website, - Support emails are not answered, - And there's no place to ask questions, get information, discuss with users and make suggestions. If things stay the same, especially after AeroSoft LIDO charts and NavData are discontinued, I will certainly not renew.

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é