richboy2307

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.

Thanks for your report, shared with the team for further investigation.

Thanks, reported to the team and we're looking into it.

HI @skydiver6547 I have my throttles mapped to bravo throttle quadrant. I set the throttle axis to IDLE, used F2 to engage reversers, then move the throttle axis levers forward and am able to go into FWD thrust immediately. Please try to reset your calibration. If that doesn't work, check your Throttledata.ini file from the locations below. Ensure that the "reverse_on_axis = false" is seen. Steam: %APPDATA%\Microsoft Flight Simulator\Packages\microsoft-aircraft-a310-300\work MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\microsoft-aircraft-a310-300\work Thanks!

As answered via discord post, "Its an issue of lack of reconciliation between CFD Flight Model and the sim's event logger (likely designed for the older flight models). In any case, its for MS/Asobo to address. It is not up to us to be fixed and should be reported to ZenDesk as Asobo will need to make changes to the core of the sim to reflect the CFD flight model" Thanks!

Hi, The 'Enhanced' package adds 4K textures, passenger cabin and dynamic seat-back cabin screens. It should have no effect on the aircraft's systems itself. It is also not mandatory to use this package and the A310 will work functionally the same without it. So what you are noticing are probably just bugs in general, not specific to the enhanced package. That is noted, the F4 (Full Throttle) command does not work currently. Are you talking about when you are flying? This is the correct logic and how it is in real life. . When either condition listed below is no longer true, the lights will automatically turn off. That is noted, there aren't any touchdown sounds simulated currently. There is a difference in the sounds, and is most noticeable in front and besides the aircraft. But feedback is noted, thanks! The way it is currently modelled this allows you to still maintain IDLE REV, but feedback is noted, thanks!

Thanks for the video and additional reports. We're looking into it.

Hi, are y'all using any scenery for LFSB as well? I have just flown a flight with the route below, once in GE F and once with PW Pax, with Navigraph Navdata (2405 rev.1) on SU15, with v1.1.1 of the A300 without any crashing issues. LSGG/04 N0473F300 MOLU4N MOLUS N871 KONOL Z59 LUMEL LUME8K LFSB/15 This is with a near empty community folder, no sceneries used for either airport. Not getting any WASM crashes throughout the route, even tried to change the STAR/APPROACH procedures multiples time in the air, whilst in a hold, from ILSZ15 to ILSY15 to ILSX33 to ILSY15, no crashes, and MCDU has changed the procs appropriately. In any case, we do have a new update for the A300 which will hopefully address the issues you are facing. Enclosed is a post shared on our discord. Please try that update (once available) and do report back if you still face such issues. Thanks!

Thanks for the reports guys, but as KSFO is a BMWorld & AmSim product, best to contact them directly (linked social) with bug reports and suggestions as they may not be monitoring our forums.

Reported, thanks!

Thanks for your question. I've shared with the team for a more detailed response of what the EFB is doing. But meanwhile, yes ideally all bearings used should be same (both Magnetic or both True) when making calculations. So you could make the adjustment by entering TRUE bearing for the runway, or by adjusting the reported True METAR wind bearing by MAGVAR. Thanks!

Thanks for the update. As noted here, we're working on it: