Do you have any add-ons in your Community folder? If yes, please remove and retest before posting.
NO Are you using Developer Mode or made changes in it?
NO Brief description of the issue:
Trying various airports, runways, and frequencies. I have both loaded a flight plan from simbrief (along with proper w/b) and manually entered flight plan. I can successfully capture the LOC and the GS. However, I am not able to engage both autopilots.- thus I only have a single channel app. Sometimes the LOC and G/S become âLANDâ and I assume this means autoland will be successful. Everytime, at around 50ft agl (before the âretardâ call) the airplane dives down into the runway. Perhaps also worth note, at around 500 ft AGL I notice a message on one of the displays that says âlanding inhibitâ in purple lettersâŠanyone with any advice or recommendations?! I would even be open to a cockpit share (though I have never tried)
Umm, are you landing on a CAT III runway? Autoland is only applicable to CAT III runways. I have successfully used autoland on at least 3 runways so far.
ILS category has not much to do with autoland.
If e.g. the surface is flat far enough ahead of the runway, the AP has no problem to perform an autoland even on a CAT I runway.
Default Asobo A320 doesnât have Autoland, so this bug and Issue doesnât apply to that.
The FBW A32NX Stable version 0.6.1 that you installed into the community folder or from the Marketplace also doesnât have Autoland feature, so this bug and issue also doesnât apply to that since itâs both not implemented and the bugs and issue reporting is not for third-party aircraft.
Only the FBW A32NX Development version that you install using the FBW installer has the Autoland function. So you need to install that version.
As PZL104 said, the ILS Category has nothing to do with the Autoland, itâs just a regolatory purposes that Pilots should only use Autoland on CAT III certified runways because it has enough system redundancy to ensure a safe landing in CAT III conditions.
Autopilot system wise, as long as thereâs ILS, no matter whichever category itâs certified, at any runway at any airport that has ILS, Autoland will work. Been doing it for a number of times myself in many ILS runways regardless of the category. I still put the Radio minimums according to the charts. And the Autoland still works regardless.
THANK YOU! I did download the FBW version from the marketplace so from your response, regardless of whether the runway is CAT111 cert, the bug will not execute the autoland. Any tips on what to do with the marketplace version getting it to flare? it looks like after it dives, the flare mode pops up on one of the displays⊠I have tried both selected speed (speed taken from mcdu) and managed speeds. and have tried with thrust lever at CLB detent as well as hovered slightly above idle to close when retardingâŠ
Even the default A320 displays e.g. FLARE, but these are only a fake messages.
As @Neo4316 pointed out, you need the development version, not the one from the marketplace.
But the A320 is really easy to land manually.
Disengage the AP at 100ft.
At the 30ft callout pull the thrust levers to idle, slowly pull the nose up ~2deg and wait.
appreciate the info! Landing the a320 is pretty easy, the FBW moreso than the asobo version. Patiently waiting for the update when the version I have can do the full autoland.
In the takeoff and landing phase, items which donât require immediate action and which are not important during this very short flight phase, are inhibited.
e.g. anti-ice related messages like ENG 1 VALVE OPEN.
Make sure you enter ânoâ at radio line on the approach page in the perf menu:
Press perf button on mcdu
go to approach page
enter al missing data and enter ânoâ on the right side next to radio
-make sure appoach phase is activated before caturing loc and gs
Otherwise no cat 3 autoland where you can turn both autopilot on
It probably wonât come anytime soon. I had a look at the version 0.7.0 changelong, and it doesnât look like the custom fly-by-wire system and the custom autopilot with the autoland feature would be included there in the next release. (It might change though, so I dunno) So you might need to wait a bit longer if you want to wait for the marketplace version to be updated with it.
I believe you have to be in approach mode (activated on the FCU) before you can activate both autopilots. But it should work with only one autopilot, which is not how it works in the real world.
Use the developer version available on the installer from https://flybywiresim.com/
Make sure to remove any other versions from Marketplace before doing so
As suggested I was happy with the developer version till the latest update on msfs. I reinstalled the developer version and now Iâve lost the cockpit view⊠and the sim crashes the moment I load the flight plan from SimBrief. Restart is with Safe mode or Normal mode option.
Appreciate any help.
