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

Can't create new airport

T

tman

Messages
11
When ever I put in all of the info for the new airport this comes up(see attached) here also is the log in the same zip.
 

Attachments

KDAY already exists in FSX Cox-Dayton Intl. You should not try to create a new airport using an existing airport code. Load it as a stock airport and work from there if you want to modify it.

Having said that ADE should not crash so that is a bug we need to fix
 
Like previously stated by both Meshman and Jon, DO NOT make a new airport if the same airport exist in the FSX database.

This becomes a duplication (of the default KDAY without blocking code) based on the ICAO header compiled and all duplicate XML (start locations) airport data. That in turn will cause FSX to crash to your desktop when you enter certain sectors within the 108 NM visual radius of the airport.
 
I have modified the New Airport Code to stop this happening in future versions
 
Thanks. I do also have a suggestion. The background images are hard to get in the right spot because you have to resize them. It would be very helpful to be able to put a "pin" on a point in the image and have that point stay where it is when you resize. For me I use apd's so I have to line up the lat long lines. If you are not sure what in the world I am talking about, you can see the same thing on airport facilitator X
 
tman said:
Thanks. I do also have a suggestion. The background images are hard to get in the right spot because you have to resize them. It would be very helpful to be able to put a "pin" on a point in the image and have that point stay where it is when you resize. For me I use apd's so I have to line up the lat long lines. If you are not sure what in the world I am talking about, you can see the same thing on airport facilitator X
Click to expand...

No I'm not sure what you are referring to. There are two ways to add a background image - one is to size it against a known element such as the main runway and the second is to set the top left and bottom right lat/lon values. Or are you referring to another method?
 
We cannot pin the background image to the ADE grid as long as you are in resize mode. Once you have the background imaged sized and positioned correctly then you can pin it to the Grid which we call 'Lock'.
 
You guys aren't picturing the right thing. Download airport facilitator X and read about their background image placement and try it to see what it does.
 
It might be best if you take some pictures of what you are refering to when saying a background image. You can then post your pictures here in the forum with an explaination.
 
Unfortunatly, pictures would not be a very good medium of explanation. The best way would be to just try it out yourself with the directions on AFX.
 
tman

If AFX thought that pinning down a corner of the background image or pinning the runway end then using a mouse stretch technique was the best way to scale the precision then why would they also say

Note that for best precision, you find out the corner coordinates of the image and enter them in the properties dialog box, instead of moving it with the mouse.
Click to expand...

ADE is not about shortcuts that does not give a precision placement of the background image. We feel the best approach is give the User the best possible way to do something the first time and not the other way around that says if this does not work then do this.

We take all suggestions seriously but in the end it is a team effort that decides if the suggestion enhances the ability to design a airport or is it just a piece of code that does something and if that does not work then here is a Note to do something else.

Your suggestion as been noted and may very well be tested but we do not believe in taking one step forward just to lose 2 steps backwards when trying to place a background image precisely.
 
I understand what is being suggested by tman :)
 
If you find me some good resources where the corner coordinates are marked and precise, let me know. The only reason I am suggesting this is for things like airport diagrams where you only have lat long intersections and there is no way to determine the corner coordinates.
 
tman said:
If you find me some good resources where the corner coordinates are marked and precise, let me know.
Click to expand...

I suggest GoogleEarth--it quite accurate--and you can set its lat/long display out to at least 8 or 9 decimal places. It is simplicity itself to obtain a screenshot with exact lat/long coordinates for use in ADE in this manner.

If anyone tells you that GoogleEarth is not accurate, they are in most instances incorrect. I have correlated actual positions in GE with GPS *and* USGS topo data, and GoogleEarth is usually accurate to a few meters most of the time. Granted there are locations with inaccuracies, but they are relatively few.

This level of accuracy in GoogleEarth generally far exceeds what shipped with the default MSFS database, so in my opinion is quite sufficient for our needs as designers.

This is much better than going off airport charts and then stretching the image with the mouse.
 
You must log in or register to reply here.
Back
Top