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

FSX Planner release 18 now available (June 25)

Messages
961
Hi all,

Release 18 of FSX Planner is now available. It can be downloaded at: http://www.zbluesoftware.com/clients/FSXPlanner.zip

Here are the details:

* Windsocks can now be added or edited. The tool for creating them is in the Navigation Toolbar.

* Exclusion Rectangles are now created by using the Exclusion Rectangle tool from the toolbar. You click and drag the create the rectangle. To modify the size of the rectangle after it is created you can either enter exact lat/lon coordinates into the Exclusion Rectangle properties display, or when using the exclsuon rectangle tool, you can click and drag a vertex. The Exclusion tab of the Prepare Options dialog is now no longer included as it has been replaced by this functionality.

* Apron Edge Lights were not being handled correctly. They were being loaded as individual points instead of as a string of lights. This has been fixed. Apron Edge Lights are now treated similarly to fences in that they consist of a series of vertices which are connected by a 'string.' They are midified in the same fashion as a fence. To create a new string of edge lights, select the Apron Edge Light tool and click where you want the first vertex to be, then click at the location of each additional vertex. Double click to end the string. If you hold down the shift key when double clicking the string of lights will be closed by adding an end vertex at the same location as the start vertex. To insert a vertex into an existing string of edge lights, select the apron edge light tool, then click on the string of edge lights to select them, then shift-click at the location on the string where you want to insert the new vertex. To delete a vertex, follow the same procedure, but control-click on the vertex to be removed.

* Modifyied the add taxiway tool so that holding the shift key down when you are creating the start or end point of the taxiway will allow you to insert the start or end point into the middle of an existing taxiway.

* The undo/redo/history functionality was not recording or undoing some of the runway details. This has been fixed and now all runway details are undoable.

* You can now specify whether or not the DeleteAirport information should be written to and/or read from the airport xml file. This option can be set in the preferences dialog and is on by default. This allows for xml source files shared between different users to maintain what parts of the airport should be deleted instead of just blindly setting all delete flags to true.

* There is a new preference option under the Option tab of the Preferences dialog which allows you to specify whether or not you want to read and write exclusion rectangles from/to the airport's xml file.

* Added error checks for ILSs without Idents; and taxiway points that have incorrect types or orientations.

* Added an error check for parking locations that don't have an appropriate Type assignment.

* Airports can now be printed. You can specify the size of the page, allowing you to print from a regular letter size sheet up to a huge banner size many feet across.

* The latitiude and longitude coordinates of a vertex associated with an Apron, Boundary Fence or Blast Fence are now displayed in the properties display when a specific vertex is click on during the editing process of the apron or fence. This allows for fine control over the exact placement of a vertex associated with the apron or fence.

* There is a new preference in the Preferences Dialog that allows you to specify if lines should be drawn between the vertices of an edge light string when it is not selected. This option is off by default.

* The Taxiway Names menu item has been moved to the Edit menu. The Lists menu has therefore been removed as it only had that one option under it.

* Improvements have been made to the Taxi Name dialog to make it easier to handle taxi names. In addition the default blank taxi name is now assigned properly to all new taxiways even if no taxi names have been created for the airport. Note this does not affect taxiways that are being copied or created by extending an existing taxiway.

* Cleaned up some of the UI to be more user friendly.



NOTE: There seems to be some sort of issue with exclusion rectangles. If they are too small they do not exclude anything. In my tests is seems that any rectangle less than about 25 seconds or so to a side does not exclude anything. Also it seems that they are not exact rectangles, almost as is flight simulator was rounding them off, which might explain the minimum size issue. Alternatively FSX Planner could be writting the xml incorrectly. If some people have time to test this and see what they find, that would be extremely helpful!

Thanks!
-Russell
 
2 Smalls bugs

Hi, Russel

I have found two small problems.

one is
in the Dialog Box "Taxiway Parking Data" in the ListBox "Name" the item "DOCK" is written "DOCK,"
and BglComp protests :)

second is

ERROR: <MissedApproachLegs
ERROR: >
ERROR: <Leg
ERROR: type = CI
ERROR: flyOver = FALSE
ERROR: turnDirection = L
ERROR: magneticCourse = 18.0
ERROR: altitude1 = 0.0M
ERROR: altitude2 = 0.0M
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2577:

ERROR: This LEG is missing some of this required part (00000801 00004801)
Missing: Time or Distance,
INTERNAL COMPILER ERROR: #C2031: Failed element parse <Leg>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

For MissedApproachLegs, Leg of type CI, Bglcomp refuses to compile but when i add
Distance = 0.0M after altitude2 it compile OK.

another but cosmetic
FSXPlanner cree a directory called Textures (with s)

Thank for your job.

Patrice.
 
Hi, Russel



second is

ERROR: <MissedApproachLegs
ERROR: >
ERROR: <Leg
ERROR: type = CI
ERROR: flyOver = FALSE
ERROR: turnDirection = L
ERROR: magneticCourse = 18.0
ERROR: altitude1 = 0.0M
ERROR: altitude2 = 0.0M
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2577:

ERROR: This LEG is missing some of this required part (00000801 00004801)
Missing: Time or Distance,
INTERNAL COMPILER ERROR: #C2031: Failed element parse <Leg>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:

For MissedApproachLegs, Leg of type CI, Bglcomp refuses to compile but when i add
Distance = 0.0M after altitude2 it compile OK.


Patrice.

Did you make any changes to the approach leg or did the above error happen wihout any changes being made to the approach?

-Russell
 
Not found the tool...

Hi, Russell

Hi all,

* Windsocks can now be added or edited. The tool for creating them is in the Navigation Toolbar.

Thanks!
-Russell

Forgive me, but I didn't find the tool to add windsock in the build18 toolbar.

Am I missing something?

Thanks,

José
 
Hi, Russell



Forgive me, but I didn't find the tool to add windsock in the build18 toolbar.

Am I missing something?

Thanks,

José

It should be there. View -> Navigation Toolbar to display the nav toolbar. Then it's the icon at the right side end of the toolbar.

-Russell
 
Leg of LFBO

Did you make any changes to the approach leg or did the above error happen wihout any changes being made to the approach?

-Russell

i use SDE for get the LFBO stock, with SDE, i save to xml
Add with hand apron for airbus factory,
Add with hand apron pour airbus delivery center,
compile with bglcomp (command line) compile OK

load in Fsxplanner for add parking (dock) and taxipath and now compile with Fsxplanner menu give the error message.

-- Test to reproduce the problem,

extract LFBO with SDE and save it to a xml file,
compile it with bglcomp, compile OK
open and compile the xml file without anything to modify with fsxplanner and compile KO


Patrice.
 
Last edited:
i use SDE for get the LFBO stock, with SDE, i save to xml
Add with hand apron for airbus factory,
Add with hand apron pour airbus delivery center,
compile with bglcomp (command line) compile OK

load in Fsxplanner for add parking (dock) and taxipath and now compile with Fsxplanner menu give the error message.

-- Test to reproduce the problem,

extract LFBO with SDE and save it to a xml file,
compile it with bglcomp, compile OK
open and compile the xml file without anything to modify with fsxplanner and compile KO


Patrice.


Can you post the xml file?

-Russell
 
As a comparison Russell I can confirm that the above Xml loads and compiles fine with the latest version of SDE TestApp
 
in the zip, the LFBO of FSX

Patrice.

Ok, I have identified the error. There was a bug that caused distances of zero not to be included in the xml. This has been fixed and will be included in the next release.

A temporary work around for now is to uncheck the Approaches option in the Prepare Options dialog.

-Russell
 
Ok, I have identified the error. There was a bug that caused distances of zero not to be included in the xml. This has been fixed and will be included in the next release.

A temporary work around for now is to uncheck the Approaches option in the Prepare Options dialog.

-Russell

Many thanks.

Patrice.
 
Russell,

Great job the one you are doing.

I have been during the last ten days with FSXPlanner. I have no previous experience with FS9 AFCAD tools. But I believe it's a great tool.
Build 18 has added some functionality to B17, I believed was to be left out of the ui.

I have been reworking SVMI airport and testing it with Ultimate Traffic for FSX, and have got a set of very closely real operations.

I wonder if it will really be possible to add multiple runways activation (parallel, near parallel and crosswind), as you mentioned in some other thread in this very same forum.:cool:

Jorge
 
Forgot to mention the needed exclusion of default jetways at SVMI worked great (B17).

And the third bug mentioned by Patrice--> "Textures" folder is created during compilation at the "Addon Scenery" FSX folder.

Jorge
 
Forgot to mention the needed exclusion of default jetways at SVMI worked great (B17).

And the third bug mentioned by Patrice--> "Textures" folder is created during compilation at the "Addon Scenery" FSX folder.

Jorge

The Textures (with an s) bug has been fixed for the next release.
 
Back
Top