Trouble with Approach Mode and Loc Arming in MSFS 2024
-
Yes. I have the 1.1 version of the Starship.
-
No GNS. I have that set to not be there too.
-
Here's an example. Appr mode armed, ILS is tuned and in VOR mode for nav. Course is correct. Only GS arming and not LOC. The GS indictor works, but it does not capture GS. Stays in VS or ALT mode.
-
That screen shot is actually showing another issue I see intermittently. From that PPOS point on the map, I did a Direct To MUDRE, it made it my active WP and NAV worked, but it drew a line back to the airport instead of MUDRE for some reason.
-
Another note, I just tried it in MSFS2020 and got the same result. I'm starting to feel like I'm missing a step?
-
I figured it out, APPR does not arm LOC when in VOR nav mode, the NAV button does. So if you're lining up a ILS approach you have to hit both NAV to arm LOC and APPR to arm the GS.
-
I have observed the same. With MSFS2024 and v1.1, if I select HDG to direct the plane to the LOC and hit APPR both HDG and APPR will be slected at once and on the PFD HDG and GS is shown instead of LOC and GS. I think with the previous version of the plane you could not even select APPR if HDG was already slected. For me what works really well is to set FMS as primary nav source and VOR as secondary nav source. Then let the autopilot in NAV mode fly the plane using FMS to the localizer axis and then use the transfer button to swap FMS to VOR. After that hitting the APPR works well. Also, in this case the plane will be on the center of the localizer and not at a shallow angle to it.
-
No, that's not correct and not how it should work. I haven't needed to do that since updating to version 1.1.
You're sure you have the latest version? I've shot a half dozen ILS approaches since 1.1 and not had to do anything but box APPR.
@jmarkows I am definitely running 1.1. It's interesting that some of us are seeing this behavior and others are not. And I'm seeing it in both 2024 and 2020. At least I have a workaround for now until this is looked into more.
Here's my manifest.json with the package version showing 1.1:
{
"dependencies": [],
"content_type": "AIRCRAFT",
"title": "Starship",
"manufacturer": "Black Square",
"creator": "Black Square",
"package_version": "0.1.1",
"minimum_game_version": "1.3.23",
"minimum_compatibility_version": "3.19.0.47",
"builder": "Microsoft Flight Simulator 2024",
"package_order_hint": "CUSTOM_SIMOBJECTS",
"release_notes": {
"neutral": {
"LastUpdate": "",
"OlderHistory": ""
}
}
} -
I have figured out how to reproduce this. According to the underlying variables, this appears to be MSFS's misguided sense of approach arming. I'm surprised this hasn't turned up in my other aircraft, so there might be something in the configuration files that I'm missing. For now, I have implemented a workaround that should produce the expected behavior, even if I can't figure out what's happening under the hood just yet. Thanks for pointing it out.
-
I have figured out how to reproduce this. According to the underlying variables, this appears to be MSFS's misguided sense of approach arming. I'm surprised this hasn't turned up in my other aircraft, so there might be something in the configuration files that I'm missing. For now, I have implemented a workaround that should produce the expected behavior, even if I can't figure out what's happening under the hood just yet. Thanks for pointing it out.
@Black-Square As I was experiencing this, I was having a flashback of it happening while flying Carenado C337 in the past on MSFS2020 and not finding any solution at all online.
-
Interesting thread, I've had the same thing when using heading mode, I can see the GS and LOC on my display but APP didn't trigger so ignored the FD and flew down using the LOC and GS indicators.
This happened after Vectors to ILS from Beyond ATC, when flying in a STAR and using Nav then wasn't an issue, APP worked as expected. Glad to see the issue wasn't between the keyboard and chair
