• 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.

Missing Fencing / Blast Fencing

Messages
22
Country
england
Hi Russel,
I upgraded to R23 this morning. I am working on EGDG RAF St Mawgan. I had it almost finished in R22 with fencing around the perimeter and 3 lots of blast fencing. Whilst they show up fine in R23 they fail to show when compiled and run in FSX.
Re- other posts about sudden height changes. This was a problem in R22 which I overcame by manually editing the .xml and then compiling. It is still present in R23.
Tony
 
Hi Russel,
I upgraded to R23 this morning. I am working on EGDG RAF St Mawgan. I had it almost finished in R22 with fencing around the perimeter and 3 lots of blast fencing. Whilst they show up fine in R23 they fail to show when compiled and run in FSX.
Re- other posts about sudden height changes. This was a problem in R22 which I overcame by manually editing the .xml and then compiling. It is still present in R23.
Tony

I was working with an airport that I had added blast fences and
boundry fences to some time back.
I opened that BGL in FX Planner and created a XML file.

After adding taxiway signs and compiling the abridged file
I found the fences were missing even though they were
there in the XML file and were OK in the original BGL file.

I then ran the XML file through SDE and compiled it. The
fences were still missing. After several other attempts to
get the fences to shop up I finally arrived at a solution
that worked. I used the original file XML that had been
created with the fs92fsx utility and added in the fence XML
xod. Using that XML file as the "master", I cut & pasted my
additions into that file. It compiled OK and the fences were there.

The difference that I saw between the FX Planner XML and
the one that worked OK was the position in the file of
the Blast Fence and Boundry Fence XML code.

In the code that worked, the fences were the last items
prior to the </Airport> tag. In the versions that didn't
display the fences, the XML code was up near the begining
of the file, after some apron definitions.
Also, in the XML file created by FX Planner from the original
"working" BGL. the Blast Fences were listed prior to the
Boundry Fences. In the file that worked, the Boundry Fences
were defined first, then the Blast Fences, so there seems to
be a definite order that must be maintained.

Paul
 
Last edited:
That's interesting. I'll have to check that and see if I can duplicate your results. If so then I'll have to make the appropriate modifications to how the xml code is written out.

Thanks for the detective work!

-Russell
 
That's interesting. I'll have to check that and see if I can duplicate your results. If so then I'll have to make the appropriate modifications to how the xml code is written out.

Thanks for the detective work!

-Russell

If you can't duplicate my results I can send you my original
AFCAD file that I had converted to XML, added the fences
and compiled. This is the BGL file that was working OK and the
file I loaded into FsX Planner and subsewuently experienced
the "no fences" problem.

Paul ( will be AFK most of today however )
 
In the code that worked, the fences were the last items
prior to the </Airport> tag. In the versions that didn't
display the fences, the XML code was up near the begining
of the file, after some apron definitions.
Also, in the XML file created by FX Planner from the original
"working" BGL. the Blast Fences were listed prior to the
Boundry Fences. In the file that worked, the Boundry Fences
were defined first, then the Blast Fences, so there seems to
be a definite order that must be maintained.

Paul

That's an interesting observation.

By happenstance, I *always* put BoundaryFences as the last item in the whole file...never realizing that it might have an effect in the sim. But keep in mind that this is the order that Jon Masterson's decompiler uses...<BoundaryFence> last.

One thing about FSXPlanner that I do not like, is that it messes with my xml. I wish it simply wrote xml data in the exact same order as Jon uses in his BGL2XML decompiler. The order Jon uses seems to work 100%.

That is (roughly):

<ExclusionRectangles>
<SceneryObjects>
<Airport>
<Runway>...etc.
<Aprons>
<TaxiName>
<TaxiwayPath>
<TaxiwayParking>
<Jetway>
<TaxiwaySign>
<BoundaryFence>

I might have missed one or two sections like Approaches but suffice to say, that is the order Jon's decompiler uses and that is the order I always use, and that is the order than never fails me in FSX.

FSXPlanner is great. But one mild criticism I have is that FSXPlanner seems to change my nicely formatted xml all around and removes my comments <!-- which is not really what I want. For that reason, I make a dummy file for FSXPlanner to write to, then I cut and paste what code I need into my master xml file.
 
Back
Top