OUT of date navigation data
Posted: Fri Oct 13, 2017 12:34 am
This issue of out of date navigation data has been raised many times yet it seems LM wont do anything about it. Some are quite ready to say to users, update the navaids etc by yourself using some available files. Why should a user be forced to do this?
I am not talking about the 28 day AIRAC cycle data. I am talking about basic stuff like correct ICAO 4 letter designators (eg YBSU instead of YBMC which changed at least 7 years ago) and incorrect VOR/NDB/ILS frequencies. Also incorrect aerodrome layouts and runways (EDDF is a prime example).
This is especially relevant given LM market the product as a professional/training product. Yet there is still incorrect data in it and has been for years.
So LM how about updating this data? It surprises me that this wasnt even done for a brand new product such as P3D v4. If XPlane can manage it then surely LM can as well?
I am not talking about the 28 day AIRAC cycle data. I am talking about basic stuff like correct ICAO 4 letter designators (eg YBSU instead of YBMC which changed at least 7 years ago) and incorrect VOR/NDB/ILS frequencies. Also incorrect aerodrome layouts and runways (EDDF is a prime example).
This is especially relevant given LM market the product as a professional/training product. Yet there is still incorrect data in it and has been for years.
So LM how about updating this data? It surprises me that this wasnt even done for a brand new product such as P3D v4. If XPlane can manage it then surely LM can as well?