Yes sure, I have to confess I didn't study the manual thoroughly enough. "Real men don't read manuals"
-
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.
FS2004 Array Elevation wrong?
- Thread starter hgschnell
- Start date
Please try Development Release 4.4.2.4.
I'm thinking of doing away with the automatic selection of m. for ICAO approaches and ft. for the rest. But, that will be in a future release (if I do it at all i.e., if there's not too much work/risk of destabilization involved).
I'm thinking of doing away with the automatic selection of m. for ICAO approaches and ft. for the rest. But, that will be in a future release (if I do it at all i.e., if there's not too much work/risk of destabilization involved).
Thanks for the info. Glad you could find it.
By the way the automatic checking for new versions doesn't work for me (I have checked both general and development releases).
If I try it by "Help etc." I get the old window again:
So I go to www.stuff4fs ... and get it.
By the way the automatic checking for new versions doesn't work for me (I have checked both general and development releases).
If I try it by "Help etc." I get the old window again:
So I go to www.stuff4fs ... and get it.
The important things work fine.
The automatic update works 1 step further:
But this is no problem for me.
The changing of meter and feet is a little confusing. AFLT4 changed it because of the project, but the my 502 ft in the "Edit approach lihts" window were changed to about 1600 ...
Isn't it easier with 2 fields in the window (ft and M) which are connected. So we could fill one ore the other and the other is computed automaticly?
Anyway, thanks a lot Don!
The automatic update works 1 step further:
But this is no problem for me.
The changing of meter and feet is a little confusing. AFLT4 changed it because of the project, but the my 502 ft in the "Edit approach lihts" window were changed to about 1600 ...
Isn't it easier with 2 fields in the window (ft and M) which are connected. So we could fill one ore the other and the other is computed automaticly?
Anyway, thanks a lot Don!
This is a different issue. Are you sure you weren't having internet connection problems?
This was likely due to the one-time required change highlighted in the announcement for the general release - complicated by the problem you discovered. From here on, you get to pick whatever units you want and AFLT will not force you to use the other.
very sure