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

Unit of Measurement Changes

John Hubbard

John Hubbard

Messages
287
Country
ireland
I am trying to put a beacon on top of a mast on a hill near the airport (PAMH).
Feet keep defaulting to metres.

When I open the program (4.4.3.9) I choose Feet. When I place the object and enter the height I enter 50 Feet ASL.
After compiling I am asked if I want to change the units. I do not know what to do. So, the first time I said yes.

When I ran the program again and checked Options/units, it had changed back to metres. Next time, I said no when asked about changing units.
The same thing happened anyway! Units had gone back to metres.

Maybe I missed something obvious?

I'd be grateful for advice.
 
It's not clear why AFLT keeps asking you if you want top change units. In order to determine what is going on, I need your Projects folder and the .bgl for the reference airport. I suspect, however, It's got something to do with your choice of units under Options/Display Format/Units.
 
Thanks. The airport as such was modified with ADE. I've not used AFLT before (W7). Trying to put a beacon light on a mast on a hill nearby.
The mast is fine, but the light is some way distant although the coords are identical.

The files you asked for re. units can be downloaded here.

Files shared via Tresorit

Tresorit uses end-to-end encryption to keep file exchange secure and private. Access the received content via this link.
web.tresorit.com web.tresorit.com
 
John, I've run your files and I don't see anything fundamentally wrong. But:
  • your default distance and elevation units are meters. If you want to work in Ft. I suggest you open AFLT, using Options/Units, change to feet and close AFLT. Then re-open. Your default units should be Ft. and you shouldn't get any further messages about changing units.
  • you have placed an obstruction light (which is intended for building tops, etc.) I suspect you want an AeroNav beacon.
Give these a try and you should get the expected results.
 
Thanks. I changed the units to feet and closed the program. When I re-started the program had defaulted to metres.

The same thing exactly happens in Windows 10. No matter what I do, when the program re-opens it defaults to metres.

AeroNav_PAMH.jpg
 
Last edited:
AFLT "remembers" the unit in effect when you specified the element and reverts to those units automatically.
 
Something about your report above prompted me to take another look at the issue. It turns out when AFLT asks you if you want to save the new units, it ignores your answer. So, I will fix this in the next release which should be along in the next day or so.
 
Don,

Just as a follow up, in Appendix "A" you refer to a Beacon tower as 50m high. I wonder if you meant 50ft?
 
Don't know to what reference you are referring, John. But, it doesn't matter. It's your tower. Make it as high (or low) as you want.

Don
 
gadgets said:
Don't know to what reference you are referring, John. But, it doesn't matter. It's your tower. Make it as high (or low) as you want.

Don
Click to expand...
The key word here is Supplied. So, is a 'base model' supplied or not? If it is supplied, may I ask what form it takes exactly?

Appendix "A" - Base Models Supplied
Base models for all but surface mount applicatoions must fall into one of the following
categories:
 Approach - uni-directional light intended as a threshold light in approach lighting
configurations either as a threshold light or mounted on a tower.
 Approach_T – a simple horizontal mounting bar 1m. long, which will be adjusted onthe-fly as needed and to which will be attached one or more posts and one or more
light heads. Two associated base models are required:
o Approach_Post – post to be attached to Approach_T
o Approach_Head –uni-directional light to be attached to Approach_T
Beacon - a 50 m. high tower. You may choose to have a blinking light atop it or a
blinking light at night and a strobe during the day
 
You must log in or register to reply here.
Back
Top