Description of the issue: Airport Scenery (FSDreamteam LFSB) is no longer flat, huge steps on main taxiway. Till SU3 everything was fine, with SU4 the airport is no longer flat
Coordinates or location: FSDreamteam LFSB
Always
Start any Flight from LSFB, Check Taxiway B (southbound)
It would also be a good idea if you post about this on the FSDreamTeam forum. That way they can check it on their side as well.
I will post it on that forum as well. Just need to wait till my account is approved there…
I am not able to post on the other forum… 
Black Square’s “Real Taxiways” can cause this in a few airports. These airports should be disabled in Real Taxiways, to avoid the clash. I guess other programmes that impact on taxiways might have a similar effect on some airports. Of course, this might not be the problem at all …
It IS not Real Taxiways… 
Sorry I couldn’t help.
i guess it would have been more accurate to say that Real Taxiways sometimes “uncovers” this, rather than causes it; the fault would already exist in a particular airport, it just wouldn’t normally be visible.
Still the same with newest SU4 Beta 1.6.11.0
Anyone having same issue please leave a comment → if we get more comments, maybe the devs react to it too
SU4 1.6.13 → Still the same
A fix has been implemented in SU4 for that airport:
I have the France-VFR LFSB addon and see the same elevations issues than reported by OP. So 3rd party developers need to make some adjustments to their scene. It ahs been reported to France-VFR.
With the scene disabled, the terrain is flat.
Good find. Didn’r see it in the release notes
Still the same with 1.6.16.0
Posted also on Forum of FranceVFR (Needs a registered forum account to read):
Retours sur la compatibilité des scènes France VFR MSFS2020 sous MSFS2024 - Page 7 - Nouveau simulateur MSFS2024 - VFR Network - Forum
Don’t expect to get a fix in a Sim Update. Developers of the 3rd party airport need to adjust their scene based on the new terraforming data for LFSB so far available in SU4 and not the live version. So I assume they’ll publish a fix after SU4 release.
Good to know this is the case and hopefully it will be done as it’s unusable in its current state
