• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Putting it all together?

D

DougD

Messages
22
Country
canada
Just wondering if I have this right. I have completed the re-work of my local airport (tried starting from scratch but couldn't get the instrument approaches to work properly) and have a number of files.

I have the basic .bgl file created with FSX Planner; another .bgl file created with Whisplacer and 5 exclusion zone .bgl files created with FSX KML.

In total there are SEVEN (7) files for one airport. Does that seem right or is there some way to combine them into one master .bgl file?

Another question is the placement of the files in the Addon Scenery folder. I have attempted to create a folder to hold all the files for simple maintenance. Unfortunately FSX does not recognize the sub folder in the Addon Scenery folder. It will only 'see' them when placed individually into the Addon Scenery - Scenery folder.

Any help or thoughts on either of these two questions would be appreciated.
 
Hello

Personnally, I prefer to keep 3 bgl files:

- one for airport (ADE, AFX, FSX Planner, ...)
- one for scenery objects (IS, Whisplacer, ...)
- one for terrain (SBuilderX, FSX KML, ...)

SBuilder is more convenient for multiple lines, polygons.
However, if you have multiple kml files for every line or polygon you may merge those data in a single file before using in FSX KML; I don't know an automatic way, but with an editor you copy/paste all placemark blocks in the same kml file.

Pierrot - FMEP
 
Thanks for the help guys - I have been trying to merge the FSX KML files but I can't seem to find just the right spot to 'cut' or 'paste'.

I'll keep working on it though.
 
Meshman - thanks again - Yes they are all identical FSX KML files all excluding autogen objects.

The description used is: Airports_Backgrounds_MaskClassMap_ExcludeAutoGen in each file.

My problem is that sometimes I need to be lead by the hand to get things right. My cut and paste never seems to work:

I have included a copy of the text of one of the files here: Could you please indicate which part I cut and where I would place it in the next file to have them all work properly:

<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://earth.google.com/kml/2.2">
<Document>
<name>Sudbury-Radar-Base.kml</name>
<Style id="sn_ylw-pushpin_copy10">
<IconStyle>
<scale>1.1</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
<LineStyle>
<color>ff0000ff</color>
</LineStyle>
<PolyStyle>
<color>19ffffff</color>
</PolyStyle>
</Style>
<StyleMap id="msn_ylw-pushpin_copy10">
<Pair>
<key>normal</key>
<styleUrl>#sn_ylw-pushpin_copy10</styleUrl>
</Pair>
<Pair>
<key>highlight</key>
<styleUrl>#sh_ylw-pushpin_copy10</styleUrl>
</Pair>
</StyleMap>
<Style id="sh_ylw-pushpin_copy10">
<IconStyle>
<scale>1.3</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
<LineStyle>
<color>ff0000ff</color>
</LineStyle>
<PolyStyle>
<color>19ffffff</color>
</PolyStyle>
</Style>
<Placemark>
<name>Sudbury-Radar-Base</name>
<LookAt>
<longitude>-80.84384571358855</longitude>
<latitude>46.62658826565118</latitude>
<altitude>0</altitude>
<range>648.3005598507103</range>
<tilt>0</tilt>
<heading>5.842020081017863</heading>
<altitudeMode>relativeToGround</altitudeMode>
</LookAt>
<styleUrl>#msn_ylw-pushpin_copy10</styleUrl>
<Polygon>
<tessellate>1</tessellate>
<outerBoundaryIs>
<LinearRing>
<coordinates>
-80.84488455555501,46.62670986296985,0 -80.84523371757562,46.62651939189745,0 -80.84545886718516,46.62616600029333,0 -80.84553375200422,46.6257372486678,0 -80.84534700770561,46.625237839767,0 -80.844943149815,46.62503223214824,0 -80.84443552726272,46.62497775716971,0 -80.84390028534551,46.62505036710732,0 -80.84347402563473,46.62504674789928,0 -80.84305202082618,46.62509316117941,0 -80.84265250067239,46.6252093292012,0 -80.84223031887777,46.62537658054198,0 -80.84212557679749,46.62552977023082,0 -80.84208051280838,46.62582561521088,0 -80.8422592065576,46.62600330230579,0 -80.84235710095135,46.62613502894567,0 -80.84251194269363,46.62619196458932,0 -80.84251384259781,46.6263225391024,0 -80.84248003336555,46.62657969735967,0 -80.84248584217349,46.62685221747671,0 -80.84273363385096,46.62702509218014,0 -80.84323086018917,46.6270522913146,0 -80.84376870615191,46.62697917052391,0 -80.84418311102857,46.62690508380822,0 -80.84459628145436,46.62679287100748,0 -80.84488455555501,46.62670986296985,0 </coordinates>
</LinearRing>
</outerBoundaryIs>
</Polygon>
<description>Airport_Backgrounds_MaskClassMap_ExcludeAutoGen</description></Placemark>
</Document>
</kml>


*****
Thanks very much.

On another note - I also found that if remaking an airport, it is not necessary to put in all the information required for instrument approaches. The original information is retained (must be a separate file somewhere) and when cleared to an airport, one approach will be given.

However, if you choose to select a different approach, two of each available approaches are presented. They both work, it just looks really confusing.

And it would be especially nice if there was a tutorial on making approaches.
 
Hello

Ok! In your example, you keep the bold header,
You erase the red style block, keep the blue placemark block, and the bold final lines.
I think the blue italic Look at section can be erased; personnaly, I have not this section.
Then, in every kml file (open with notepad, don't double-click for GE!), just copy its whole Placemark block, then paste in first file.
You'll have all placemark blocks following each other.

===============
<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://earth.google.com/kml/2.2">
<Document>
<name>Sudbury-Radar-Base.kml</name>
===================
<Style id="sn_ylw-pushpin_copy10">
<IconStyle>
<scale>1.1</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
<LineStyle>
<color>ff0000ff</color>
</LineStyle>
<PolyStyle>
<color>19ffffff</color>
</PolyStyle>
</Style>
<StyleMap id="msn_ylw-pushpin_copy10">
<Pair>
<key>normal</key>
<styleUrl>#sn_ylw-pushpin_copy10</styleUrl>
</Pair>
<Pair>
<key>highlight</key>
<styleUrl>#sh_ylw-pushpin_copy10</styleUrl>
</Pair>
</StyleMap>
<Style id="sh_ylw-pushpin_copy10">
<IconStyle>
<scale>1.3</scale>
<Icon>
<href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
</Icon>
<hotSpot x="20" y="2" xunits="pixels" yunits="pixels"/>
</IconStyle>
<LineStyle>
<color>ff0000ff</color>
</LineStyle>
<PolyStyle>
<color>19ffffff</color>
</PolyStyle>
</Style>
===============================
<Placemark>
<name>Sudbury-Radar-Base</name>
<LookAt>
<longitude>-80.84384571358855</longitude>
<latitude>46.62658826565118</latitude>
<altitude>0</altitude>
<range>648.3005598507103</range>
<tilt>0</tilt>
<heading>5.842020081017863</heading>
<altitudeMode>relativeToGround</altitudeMode>
</LookAt><styleUrl>#msn_ylw-pushpin_copy10</styleUrl>
<Polygon>
<tessellate>1</tessellate>
<outerBoundaryIs>
<LinearRing>
<coordinates>
-80.84488455555501,46.62670986296985,0 -80.84523371757562,46.62651939189745,0 -80.84545886718516,46.62616600029333,0 -80.84553375200422,46.6257372486678,0 -80.84534700770561,46.625237839767,0 -80.844943149815,46.62503223214824,0 -80.84443552726272,46.62497775716971,0 -80.84390028534551,46.62505036710732,0 -80.84347402563473,46.62504674789928,0 -80.84305202082618,46.62509316117941,0 -80.84265250067239,46.6252093292012,0 -80.84223031887777,46.62537658054198,0 -80.84212557679749,46.62552977023082,0 -80.84208051280838,46.62582561521088,0 -80.8422592065576,46.62600330230579,0 -80.84235710095135,46.62613502894567,0 -80.84251194269363,46.62619196458932,0 -80.84251384259781,46.6263225391024,0 -80.84248003336555,46.62657969735967,0 -80.84248584217349,46.62685221747671,0 -80.84273363385096,46.62702509218014,0 -80.84323086018917,46.6270522913146,0 -80.84376870615191,46.62697917052391,0 -80.84418311102857,46.62690508380822,0 -80.84459628145436,46.62679287100748,0 -80.84488455555501,46.62670986296985,0 </coordinates>
</LinearRing>
</outerBoundaryIs>
</Polygon>
<description>Airport_Backgrounds_MaskClassMap_Excl udeAutoGen</description></Placemark>
================================

>>> insert Placemark block from each kml file

================================
</Document>
</kml>

==========

When opening this single file in FSX-KML, every line / poly will appear in the left-down part of window, and you may edit tags, ...
Hope it will work! Pierrot - FMEP
 
Last edited:
<DeleteAirport
deleteAllApproaches="TRUE"/>

Is a blocking statement and not a delete statement.

You do not need it

IF

you write a new approach for an exsiting or new runway. FS is smart enough to read all the approach data at the root APX and then add to any new approaches you write. In this way you leave all exsiting approach code in the stock APX bgl and FS adds to what is now in the FSXP bgl which you wrote.

Only when you need to edit the exsiting approaches do you bring ALL of them into your higher priority airport FSXP xml/bgl. This requires the deleteALL= so no approach code is read x2 and duplicated in the GPS/ATC menu window.

Duplication of any part of the airport data that is carried forward to a higher priority will cause a CTD somewhere in the 108 NM radius of the airport. It may only be on the cusp of one visual sector out of a total of nine rectangles when the CDT occurs so everyone may never see the problem unless they fly into that sector.



GE PLus

If you use this Utility (the GE Plus) then you can combine all your single KML's that GE makes for you into a single My Place folder. If you made 10 kml's with GE then make a new folder and drag them all into a single folder from the GE My Place folder tree.

Now copy that single KML My Place folder file (save as) over to FSX_KML and it will make a single cvx for you with all the GE KML's combined. In this way there is no manual edit of any data.
 
Last edited:
Hello,

Thanks for the info concerning merging of several kml files; very quick and easy.
I successed in recovering former separate kml files, even created with editor.

Unfortunately, I had many AB_flatten I used to rebuild streams, with overlapping tiles, first created in SCenGenX in API code, then converted to kml files.
I gather all files in a kml folder; every tile is correct, but no cvx is created; maybe overlapping flattens can't be compiled together?
All separate cvx (one for each elevation, step meter by meter) work.

Thanks for help.
Pierrot - FMEP
 
You must log in or register to reply here.
Back
Top