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

New version of FSX Planner available (May 7)

R

rf360m

Messages
961
The lastest build of FSX Planner is now available here: http://www.zbluesoftware.com/clients/FSXPlanner.zip

The following is a list of the major updates in the release:
* Can now add and remove vertices for aprons and boundary fences. Right clicking when using the apron or boundary fence tool provides add and delete verions of the tool, which allow you to add or remove vertices respectively.
* Added option to display airport test radius
* Fixed bug where surface color preferences were not saved
* Fixed bug were your could not assign Gate_A throught Gate_Z option to parking spaces
* Can now create, edit and delete Blast Fences.
* Can now add and remove vertices for blast fences. Right clicking when using the blast fence tool provides add and delete verions of the tool, which allow you to add or remove vertices respectively.
* Can now create, edit and delete Jetways.

The Read Me file contains full details.

Enjoy, and please let me know if you find anything that doesn't work properly.
 
NICE work!!! love that now when u edit the gate info the gate doesnt automaticaly go to parking.

also can u possibly add a feature to be able to select more than one gate at once. so u can add codes to multiple gates at once.

thanks in advance. this is update is a major step foward!!
 
here are some error messages that i get with the newer version

i dont know what they all mean, but some say taxiways, and i didnt change anything with the taxi ways.


Parsing document: KPHX.xml

INTERNAL COMPILER ERROR: #C2033: XML Parse Error (line, column, error)

ERROR: 2139, 281, minInclusive constraint failed.

The attribute: 'name' has an invalid value according to its data type.

INTERNAL COMPILER ERROR: #C2425: Negative numbers are not allowed!
INTERNAL COMPILER ERROR: #C2031: Failed element parse <TaxiwayPath>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: airportTestRadius = 5000.0M
ERROR: alt = 345.95M
ERROR: city = Phoenix
ERROR: country = United States
ERROR: ident = KPHX
ERROR: lat = 33.4342778474092
ERROR: lon = -112.011583596468
ERROR: magvar = -12.0
ERROR: name = Phoenix Sky Harbor Intl
ERROR: state = Arizona
ERROR: trafficScalar = 0.7
ERROR: >
ERROR: <TaxiwayPath
ERROR: centerLine = FALSE
ERROR: centerLineLighted = FALSE
ERROR: drawDetail = TRUE
ERROR: drawSurface = TRUE
ERROR: end = 801
ERROR: leftEdge = NONE
ERROR: leftEdgeLighted = FALSE
ERROR: name = -1
ERROR: rightEdge = NONE
ERROR: rightEdgeLighted = FALSE
ERROR: start = 308
ERROR: surface = ASPHALT
ERROR: type = VEHICLE
ERROR: weightLimit = 0
ERROR: width = 15.0M
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2033: XML Parse Error (line, column, error)

ERROR: 2140, 281, minInclusive constraint failed.

The attribute: 'name' has an invalid value according to its data type.

INTERNAL COMPILER ERROR: #C2425: Negative numbers are not allowed!
INTERNAL COMPILER ERROR: #C2031: Failed element parse <TaxiwayPath>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: airportTestRadius = 5000.0M
ERROR: alt = 345.95M
ERROR: city = Phoenix
ERROR: country = United States
ERROR: ident = KPHX
ERROR: lat = 33.4342778474092
ERROR: lon = -112.011583596468
ERROR: magvar = -12.0
ERROR: name = Phoenix Sky Harbor Intl
ERROR: state = Arizona
ERROR: trafficScalar = 0.7
ERROR: >
ERROR: <TaxiwayPath
ERROR: centerLine = FALSE
ERROR: centerLineLighted = FALSE
ERROR: drawDetail = TRUE
ERROR: drawSurface = TRUE
ERROR: end = 797
ERROR: leftEdge = NONE
ERROR: leftEdgeLighted = FALSE
ERROR: name = -1
ERROR: rightEdge = NONE
ERROR: rightEdgeLighted = FALSE
ERROR: start = 798
ERROR: surface = ASPHALT
ERROR: type = PARKING
ERROR: weightLimit = 0
ERROR: width = 15.0M
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2033: XML Parse Error (line, column, error)

ERROR: 2142, 274, minInclusive constraint failed.

The attribute: 'name' has an invalid value according to its data type.

INTERNAL COMPILER ERROR: #C2425: Negative numbers are not allowed!
INTERNAL COMPILER ERROR: #C2031: Failed element parse <TaxiwayPath>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: airportTestRadius = 5000.0M
ERROR: alt = 345.95M
ERROR: city = Phoenix
ERROR: country = United States
ERROR: ident = KPHX
ERROR: lat = 33.4342778474092
ERROR: lon = -112.011583596468
ERROR: magvar = -12.0
ERROR: name = Phoenix Sky Harbor Intl
ERROR: state = Arizona
ERROR: trafficScalar = 0.7
ERROR: >
ERROR: <TaxiwayPath
ERROR: centerLine = FALSE
ERROR: centerLineLighted = FALSE
ERROR: drawDetail = TRUE
ERROR: drawSurface = TRUE
ERROR: end = 0
ERROR: leftEdge = NONE
ERROR: leftEdgeLighted = FALSE
ERROR: name = -1
ERROR: rightEdge = NONE
ERROR: rightEdgeLighted = FALSE
ERROR: start = 0
ERROR: surface = ASPHALT
ERROR: type = TAXI
ERROR: weightLimit = 0
ERROR: width = 15.0M
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2033: XML Parse Error (line, column, error)

ERROR: 2143, 278, minInclusive constraint failed.

The attribute: 'name' has an invalid value according to its data type.

INTERNAL COMPILER ERROR: #C2425: Negative numbers are not allowed!
INTERNAL COMPILER ERROR: #C2031: Failed element parse <TaxiwayPath>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: airportTestRadius = 5000.0M
ERROR: alt = 345.95M
ERROR: city = Phoenix
ERROR: country = United States
ERROR: ident = KPHX
ERROR: lat = 33.4342778474092
ERROR: lon = -112.011583596468
ERROR: magvar = -12.0
ERROR: name = Phoenix Sky Harbor Intl
ERROR: state = Arizona
ERROR: trafficScalar = 0.7
ERROR: >
ERROR: <TaxiwayPath
ERROR: centerLine = FALSE
ERROR: centerLineLighted = FALSE
ERROR: drawDetail = TRUE
ERROR: drawSurface = TRUE
ERROR: end = 568
ERROR: leftEdge = NONE
ERROR: leftEdgeLighted = FALSE
ERROR: name = -1
ERROR: rightEdge = NONE
ERROR: rightEdgeLighted = FALSE
ERROR: start = 568
ERROR: surface = ASPHALT
ERROR: type = TAXI
ERROR: weightLimit = 0
ERROR: width = 15.0M
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=985> <column=53>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=1060> <column=54>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=1065> <column=54>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=1070> <column=54>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=1075> <column=54>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=1080> <column=54>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=1085> <column=54>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=1090> <column=54>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=1095> <column=52>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=1100> <column=52>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=1105> <column=52>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=1110> <column=52>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=1115> <column=52>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!
INTERNAL COMPILER ERROR: #C2607: Compilation errors detected, compilation failed!


Parse complete!
 
Last edited:
bkircher said:
here are some error messages that i get with the newer version

i dont know what they all mean, but some say taxiways, and i didnt change anything with the taxi ways.


Parsing document: KPHX.xml

INTERNAL COMPILER ERROR: #C2033: XML Parse Error (line, column, error)

ERROR: 2139, 281, minInclusive constraint failed.

The attribute: 'name' has an invalid value according to its data type.

INTERNAL COMPILER ERROR: #C2425: Negative numbers are not allowed!
INTERNAL COMPILER ERROR: #C2031: Failed element parse <TaxiwayPath>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: airportTestRadius = 5000.0M
ERROR: alt = 345.95M
ERROR: city = Phoenix
ERROR: country = United States
ERROR: ident = KPHX
ERROR: lat = 33.4342778474092
ERROR: lon = -112.011583596468
ERROR: magvar = -12.0
ERROR: name = Phoenix Sky Harbor Intl
ERROR: state = Arizona
ERROR: trafficScalar = 0.7
ERROR: >
ERROR: <TaxiwayPath
ERROR: centerLine = FALSE
ERROR: centerLineLighted = FALSE
ERROR: drawDetail = TRUE
ERROR: drawSurface = TRUE
ERROR: end = 801
ERROR: leftEdge = NONE
ERROR: leftEdgeLighted = FALSE
ERROR: name = -1
ERROR: rightEdge = NONE
ERROR: rightEdgeLighted = FALSE
ERROR: start = 308
ERROR: surface = ASPHALT
ERROR: type = VEHICLE
ERROR: weightLimit = 0
ERROR: width = 15.0M
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2033: XML Parse Error (line, column, error)
Click to expand...

Ah, I think I know what that means. It should be an easy fix, so next build should have fix this bug. Thanks for finding it!
 
no problem!! i figured i post what errors i have since u said report anything wrong. glad i could help!! also do u think u could enable a feature that would let u select more than one gate at once?
 
These errors:

INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=985> <column=53>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!

result from having a jetway that is associated with a non existant parking spot. I will add an error checking component to help make it easier to find these errors.

So this error isn't a bug in the traditional sense. Once we add the error checking, though, it will be easier to find things like this that will prevent the xml file from compiling.
 
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=985> <column=53>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!


i dont know what that is all about because i havent deleted any parking spots or changed any parking locations. i have added one gate that does not need a jetway but that is it. for the rest of the gates i have added parking codes and resized the gate radius and that is all i have done to the afcad
 
bkircher said:
INTERNAL COMPILER ERROR: #C2434: Could not find parking spot for jetway! <line=985> <column=53>
INTERNAL COMPILER ERROR: #C2441: Failed to generate jetway binary!


i dont know what that is all about because i havent deleted any parking spots or changed any parking locations. i have added one gate that does not need a jetway but that is it. for the rest of the gates i have added parking codes and resized the gate radius and that is all i have done to the afcad
Click to expand...

I suppose the xml file being generated from the bgl file could have some mistakes in it when it comes to Jetways. Then if you just opened the xml file and tried to compile it without making any changes the above errors would occur.

Hopefully the error checking that we'll implement will help find and solve issues like this within the airport.
 
Golf-HotelDelta said:
Aha, so it's Jon's fault, is it :p
Click to expand...

Quite possibly - many things are :) However I have not had any problems decompiling and compiling Jetways with SDE so far. Another possibility to check is that the latest version of bglcomp.xsd is being used. The original one shipped with the SDK certainly throws out boundary fences.
 
i have added one gate that does not need a jetway but that is it. for the rest of the gates i have added parking codes and resized the gate radius and that is all i have done to the afcad
Click to expand...

Which gate did you add?

The main/ easiest error with Jetways is the association with a gate.

You cannot have two "Gate A 1" on the airport if "Gate A 1" is associated with a jetway.

A jetway without an associated gate will cause an error.

Frankly, I see this as a huge learning curve and error checking issue.

People are used to renaming groups of Gates and having to check each gate number and it's reference to any jetways is going to be more work than many will want to do.
 
I think I found it:

<Jetway gateName="GATE" parkingNumber="10">
<SceneryObject alt="0.0M" altitudeIsAgl="TRUE" bank="0.0" heading="358.59924" imageComplexity="DENSE" lat="33.4335948899388" lon="-112.014090567827" pitch="0.0">
<LibraryObject name="{bfcdf52b-9142-415c-8318-03c1b92ca9d9}" scale="1.0"/>
</SceneryObject>
</Jetway>
Click to expand...

<TaxiwayParking airlineCodes="UALX" heading="28.0" index="26" lat="33.435173034668" lon="-112.011826336384" name="GATE" number="10" pushBack="RIGHT" radius="18.0M" teeOffset1="7.9248" type="GATE_SMALL"/>
Click to expand...

<TaxiwayParking airlineCodes="COA" heading="80.95" index="75" lat="33.4334886074066" lon="-112.014393210411" name="GATE" number="10" pushBack="BOTH" radius="22.0M" teeOffset1="7.9248" type="GATE_MEDIUM"/>
Click to expand...
 
In your file I see the following gates associated with Jetways:

GATE 10 - 2 instances
GATE 4 - 2 instances
GATE 5 - 2 instances
GATE 6 - 2 instances
GATE 7 - 2 instances

I do not see the following parking spots which need to be present because there are Jetways associated with them. There are 13, and there are 13 errors in the post above:

<Jetway gateName="GATE_C" parkingNumber="10">
<Jetway gateName="GATE_G" parkingNumber="104">
<Jetway gateName="GATE_G" parkingNumber="105">
<Jetway gateName="GATE_G" parkingNumber="106">
<Jetway gateName="GATE_G" parkingNumber="107">
<Jetway gateName="GATE_G" parkingNumber="108">
<Jetway gateName="GATE_G" parkingNumber="109">
<Jetway gateName="GATE_G" parkingNumber="110">
<Jetway gateName="GATE_N" parkingNumber="2">
<Jetway gateName="GATE_N" parkingNumber="4">
<Jetway gateName="GATE_N" parkingNumber="5">
<Jetway gateName="GATE_N" parkingNumber="6">
<Jetway gateName="GATE_N" parkingNumber="7">

At large airports keeping track of Jetways and associated gates is going to be a HUGE pain in the rear.
 
Last edited:
No, not Jon's fault. :)

I am going to add an error checker which will look for things like Jetways associated with missing gates, to help find and fix errors like this as easily as possible.
 
In your file I see the following gates associated with Jetways:

GATE 10 - 2 instances
GATE 4 - 2 instances
GATE 5 - 2 instances
GATE 6 - 2 instances
GATE 7 - 2 instances

I do not see the following parking spots which need to be present because there are Jetways associated with them. There are 13, and there are 13 errors in the post above:

<Jetway gateName="GATE_C" parkingNumber="10">
<Jetway gateName="GATE_G" parkingNumber="104">
<Jetway gateName="GATE_G" parkingNumber="105">
<Jetway gateName="GATE_G" parkingNumber="106">
<Jetway gateName="GATE_G" parkingNumber="107">
<Jetway gateName="GATE_G" parkingNumber="108">
<Jetway gateName="GATE_G" parkingNumber="109">
<Jetway gateName="GATE_G" parkingNumber="110">
<Jetway gateName="GATE_N" parkingNumber="2">
<Jetway gateName="GATE_N" parkingNumber="4">
<Jetway gateName="GATE_N" parkingNumber="5">
<Jetway gateName="GATE_N" parkingNumber="6">
<Jetway gateName="GATE_N" parkingNumber="7">

At large airports keeping track of Jetways and associated gates is going to be a HUGE pain in the rear.
Click to expand...

ya i saw this yesterday. on terminal 2 and 3

but this was a default error. i think ill have to add a letter designator to one of the terminals even tho that doenst exist in the real airport

also is there going to be a way to possible lock the jetway to the gate so u dont have to do any renaming twice or anything more than once? or have the jetways properties update automaticaly when u edit the name to the gate. or something to that effect.
 
Last edited:
I did a fresh decompile of the APX18200.bgl file and compared it to the file posted above with BGLAnalyzeX.

The default airport has no duplication of gate names/ parking spot names.

The default airport also has jetways assigned to all the 13 gates listed above.

If you did not change those gate designations - then we need to look at the program you used to create the xml file.
 
bkircher said:
also is there going to be a way to possible lock the jetway to the gate so u dont have to do any renaming twice or anything more than once? or have the jetways properties update automaticaly when u edit the name to the gate. or something to that effect.
Click to expand...

Very good idea! We'll add that.
 
You must log in or register to reply here.
Back
Top