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

Progress Update

Messages
961
Hi all,

It's been a while since I've posted anything about the next version of FSX Planner. There have been many projects that have taken time away from working on the next version of the application. However, work has been started on the next version and has been going on for a little while now as we have had more time to devote to the next version.

We have a very high target for this next version, and want to make sure it meets those goals. I don't want to specify a release date because we're not sure exactly how long it will take to make everything work the way we want it to. Rest assured we are working as fast as possible on it.

There should be a lot of new functionality in the next version; some features that have been requested as well as some that will be brand new, and we hope very exciting. I can't say much more than that at this point, except that we have been working hard on multi core support and 64 bit support. If we can get things optimized as we hope then that should allow us to do some very cool thinigs which would not have been realistically possible otherwise.

That's it for now. Thanks to everyone for your ideas and support, and of course for using FSX Planner.

-Russell
 
Vista 64

Hi Russell,

Just to let you know, I have been using FSX Planner r28 quite successfully on my Vista 64-bit machine since build 28 came out. It is a great program and I have recommended it in other FS forums.

The only problem I have encountered is the initial install of the program. Vista 64-bit does not always believe you when you tell it the path to install. ;-)

Thanks,

Tim (FlyGuy)
 
Last edited:
Thanks for the tip on the install. We'll be sure to test that and fix any issues we find.

I'm also glad that FSX Planner is working so well for you. :)

-Russell
 
IFR Approach

I found another problem when compiling airports in FSXP. If you have IFR approaches to any airport, and one of the missed approach legs is of the type "VR," then, when compiling, it shows an error saying that there are parts in that leg that are not allowed. It also gives the part that is extra, which is "Rho." After looking at the help file given in the SDK, I found out that "Rho" is distance. I also found out how to fix it using an XML Editor, such as Notepad: Change "Rho" to "Theta," and remove the "M" or "N" that appears at the end of the line. After making that change, the file compiles if you don't use FSXP. If you try to use FSXP to fix the problem, in any approach that is type "VR", you have to uncheck "Distance." However, it will stay checked, therefore resulting in the compiler giving an error. I have included an example with 2 versions: FSXP, and mine. Plase look into this and fix the problem.

Also, FSXP has helped me soooo much in editing airports and assigning parking codes to parking spots. Thank you for creating this editor!:)
 

Attachments

Taxiway Signs

I noticed another problem. When importing an airport, there are 2 taxiway signs, one on top of another. Is this a FSXP problem or is it that way in the .bgl file?
 
I noticed another problem. When importing an airport, there are 2 taxiway signs, one on top of another. Is this a FSXP problem or is it that way in the .bgl file?

Which airport is this? It is possible to have this happen if the bgl you are opening is a previously modified airport, one for which the person who modified it did not delete the existing taxiway signs. This would create two taxiway signs for every sign, and FSX Planner would then display both of them.

-Russell
 
When you use "Find Airport BGL" to load KABQ (Albuquerque Intl Sunport), the version made by Microsoft, and you click on any taxiway sign, you will see that the outline is thinner than usual. For example, at the intersection of runways 12-30 and 17-35, click on the 2nd taxiway sign from the intersection on runway 35. You will see that the taxiway sign says that you are at the intersection of runway 30-12. However, the outline is not as bold as usual. If you move the sign, you will see another sign in the place the 1st sign was. The heading, label, justification, and size are the same, so its not a back-to-back sign. It seems this applies to most, if not all, of the signs in the airport.

I have included 2 pictures of the taxiway sign in a zip file. The first one is the sign on top of another sign. The 2nd one is the sign moved to the side to reveal the sign underneath.
 
Last edited:
Back
Top