Some time ago, EYND changed the ICAO code of the airport to EYNI, but MSFS has yet to update this change. However, Navigraph already uses the EYNI airport code, which means a new airport is generated with different data. This results in Nida airport being unusable as the tiny “apron” has a large collision box over it and there are duplicate runways present
I’m happy to manually exclude EYNI from the navdata myself, but I’ve not one idea how. Taking EYNI out of the navdata for the time being until MSFS updates to the correct ICAO code would be preferred, though
Hi,
Thank you for contacting us. Unfortunately, there is no simple solution for that. We use real-world data in the sim, too (not just in our flight planner), not satellite imagery or pseudocode.
There is currently no way to change MSFS ICAO codes to the correct ones; this is a technical limitation, besides a copyright issue.
I am sorry - enjoy your weekend
Richard
I see. I suppose there’s also no easy way for me to manually exclude it myself, even through a custom addon?
No, for us, the reference can only be the stock data, because we don’t know which 3rd-party is installed and which isn’t.
Also, when you install a 3rd-party scenery, you will see the glitch. I am sorry.
Cheers
Richard
I see, no worries at all, thank you for the information regardless, going to hope Asobo gets around to fixing this eventually
No probs …
Yes, that is also a point for me that I don’t understand: why they can’t sync the data between their flight planner and the sim, because the MSFS Flightplanner uses the correct codes, the correct runway identifiers - but not the sim scenery…
Cheers
Richard