Let’s see, I’m the one who developed the autopilot, and Dean may have been confused when writing the manual. We all make mistakes and for that we should not blame him.
That said, the event is LOC. And you will never capture the GS with it, only the localizer.
Not neccesary, if you look the second video i uploaded the other days i used only NAV 1 freq.
If you have ILS freq on NAV2 but not NAV1, the GS should use NAV2, otherwise NAV1.
@DEAN01973
According to the documentation provided by @GreyStone93 above, this confirms what you say about GLIDE alone being used for ILS approaches. However the last paragraph states that VOR LOC should activate automatically when it detects an ILS signal. With the triangle marking which your model doesn’t have yet.
OK well that makes things more confusing then. Because I’ve been using LOC as you describe for capturing a Localizer and it does not work.
This is what I mentioned above in my big post. I’m not saying it’s a ghost, but there is something going on with the coding where the code is not being activated the way I am pushing the buttons.
I’ll try to show everything in the video later today
What do we mean by capturing a localizer? Because the LOC event, or VOR LOC in this case, what it does is guide you to the localizer without capturing the GS.
The difference with GLIDE is that it captures the localizer and also captures the GS. You can omit the use of VORLOC if capture GS that is your direct intention.
Hey @CodenameJack447 - one thing I’ve noticed with 1.0.2 is the auto-throttles seem to be ON even when the piano keys are not armed – is this normal (when using Auto-throttle)? My understanding was we only want to use auto-throttle for a few minutes (otherwise we burn fuel way too fast).
You can see below I do not have the afterburner piano keys engaged, yet afterburners are indeed on.
Thats exactly what I mean. Capturing a Localizer several miles out before capturing the glideslope.
And what you’re trying to tell me is that it doesn’t? Because it does it, if you’re in RAD mode. At least on my end.
Moxie, it is impossible that with the piano keys down, the autotrottle is working for you. Try moving the throttle levers.
And in your screenshot i’m seeing AT1 Up, so your are in AT on
Yes, that’s what I’m telling you. It doesn’t on my end. That’s the bug we’re trying to resolve.
I’m going to investigate it myself, but I assure you that you don’t have to do tricks for it. If the aircraft is within range of the localizer and the RAD INS is in RAD mode (whose event is GPS DRIVES NAV off), you should be able to capture it.
The only explanation I can think of is that you are far from the localizer or that you are still in GPS mode, but then RAD INS switch would be in INS mode
Cool. I’ll make a more comprehensive video for you later
Sorry maybe I am misunderstanding.
I have Auto-Throttles engaged/ON (as you said). But I thought the afterburners would only engage if you have these keys turned upwards? Which I do not in this photo:
In regards to capturing ILS, maybe you’re not talking about this way, but I keep everything on INS, then make sure I have the correct ILS entered in FMC and as soon as I am near establishing on the ILS, I click Land and Glide and it captures it flawlessly.
No, you see, the AI that handles the autothrottle bypasses those switches. or even the event that you have mapped on your keyboard or your device. Those switches work if you interact with them directly, but with AT off.
ahhh got it. OK, thanks CodenameJack!!
minor cosmatic glitch, I think the baggage ramp is way lower than it should be in the animation?
and just wondering… during icing condition, which switches should I engage in order to de-ice? I think there are 4 engine de ice switch which I usually turn on, and then is the fuel heating needed to de-ice the wings and kept if from stalling?
No, INS or HDG mode is irrelevant. Localizer should capture correct regardless just like other aircraft
Hi I have seen the light marked by the blue arrow on and turned all the switches you have marked to on and it just keeps there and won’t vanish, is that normal? and that the blue circled switches, I think in 1.0.2 it’s now in the “On” position which is the opposite to the original release?
question on the fuel panel:
is the fuel heating actually doing anything? just wonders should I worry about that in flight.
and I saw the engine state switch labelled “Lo, Auto and Hi”, which when playing around if I kept in auto, it just stays in the “Med” lights in the indicator, was that supposed to be manually switch to “lo” during taxi and “hi” once using the afterburner? or staying in auto is ok
The switches you’ve circled in blue were reversed in the update to match the actual concorde. I have to retouch the warning that you mention, for the time being pay attention to the one I marked before.
At the moment they do nothing, due to Asobo limitations: it is possible to measure the fuel temperature in a piston or turboprop engine, but not in a turbine engine (we can measure the temperature of the oil for example). They are there as a cosmetic level waiting for us to use them in the future.
the same goes for Lo, Auto and Hi,
The idea is to be able to change between ECUs, or what is the same, to vary the FADEC of the engine. At the moment in MSFS we cannot do it. But it is set to be used in the future if Asobo implements it.
