richboy2307

Hi @JoeDel To intercept an ILS, you need to: Fly on an intercept heading/course towards the LOC, and Capture and establish on the LOC before you can capture the GS Capture the GS at an altitude below the GS If you are already above the GS, the AP may still capture the LOC, but will not initiate a descent to capture the GS. The airplane will also not follow the GS until you are established on the LOC first. From your screenshot, I can see LAND is selected on the FCU, and G/S & LOC are properly armed (in blue) as the next modes for the autopilot to capture. However, from the ILS raw data, I can see that the LOC is to your right, and the GS is already below you. From the current position, you'd need to fly further to the right to intercept the LOC, and initiate a descent to a lower altitude (e.g. 1500ft) using VS mode (at -1000 fpm or as necessary) to get below the GS to intercept it. There are plenty of video tutorials available on youtube regarding this, but here is a Computer Based Training (CBT) for a standard ILS approach: https://youtu.be/bS_tLfKDak4?t=587 Hope it helps, thanks!

Hi @samj Other than conflicting/noisy control inputs, other things that can upset the autopilot include excessive turbulence or abrupt wind/weather changes (e.g. when the sim does a weather update). One way to ensure that this isn't what is happening here is to try a flight with the 'Clear Weather' preset, and see if you still notice the issue. The other thing is to also check that AI Assists (e.g. Auto Yoke and Auto Trim) are disabled. Those can also cause issues with the Autopilot. Thanks!

Seen your report on discord and noted, thanks!

Can y'all confirm you've enabled the correct radios from the ACP? See:

Hi @Nighthwk Thanks this is known and will be sorted in next update.

Hi @Airbuskid87 As reported by @DanDan87 on discord, this issue appears to be related to anti-aliasing settings. Perhaps try to change your settings and see if the issue is resolved. Thanks!

Hi @KirkJohn The ND does not display the top of descent arrow when HDG (or TRACK) mode is engaged. So you have to be in Managed (NAV) mode following your flight plan. There could also be additional reasons such as not having reached your CRZ alt, as well as having already passed it. Could you please share the route you were flying (e.g. EGGW/25 N0371F180 OLNE2B OLNEY T420 TNT N57 DENBY DCT LBA DCT EGNM/32) as seen on simbrief in the 'Route' section of the dispatch? Thanks!

Hi @geckuz Thanks for your post. Unfortunately this is not correct, and a misconception derived from an old version of FCOM. Such a limitation was only applicable to very early variants of the A320ceo. The A320neo meanwhile is a different beast altogether when it comes to Flexible Thrust takeoffs when compared to any variant of the A320ceo. The A320neo engines generally have more FLEX by comparison. Here is a real world example of an A320neo where the FLEX N1% target (~79%) is lower than the CLB one (~83%). https://youtu.be/cv41hm4JEB8?t=157 And also for A321ceo where the FLEX N1% target (~85%) is lower than the CLB one (~87%). https://youtu.be/LGeegwNsKwU?si=Iir3j35AKEqxTQxt&t=1120 We are looking into improvements for calculations at high altitudes in a future update, but generally, performance calculations are a complex subject with a lot of variables at play. The takeoff speeds are optimised for maximum flex for the given restriction, meaning on a dry runway 50ft elevation at the end of it, and 35ft for a wet one. The EFB's computed performance is aiming to FLEX as much as possible while giving as much climb gradient for the 2nd segment which is often why you see 2nd segment limited message, and it will try to use up as much runway as it can if it means it can flex the engines more. Thanks!

Hi @albertom We'll take a look at this. Can I also confirm are you using Navigraph or default navdata? Thanks!

Hi @DaveEastwood All the files can be found in the ``microsoft-aircraft-a320neo`` folder that is in your 'Packages/Official' folder. However do note the 'Aircraft.cfg' file is unfortunately encrypted by Microsoft and may not be user accessible. We cannot share/provide this file as it is a Microsoft product, for further enquiries you can contact them directly via ZenDesk. Thanks!

Hi @Saitek15 You can find the A320neo, and all other Microsoft aircraft manuals here: https://www.flightsimulator.com/aircraft-manuals/ As for the videos, we do not have any detailed instructional series planned as there are plenty already covering the A320 and its variants. However you can refer to our introductory video below for the more pertinent info, specifically detailing the differences between the 320Neo vs 320Ceo:

Hi @a321xlr The animation is quite slow and can take upwards of 60 seconds in some cases before the baggage truck moves away. See video example: 2024-06-04 18-33-43(1).mp4

As mentioned on our discord, its under consideration. Additionally, to manage expectations, it isn't a minor fix that can be delivered in the short-term. We understand why people request it, and the importance of such features would only grow with products like the A350 and A380, so we would like to incorporate such features on it and possibly roll them back into previous products eventually. We appreciate your understanding. Thanks!

Hi @Josh1999 Thanks we're looking into it. Are you on PC or Xbox? In the meanwhile, users have reported that by selecting DIR TO to the next waypoint allows you to resume managed (NAV) mode flying in case you face this issue again. Also may I ask how did you engage HDG mode? Did you: Pull the knob first, then rotate the knob to select a heading? OR Rotate the knob to select a heading first, then pull the knob? Just trying to see how to reproduce the issue. Thanks!

Roger, we'll take a look. But is the issue that you cannot swap frequencies? On A300, the fix was allowing radio swapping via `COM1_RADIO_SWAP' and 'COM2_RADIO_SWAP' simconnect events. Both of these already work on the A320neo currently. Thanks!

Thanks for confirming. I've passed on your suggestion to the team, we'll take a look if it can be incorporated in a future iteration of the plane. Thanks!

You can download liveries from the iniManager. It will automatically install them into your community folder. For other liveries downloaded from third-party sites, please follow the instructions as included with those. Normally, same as any plane, all compatible liveries should work by drag-and-drop in your community folder. Thanks!

Are you using any pedals or axis for Left Brake/Right Brake? The Autobrakes disconnect when they detect any input on the brake axis (left or right), and judging by the fact you drift to the left, it leads me to believe that Left Brake axis is getting erroneous input. So please cross check your bindings, and deadzones of those axis. Thanks!

What was the PBD in which you noticed the issue? Also are you able to reproduce this problem successfully? Yes this is an acknowledged shortcoming of the currently implemented LNAV logic, and we're working to improve this on a future version. For now it is recommended to fly DME ARC segments manually where necessary. Thanks, will investigate. Can you verify you are using the same units (Metric/KG vs Imperial/LBS) on both the EFB settings and Simbrief Dispatch? Just a reminder to avoid posting the same comment in multiple places I've answered this on your dedicated post: Thanks!

Hi @echopapa Had you dispatched an A320neo flight before this? Coz it seems it was still trying to pull an old/previous OFP you may have dispatched for the A20N. This may be due to server issues. Alternatively, you should also verify the type in your dispatched OFP in the 'ATC Flight Plan' section. If that is showing as A306, then I recommend you erase your Simbrief ID on the EFB, then re-enter to try again. Thanks!

Hi @may433 All Microsoft product manuals can be found here: https://www.flightsimulator.com/aircraft-manuals/ Thanks!

Currently, it should update every time you select a procedure in the MCDU. The choice is further dependent on your current 'Phase of Flight', such that in and before CLB phase, it will prioritize tuning the departure runways ILS for SRS/RWY. It will not auto-tune to the arrival runway's ILS until you select an approach procedure, and you are in CRZ (or beyond) phases of flight. Hence it is recommended to re-program the approach in your MCDU once airborne and enroute. If you only set it during pre-flight, then it would have tuned the departure runway's ILS and will remain so. In general, you should cross-check the frequency set as part of your descent planning anyways. But as mentioned above, the frequency itself auto-filled is a function of the scenery and the navdata that comes coded in it, as opposed to anything we are doing in the aircraft. This limitation holds true for any aircraft that is not using its own custom-made navdatabase. With regards to the auto-tuning logic for NAV1/2, it is programmed to pick, from a filtered list of VORDME/VOR/DME, one station that is closest to your PPOS (or closest to your next waypoint, whichever would be more precise) at the time it is making a selection. The filtered list of VORDME/VOR/DME that it picks from however, is something the sim itself generates. This again falls back on using the default navdatabase as opposed to a custom one. So if for whatever reason the sim has included SOY (LOCDME) in that list (be it on default or Navigraph-supplemented navdata), then the plane is going to consider it a valid option, and tune into it, as at the time it was probably closer to you than STN. Thanks!

Reported, thanks!

Thanks, yes team is aware and its on the list of things to do for the A310.

Hi, thanks the team is aware of this and investigating. Appears to be random, as it will work some flights and not on others.