• 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 When moving airport altitude is set to ZERO

FlyingAxx

FlyingAxx

Messages
611
Country
germany
After extending to the PRO version of ADE I'm tumbling over something I did not find fitting answer here in the forum (likely my fault). When moving an airport in both, the current release version and as well in the Beta one, the altitude of an airport is set to "0" (Zero) when just moving it (as far as I can recall there is no problem when changing the angle).

However, it's troublesome as it requires for each and every polygon (even after saving and re-opening the file) again the input of the correct altitude and usually it requires as well to check all altitudes of all other elements (starting points, runways). :banghead:

Is there any way to prevent this behaviour (or a reason to explain the way it is realised)?
 
I am not aware that it is doing this. Are you saying that it is setting everything to an altitude of zero?
 
Hmm, that doesn't happen here. All terrain polygons retain their elevation.
 
What version of ADE are you using?
 
It happens in both, 1.55.4860 and Beta 1.60.4932. :confused:

If you want I can try to catch it in screenshots.
 
Last edited:
Here is an example (just any airport - I did not really work on it).
I opened the default PAAK in ADE (release), saved it (file PAAK_ADEX_AB.ad3 and moved it by 100ft in 90° direction. The resulting re-loaded file is now named moveFile.ad3. FaultFinder finds wrong Altitudes and in Airport Properties the Altitude is set to .000.
 

Attachments

Well I'm damned :banghead:

It retains the terrain polygon elevations but it changes the airport elevation :eek:
 
It remains just one other pic....:D

2013-10-02_16h5502_FaultFinder_AB.jpg
 
OK - I will look at it but if you move an airport then you most likely need to reset the altitude anyway - it is a long time since I wrote this code and I do not recall if the reset is deliberate or accidental :o
 
I had to move two airports. ENBM, moved 600 meters. ENDI, moved 100 meters. The MS default placement was totally out of whack, now both airports are nailed with threshold coordinates from official charts. But I never saw this zero altitude problem...

Cheers,
:stirthepo
 
Andrew said:
I had to move two airports. ENBM, moved 600 meters. ENDI, moved 100 meters. The MS default placement was totally out of whack, now both airports are nailed with threshold coordinates from official charts. But I never saw this zero altitude problem...

Cheers,
:stirthepo
Click to expand...
Hmm, I just tried it with ENBM and got as a result a beautiful valley (proving that the military always chooses the nicest places) but the result was clear:
  • nothing to sea at the surface
  • altitude in airport properties: .000
  • altitude of runway 300ft
  • altitude of starting points: 300ft

In fact the landscape would ask for an airport altitude of about 442ft when I shift it by using Google Maps as reference. and consequently it sits for me in a hole at the old location.

Probably we should try finding out the difference in our installations. :confused:
 
Last edited:
scruffyduck said:
OK - I will look at it but if you move an airport then you most likely need to reset the altitude anyway - it is a long time since I wrote this code and I do not recall if the reset is deliberate or accidental :o
Click to expand...

Jon, ACES sometimes managed it to misplace an airport but using at least the other airport data more or less correctly. As I adapted about 150 airports meanwhile (mostly remote places with just a few available data) I feel that this function is quite useful.
 
The altitude set to zero on move bug should now be fixed.
 
You must log in or register to reply here.
Back
Top