I’m trying to figure out what happened to the airport data on SU2. It has taken a massive regression.
When 2024 launched the smaller airports almost looked like they were hand made. Now I’m seeing more mess than in 2020.
Has there been any word on what changed. Are they using a different database?
I fly out of KFFC a lot in the sim and its literally unusable in 2024. The runway is a death trap and the ramps are literally hills
@Michail71
Do you have any specific examples that you could provide?
Why not report this?
I’m not sure I’d report beta regressions to the tracker - I think the elevation issues encountered in the beta have their own thread. If they become part of the production, then all bets are off.
Also, it would really suck if everything changed for the worse between versions because all the things that have been catalogued would need to be audited again.
There is clearly an issue at KFFC, though this is the 1st time I’ve been there so can’t say if it is a new bug or regression:
The NX cub could probably handle this. Not sure about a Boeing or Airbus:
This is by the windsock circle:
This may be related to this bug-logged issue (I’m not a developer so could be totally wrong), reported prior to SU2:
Because I thoroughly enjoy XP12 about 100 times more than I do any of the MSFS products so It almost feels like a waste of time
Here’s some examples:
I have this horrible feeling that this is going to be what ends up in the release of SU2. It has all the makings of “one of those bugs” that gets reported in a beta, doesn’t get any attention, and then we live with it forever.
These are airports I frequent, and all three are jacked.
Why can’t we have nice things?
Agree, this one really worries me as well. This can be an absolute game-breaker at many airports.
Hi all,
This issue has already been logged via the Community Team in the thread linked by @NixonRedgrave, and has been reported on the MSFS Dev Forums separately, which has already been bug-logged on that specific platform.
I’ll make sure to update the Feedback Item linked above with the relevant information from the Dev Forums to check on the status of this! 
Update at 13:30 UTC: I’ve now ensured the forum thread linked above has been updated with the bug-logged tag, and have made the development team aware that this issue has not yet been resoled
Thanks
The MSFS Team
Most seem to be complaining about elevation issues. But in addition to that, I’m seeing what had been rendered near perfect to real as far as airport lighting, approach lighting, taxiway naming, runway numbering, and signs not matching runway numbers.
For instance, I’m seeing different sized taxi signs on hold pairs. Random placements of taxi signs that make no sense, way too many signs randomly scattered around, etc.
My home airport, KLNA, is really bad. Even the runway numbers are wrong. I did make a bug report, but it didn’t get any traction.
I know it had been good as I published a community version for 2020. When 2024 came I didn’t think there was much more I needed to do so opted to not port it over. I may have to now.
Prior to SU2 it looked hand crafted, everything was just right (except for missing beacon).
I’ve just posted to your bug topic:
It is pretty bad - I’d not want to be trying to taxi around Palm Beach County Park (KLNA) on a foggy day in real life with the signs as they are currently placed & marked in the sim! 
It’s especially strange since at launch the AI rendering of the airport was near perfect.
