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

R22 Bugs

Messages
41
Country
us-arizona
* It seems that FSXPlanner is changing the runway and pattern altitudes to huge numbers after clicking on a runway, causing compile errors or, if the number was accepted by the compiler, mountains on runways.

* Using the zoom tool with an object selected also not only zooms, but also moves the object to wherever the zoom tool was clicked.

* Deleting an apron vertex deletes the entire associated apron.

* Adding vertices to an apron works erratically.

* Recent Airports list cleared after restarting app.

* Opening more than one airport causes slow performance.

Looking forward to the final release!
 
* It seems that FSXPlanner is changing the runway and pattern altitudes to huge numbers after clicking on a runway, causing compile errors or, if the number was accepted by the compiler, mountains on runways.

I noticed this. It may be fixed, we only checked briefly. If you still notice it in R23, please let me know.

* Using the zoom tool with an object selected also not only zooms, but also moves the object to wherever the zoom tool was clicked.

This is not a bug. It's supposed to be that way. So that the airport zooms in on where you click.

* Deleting an apron vertex deletes the entire associated apron.

I'll have to check this.

* Adding vertices to an apron works erratically.

You need to be very specific in where you click. It's best to be zoomed in and then click right on the line. Clicking off by a little bit can make FSX Planner think you no longer want to have that apron selected, and then the adding doesn't work.

* Recent Airports list cleared after restarting app.

Some people have reported this. It doesn't happen for me though, which makes it very difficult to resolve. It may be something to do with read/write permissions to certain directories though.

* Opening more than one airport causes slow performance.

That is to be expected as the more airports you have open the more cpu and memory resources are required.

-Russell
 
Thanks for the quick reply. Any chance there will be some shortcut keys put in?

There are some, like the delete key for deleting objects, and the ctrl-(letter) key for menu commands.

Are there specific shortcut keys you had in mind?

-Russell
 
R23 Open Airport BGL Problems

Russell,

When I open a BGL the Taxiway Path Data seems to be missing the "Number" field. It should match the runway and does not seem to be true in a couple of airports that I tried.
 
Russell,

When I open a BGL the Taxiway Path Data seems to be missing the "Number" field. It should match the runway and does not seem to be true in a couple of airports that I tried.

Just looked at this, and it is actually a bug in how the runway number is displayed in the properties display. It is decompiled from the bgl correctly, but if it is a single digit number, such as 8, then the properties window is looking for 08, which it doesn't find and therefore displays nothing.

I have fixed this and the next release will contain the fix.


This only affects the taxiway path if you click on it, and results in setting the runway number to nothing. This is only for runway taxiways. For now the fix is to make sure you specify the runway number on the properties display if you click on a runway taxiway for runways that are numbered 1 through 9.

-Russell
 
* Deleting an apron vertex deletes the entire associated apron.

How are you attempting to delete the apron vertex? Do you control click on the vertex while using the apron editing tool, or are you doing something else?

-Russell
 
Back
Top