• 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 9th)

R

rf360m

Messages
961
The latest version of FSX Planner is now available at http://www.zbluesoftware.com/clients/FSXPlanner.zip

Here are the changes:
* Added ability to specify whether jetways should be updated along with parking locations.
* Added ability to specify how many undo items should be stored in the history. The default is 30.
* Redesigned color preferences to allow for more colors to be specified, including the background latitude/longitude lines.
* Implemented the Clean Up Aprons and Clean Up Fences functionality. This finds and removes aprons and fences which consist of two or one vertices respectively.
* Implemented Error Checking. This scans the airport for items that will cause errors during compilation, such as duplicate parking locations or jetways with out associated parking locations.
* Updated the display of parking locations to provide different graphics for airplane, vehicle and fuel parking locations.

Comments are welcome and encouraged. Thanks!
 
the auto thing works pretty well. what i am talking about for the color coating, is to have like americans code=aal to be colored red, and america west be dark blue or something like that

love the erro checking tool!!! that is great. makes it more stupid proof!
 
Last edited:
here is the latest error that i get. pretty simple. i says this no matter what i change the gate number to


Parsing document: KPHX.xml

INTERNAL COMPILER ERROR: #C2447: Duplicate jetway detected at airport! (parking=16) (gate=GATE_E) [XML line=650 column=53] [XML line=645 column=53]
INTERNAL COMPILER ERROR: #C2447: Duplicate jetway detected at airport! (parking=16) (gate=GATE_E) [XML line=655 column=53] [XML line=645 column=53]
INTERNAL COMPILER ERROR: #C2447: Duplicate jetway detected at airport! (parking=16) (gate=GATE_E) [XML line=660 column=53] [XML line=645 column=53]
INTERNAL COMPILER ERROR: #C2447: Duplicate jetway detected at airport! (parking=16) (gate=GATE_E) [XML line=985 column=53] [XML line=645 column=53]


Parse complete!
 
bkircher said:
here is the latest error that i get. pretty simple. i says this no matter what i change the gate number to


Parsing document: KPHX.xml

INTERNAL COMPILER ERROR: #C2447: Duplicate jetway detected at airport! (parking=16) (gate=GATE_E) [XML line=650 column=53] [XML line=645 column=53]
INTERNAL COMPILER ERROR: #C2447: Duplicate jetway detected at airport! (parking=16) (gate=GATE_E) [XML line=655 column=53] [XML line=645 column=53]
INTERNAL COMPILER ERROR: #C2447: Duplicate jetway detected at airport! (parking=16) (gate=GATE_E) [XML line=660 column=53] [XML line=645 column=53]
INTERNAL COMPILER ERROR: #C2447: Duplicate jetway detected at airport! (parking=16) (gate=GATE_E) [XML line=985 column=53] [XML line=645 column=53]


Parse complete!
Click to expand...


It seems that you have four different jetways associated with the same gate. I'll have to add an error check for that too.

How are you changing the gate? By modifying it at the jetway or at the parking location?
 
i figured out the problem before u posted. that was my error that i over looked. but for me i have to change the gate number both ways because for me the auto update thing wasnt really working for me. do u have to press enter everytime u change something? it seems to be working now, but it wasnt when i was changing the terminal 3 numbers. also what on the jetway menu does the desne and sparse and extremly dense mean?
 
bkircher said:
i figured out the problem before u posted. that was my error that i over looked. but for me i have to change the gate number both ways because for me the auto update thing wasnt really working for me. do u have to press enter everytime u change something? it seems to be working now, but it wasnt when i was changing the terminal 3 numbers. also what on the jetway menu does the desne and sparse and extremly dense mean?
Click to expand...

The dense, sparse, etc, options on the Jetways are what scenery density setting the user has to have for that jetway to be seen.

You shouldn't have to press enter or anything when you change the gate name of number. It should just record it and, if you have the option for updating jetways selected it will then look for a jetway associated with that gate and update it as well.
 
also can u add a feature that when u change a gate from small to medium, that it increase the gate radius? like a small as a 20 then a meduim as like a 25-30 etc....
and a feature that if u accidentaly move the tarmac or what ever that there is an undo key for that.
 
Last edited:
bkircher said:
also can u add a feature that when u change a gate from small to medium, that it increase the gate radius? like a small as a 20 then a meduim as like a 25-30 etc....
and a feature that if u accidentaly move the tarmac or what ever that there is an undo key for that.
Click to expand...

Another interesting idea! We'd have to decide what are 'defaul' or standard sizes for gates. These would be user customizable of course.
 
what i am talking about for the color coating, is to have like americans code=aal to be colored red, and america west be dark blue or something like that
Click to expand...

This would also fall under the heading of a User having the time to research a Parking Spec txt sheet and also updating it for everyone on a timely basis.

Lee gave us the ability in AFCAD to add a txt file with standard colors for all Airlines, GA, Military and Cargo but left it to user groups to develop the list.

At present, the last txt file that Graham Jackson put together for everyone using AFCAD has over 6,400 different Airline ICAO codes that matched a color. This list also included GA, Military and Cargo.

This type special coding follows the same principle of asking for different size parking spots.

Another interesting idea! We'd have to decide what are 'defaul' or standard sizes for gates.
Click to expand...

There are 7 standard sizes that FSX uses for different type parking spots. A group is working with Jon on developing a standard that enhances the 7 sizes that FSX uses.

If there is going to be more then one type of Airport design program available there should also be some areas that are consistant or we will have a mess when someone uploads a redesigned Airport based on who's utility was used.
 
jvile said:
There are 7 standard sizes that FSX uses for different type parking spots. A group is working with Jon on developing a standard that enhances the 7 sizes that FSX uses.

If there is going to be more then one type of Airport design program available there should also be some areas that are consistant or we will have a mess when someone uploads a redesigned Airport based on who's utility was used.
Click to expand...

I agree that all airport design applications should be able to read airports designed in any other tool. But I would also think that this is a given as each airport has to work within FSX, which has certain requirements. So if you can read an FSX airport you'd be fine.

I'm not sure about having more than the standard 7 FSX sizes for parking spaces though. Unless you actually modify FSX to display more than those 7 sizes I'm not sure of the benefit of having more sizes within an airport editor.

As for colors I think I'd let the user decide what colors they want to use for each airline code. Depending on what they use FSX Planner for they may onlt have 10 or so airline codes that they use all the time. So I don't think you need a universal standard for that, but rather a user defined one.
 
You must log in or register to reply here.
Back
Top