• 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 ILS and displaced thresold

Frédéric Revol

Frédéric Revol

Messages
72
Country
qatar
Hi,

I added an ILS to an existing runway (Doha/OTBD runway 16) which was added in Feb08 in real life. However, it seems the glideslope is guiding my aircraft to the runway end instead of the displaced thresold.

Have I missed something ? Thanks,

Fred
 
You need to move the small green arrow (not the big one) to the displaced threshold. That determines where you will touch down.

Hope this helps,
 
Frédéric Revol said:
Hi,

I added an ILS to an existing runway (Doha/OTBD runway 16) which was added in Feb08 in real life. However, it seems the glideslope is guiding my aircraft to the runway end instead of the displaced thresold.

Have I missed something ? Thanks,

Fred
Click to expand...

When you add a ILS (Localizer and GS) ADE places the small green triangle (GS) about 1000 ft. in from the end of the runway. If you lengthen the runway using a displaced threshold grab the small GS symbol and move it back. Align the GS to the side of the runway where you want the glideslope to intersect the threshold.

EDIT ***********

Tom

I cross posted
 
I like the fact that the 1000 feet ILS runway touchdown was added in 1.40, but perhaps it should offer some customization in the options menu, so that we could edit the default ILS touchdown to perhaps 500 ft or whatever to leave some room for flare?

I would be very happy however, if I could just punch in a touchdown number, because freehand drag is time consuming, and not very precise.

It would also be great if the 1000 feet took into consideration the actual offset threshold of the runway, because every runway is different. Better yet, if the default touchdown point could just be equal to any existing PAPI, it would save a lot of time.
 
Hi,

Here's a trick to make freehand dragging much easier.

1. Hold the mouse over the end of the runway and press the B key to place the "bookmark".
2. Now at the far right of the status bar (bottom) you will see the distance of your mouse from the end of the runway.
3. Drag the little green arrow until it is the desired distance from the end of the runway.

To move the "distance marker" just move the mouse to a new position and press the B key again.

BTW, Shift-B centers the screen on the bookmark, and Ctrl-B removes it.

Hope this helps,
 
I am aware of how to freehand. My suggestion is not designed to improve freehand technique, but rather, to eliminate freehand with ILS additions or adjustments entirely.

It would simply be more efficient if the default ILS feather touchdown point would just be tied to the existing runway VASI, PAPI or whatever, if available.

And if there wasn't a VASI, 1000 feet from the offset threshold is where the actual touchdown marker is, not 1000 feet from the beginning of the runway pavement.
 
It would simply be more efficient if the default ILS feather touchdown point would just be tied to the existing runway VASI, PAPI or whatever, if available.
Click to expand...

tlv

Do you look at approach charts? Many ILS approach charts say

VGSI and ILS Glide-path are not coincident.

ADE sets the Glide Slope which is a transmitter location. When a plane is slotted correctly for a ILS Glide Slope the plane fly's its atitude glide-path. A Cessna 172 vs a Boeing 747 have two different Glide-paths when slotted correctly on the same ILS approach. If you want the VGSI and the ILS GS to be the same then only one size plane can use both at the same time based on their Glide-path (high or low atitude).

FS sets the stock GS at the published Lat/Lon reported by the airport. ADE can not guess what that exact Lat/Lon is when adding the GS transmitter. You must change the 'Set by Drag GS window property box to 'Set Manual' when you are placing the correct GS location. This allows you to insert the exact GS location as reported by the airport that commissioned the ILS runway.
 
Of course, you can press B at the offset threshold and it will give you the distance from there to your mouse. Quick and easy, and each one can be customized for the type of aircraft, etc.

But your point is also valid - it would be nice if there was a default setting for things you add later, including GS and VASI.

Hope this helps,
 
You must log in or register to reply here.
Back
Top