admin I have the same problem with RJ04. The flattening does not run as well as with AC3D:
To enter the height, I follow these steps:
- export tap file
- in the exported tap file enter the height by hand and save it
- delete the airfield in the tool
- import tap file again
This is also how I enter positions or orientations when I transfer them from FS2.tsc files. I also do it this way when creating military airfields with pixelated airfields - with success.
Display MoreTo enter the height, I follow these steps:
- export tap file
- in the exported tap file enter the height by hand and save it
- delete the airfield in the tool
- import tap file again
This is also how I enter positions or orientations when I transfer them from FS2.tsc files. I also do it this way when creating military airfields with pixelated airfields - with success.
That didn't really solve the Issue. See the attached Pictures below:
Unfortunately, my theory has not yet helped me in practice either. 
Some airports are difficult for the auto height method, especially if the elevation data around the airport changes a lot, for example a steep drop at the side of the runway. In this case the method might fail or produce suboptimal results. For example we use hand made airports for Madeira airport of Courchevel.
But the majority of airports should work fine, so we have to check and see why it fails in certain cases. Here it would help if you could provide us with a list of ICAO codes of airports created with our new web tool so we can take a look at it.
Here it would help if you could provide us with a list of ICAO codes of airports created with our new web tool so we can take a look at it
For me this would be TFFJ and TNCS. Thank you 
For me this would be:
- FR0053: 3 helipads on a slope
- FR0347: Runway only partially visible
- LF2921: Runway only partially visible
- LF2922: Runway only partially visible
- LF2923: runway only partially visible
- LFRL (still in preparation!): Asphalt partially not visible
And RJ04 for me.
I also have the issue with some airports, especially in hilly terrain, but sometimes also for quite flat terrain.
My workaround actually is to place smaller or larger holes at the border of the airport, a bit outside of where the problem with the mesh occurs.
e.g. for LSZI:
This works often with a bit of try on error.
Of course, it would be better if IPACS can fix the issue.
Cheers,
Christophe
