How to create easy airport because i don't know can anyone help

It seems to be working normally, but I haven't found the output file.

The output directory is a default folder in your FS 4 user directory. With me on the Mac it is here:

• '/Users/USERNAME/Library/Application Support/Aerofly FS 4/scenery/airports'

Quote from ApfelFlieger

The output directory is a default folder in your FS 4 user directory. With me on the Mac it is here:

• '/Users/USERNAME/Library/Application Support/Aerofly FS 4/scenery/airports'

Thank you. The problem has been perfectly solved. Next, I will try to do some basic things, such as the runway. Do you have any suggestions? (I'm redesigning for Beijing Daxing International Airport)

One more thing what is the material name of runway?

I have already published a demonstration for the TARMACS in my post #29.

For GROUNDTEXT and TAXISIGN I have revised the demonstration today and attach the file here as well.

I still recommend the FS 2 wiki, which still applies: https://www.aerofly.com/dokuwiki/doku.php/sdk:scenery

And my general recommendation is to proceed step by step. I still do it today despite all the experience with more than 2,000 airports of all kinds, that I program 1 element in the TAP, convert and look at the result. If that works, then I will start a series production.

EDIT:

I took the file out and will put an even more current variant here instead.

See post #67

Test OK

Here is the current version of my originally posted in Post #65 file for GROUNDTEXT and TAXISIGN. I have added:

1. value [none]
2. background TARMAC for better recognition of the individual GROUNDTEXT variants
3. new TARMAC [flatten]

Explanations:

to 1. [none]

I have observed that empty values in TAP files are increasingly no longer made with "[]" but with "[none]". Therefore, I have included this variant in the overview.

to 2. Background TARMAC

Above the light background with plate grid, the differences between the individual variants can be seen better.

to 3. New TARMAC [flatten]

Recently, the selection [flat] was added to the TARMACs. It is an invisible TARMAC that "only" has the task of leveling the entire surface. This is useful and necessary on an airfield so that the automatic heights work.

            <[tm_airport_pd_tarmac][element][]
                <[list_vector2_float64][points] [(-92.045400 1.626000)
                                                 (-92.045400 1.625200)
                                                 (-92.044600 1.625200)
                                                 (-92.044600 1.626000)
                                                 (-92.045400 1.626000)]>
                <[int32][level]                 [1]>
                <[string8][material]            [flatten]>
                <[string8][brightness]          []>
            >

My recommendations are:

• This TARMAC should get the level [1] and all other TARMACs should have higher levels.
• For most airfields, this TARMAC should cover the area within the fence around the airfield. This achieves that the surface inside the fence is as level as possible and that the outside the fence is elegantly nestled to the environment.

chrispriv has already been able to successfully test this effect at one of its airfields.

Good morning/afternoon, I would like to ask why the airport runway has some angular deviations from the real runway. Is there any way to fix it?

It will always remain a challenge that the IMAGES and AIRPORTS sometimes deviate from each other by a few centimeters to meters. And depending on the IMAGES used, these also differ for the same location.

There is a new line of code in the TAP files that at least allows you to move TAPs in parallel when converting:

                <[vector2_float64][offset][0 0]>

If there are wrong angles as in the photo, all that remains is to adjust the data of the runway in the try & error procedure.

Thank you for your method. I think it is related to the real magnetic direction of the runway. I checked the latest navigation map of ZBAD and entered the correct angle of the runway, and then it can perfectly solve the angle offset. Next, I want to learn how to make a taxiway. I tried some methods myself to copy and write all the coordinates of each taxiway into the <[list_vector2_float64][points] in the tap file. The taxiway written in this way is not smooth, but consists of polygons. I think it is a huge project if the edge of the input of the taxiway to keep the taxiway smooth. Is there any way to make the taxiway quickly, or only Airport Creat Tool can realise the quick and smooth taxiway? The following is the small airport I wrote myself (which includes the runway and the runway without line)

Taxiways are TARMACs and for TARMACs and LINEs, each corner point must be entered individually. For this input I have two more hints:

• To define curves, usually 4 coordinates (beginning and end as well as 2 points in between) are sufficient to get a round shape.
• In TARMACs, coordinates must not be inside the surface by mistake.

Quote from ApfelFlieger

Taxiways are TARMACs and for TARMACs and LINEs, each corner point must be entered individually. For this input I have two more hints:

• To define curves, usually 4 coordinates (beginning and end as well as 2 points in between) are sufficient to get a round shape.
• In TARMACs, coordinates must not be inside the surface by mistake.

I will try it thak you

I had started in the summer of 2025 to create a sample TAP file with all the information. Because of other activities, however, this was left behind.

As part of this thread, I will now finish this little by little. I enclose a current WIP version.

Wow, some models in xref can indeed enrich the airport environment. Thank you for your contribution.

The XREF list is getting much longer.

I have revised my documents for the creation and processing of AIRPORTS and POI.

This file contains the samples with explanations for the files 'ICAO.tap' and 'ICAO_addendum.tap' (TAP), 'icao.toc' (TOC) and 'icao.tsl' (TSL):

• FS4_ADDON_FILES__TAP_TSL_TOC__20260609.txt

AIRPORTS creation:

The creation of AIRPORTS takes place in 2 steps:

1. Input of all data in the text file 'ICAO.tap', for aircraft towing additionally 'ICAO_addendum.tap'.
2. Conversion of the TAP file(s) to compiled TSC and WAD files and, if necessary, TOC and/or TMB files.

Empty TAP files are attached:

• ICAO.tap.txt
• ICAO_addendum.tap.txt

POI creation:

The creation of POI takes place directly in the text files:

• ICAO.tsc.txt
• ICAO.toc.txt

Good luck - and have fun.

I wrote 2026-05-06 in the post #13:

Quote from ApfelFlieger

This is how the coordinates for a WAD file are converted ("GCS" = GeoCoordinatesSystem):

The tables for WINDOWS resp. MAC can help with the conversion.

Display More

Jan wrote 2026-07-23 in the post RE: Navdata coordinates to UID about the FS internal coordinate system:

Quote

The database doesn't use lat/lon it uses world grid units, that's Aerolfy's own coordinate system. Values range from 0 to 65536 in both directions easily tiling the entire world in square textures with a factor of 2. - So lat/lon 0,0 maps to 32768.0, 32768.0 in world grid. X maps to longitude linearly but Y has a tan() function in it. lon/lat (E/N) is in radians here.

And PCT has included the conversion since version 0.9.1:

I will briefly describe how quickly a heliport can be created with the help of the PCT.

EDIT:

With the PCT, all geo positions can be converted to the FS coordinate system.

Here is a guide to creating a HELIPORT with only functional characters (no objects) for the user folder '/... /Aerofly FS 4/scenery/airports'.

The IMAGES at "FL25 - HCA FLORIDA MERCY HOSPITAL" are still such in the FS 4 that the heliport can be guessed:

This is what the before-after comparison looks like:

Note: Apparently only "Mercy" is stored in the FS 4 internal database for FL25 as AIRPORT NAME. These cases occur again and again, although they can only be problematic when looking for an AIRPORT.

The individual steps take only a few seconds each.

The ZIP file contains the folder 'fl25' with the two files 'fl25.tsc' and 'fl25.wad'. In addition, a blank TSC and WAD files are included. In these, placeholders explaining between 2 underscores in the required input fields instead of the actual data.

INSTRUCTIONS:

• FS 4:
  - open FS 4
  - check that the airfield code "FL25" is still available (menu LOCATION)
  - close FS 4
• user folder '/.../Aerofly FS 4/scenery/airports':
  - create folder 'fl25'
  - copy file templates TSC and WAD
  - rename the templates in 'fl25.tsc' and 'fl25.wad'
  - open fl25.tsc' and 'fl25.wad' with a text editor
• PCT:
  - open PCT
  - zoom in the map to the desired map section
  - click on OBJECTS in the left column
  - enter "sh70" in the search (YELLOW MARKED)
  - activate (click) button "Sh70 Cga" (YELLOW MARKED)
  - position "Sh70 Cga" as desired in the map (YELLOW MARKED)
  - fold out (click) the display "FS4 internal (.wad)" in the right column (BLUE MARKED)
  
• text editor:
  - enter the data into the files 'fl25.tsc' and 'fl25.wad'
  -- RED: direkte Texteingabe
  -- GREEN: GREEN MARKED data from PCT
  -- BLUE: BLUE MARKED data from PCT
  - save both files
  
• FS 4:
  - open FS 4
  - choose Helicopter
  - choose AIRPORT "FL25"
  - FLY AND ENJOY

Here are two examples of heliports in the Netherlands, which were created as explained in the previous post. Both heliports also have XREF objects and show how you can use the XREF objects AIRPORT MAST as a helipad (lowering and scaling).

Now I am starting to understand this matter of the heliports 😃