richboy2307

Hi @crowdall3 That is a "WASM Crash", where in the WebASsembly Module (WASM) container that runs the code for various systems has failed, so those systems "stop responding / freeze" in place. The team is aware of them and working to debug and sort them as and when we are able to reproduce them. So for that, please share the following: route you were flying (i.e. active F-PLN) route you had as secondary (i.e. entered in SEC F-PLN) Navdata Used (Navigraph or Default) Airport Sceneries used (The Departure, Arrival and ALTN airport if any was part of the secondary flight plan) Where you were when you activated the flight plan. (Go around, but at approx what altitude and near which waypoint) All this info will help us to recreate the scenario in which you had a WASM crash, such that we can trace the source of the crash. Thanks!

Its technically possible, but not practical. To implement that, it would require a completely new base airport ".bgl" file that has those enabled, which would nearly double the storage footprint of an OMDB install. The extra storage space and bandwidth required is not a worthwhile trade-off for just a few additional gates for an airport that already has no shortage of them. So as it is not practical, the currently implemented solution is the most reasonable one. Thanks!

Hi @Ralgh This is intentional and modelling what has been observed by real operators of the type, wherein it is not perfect and you ought to take over manually if such a degree of speed control is absolutely necessary for your particular area/type of operations.

Thanks, will share with the team. Meanwhile, if you have any additional reference for this, please also add it below.

Hi @peter sefton Please ensure that your thrust is being applied evenly across both engines, also ensure you have disabled all AI Assists (Options > Assistance Options > PIloting). Also ensure you do not have any conflicting bindings for the Tiller / Nose Steering Axis and Rudder Axis in the control options. Thanks!

Release and timelines are up to Microsoft as it is their product. However rest assured that the team has been fixing reported bugs and improving the aircraft in the background 🙂

Yes it was moved as placing the PAPis in their real positions caused them to be un-aligned with the glideslope. The Glideslopes for 30L are in vastly different positions depending on whether you are using Navigraph or Default navdata. The current solution is a stop-gap that acts as a middle-ground for both datasets. Team is working on a more long-term solution. Thanks!

Hmm. @sevlowdev Can you try to clear the contents of this folder? It will force a re-compile of the relevant files the next time you load into the plane. Just in case it was somehow corrupted/not compiled properly initially. Steam: %APPDATA%\Microsoft Flight Simulator\Packages\microsoft-aircraft-a320neo MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\microsoft-aircraft-a320neo Thanks!

Thanks, noted.

Hi @riccardo74 Thanks for your suggestion, but it is unlikely until MSFS introduces a better system for doing so natively with the sim's save function as the A320Neo V2 is a Microsoft Product. So best you could do is re-spawn mid air, and use one of the panel states, or re-import your flightplan data via Simbrief. Thanks!

Hi, are you on PC or Xbox? There is no such pre-requisite for accessing ground services. In fact all of my flying I do without setting up anything on the world map, or importing any plans on the world map page. If you'er on PC, please try with an empty community folder to rule out any conflict with another add-on. Simply rename your existing community folder temporarily to "_Community". Run your testing, and when done, close the sim and delete the new empty community folder. Then rename the old one back to "Community" to restore all your addons as they were. The EFB Pushback is just using MSFS pushback commands on the backend. So the TOGGLE PUSHBACK button just sends the "REQUEST PUSHBACK" command which is normally used to spawn a tug, however owing to a bug in MSFS, this does not happen reliably, so sometimes it may appear as if nothing is happening. As you have noted, the AFT, LEFT, RIGHT and PUSH buttons actually control the pushback, which will work regardless of the tug spawning or not. This is the intended behaviour of the EFB pushback. Thanks!

Can't give an ETA I'm afraid, but it shouldn't be too long now, it is under another (hopefully final) testing round with beta testers. Thanks!

Hi @naval_guy Please try again in the upcoming A300 update and let us know if you're still having the issue after. Thanks!

Sorry you're having such issues. Countless other users/testers have spent hours with this plane already, since SU15beta till date without any such AP issues, barring misconfigured sim settings. So please check if all the AI assists are disabled (Assistance Options > Piloting) as they are known to cause issues with AP. Also ensure there's no active control input (aileron/elevator/rudder) being given that would cause the AP to not engage. Not to say the plane is perfect - there's certainly room for improvement but before public release there's many hours of testing put behind this plane already by both internal MS/Asobo and iniBuilds testers to ensure proper usability on PC and Xbox. Thanks!

Hi @TurboDonkey I'm afraid I don't understand. Can you please elaborate what is the "BS Issue" you're having? Thanks!

Could you record a short video clip / screenshots showing your PFD/ND and FCU prior to intercept and then right after where it hasn't captured it? Could take a look to understand better what may be wrong. In general though, you don't need to do anything on the MCDU other than fill in DEST DATA, and verify the correct frequencies on the RADNAV page. Prior to intercept, enable LS on your glareshield, and arm APPR on your FCU. You must be established on the LOC already, before GS can be intercepted, and also you must intercept the GS from below it, else it won't capture. Thanks!

Hmm, you sure you do not have some kind of failures enabled on the World Map? Also ensure that all the AI Assists are disabled (Options > Assistance Options > Piloting). The A320neo V2 does not have any maintenance mode, so that shouldn't happen on its own. If its happening every flight after the above, please close the sim and clear the contents of this folder as that will force the WASM to re-compile on next launch: Steam Version: %APPDATA%\Microsoft Flight Simulator\Packages\microsoft-aircraft-a320neo MS Store Version: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\microsoft-aircraft-a320neo Lastly, if that also doesn't resolve the issue, then try with an empty community folder, to rule out any addon conflict. Thanks!

That is not the case normally. Please try with an empty community folder, to rule out conflict with some other addon. You can just rename the existing community folder to "_Community", then launch the sim to test. After you're done testing, close the sim, delete the new empty community folder and rename the old one back to "Community". That is the quick way to test without having to re-install any addons. If it works properly with an empty community folder, then some addon is causing issues. You may have to do some trial-and-error testing to figure out which one. Outdated community liveries (for older SU14 version of A320Neo V2) and outdated versions of Horizon Simulations 787 are known to have caused issues for other users. Also I tested again on my system and was able to successfully delete it the first time, without issues: 2024-07-10 18-07-47(1).mp4 Thanks!

Hi @Bald kelp There is no such issue on the plane currently, nor been reported by anyone else before. After landing, you need to tap on your brakes to disabled the AUTOBRAKE. Please confirm you have disabled all AI Assists (Options > Assistance Options > Piloting). Also ensure you do not have any conflicting keybinds for parking brake/brake that may be causing issues. Additionally, ensure the chocks are not enabled from the EFB. If you are still having issues, please share a short video clip/screenshot of when you have the problem showing your entire cockpit (Overhead, Front Panel, Center Pedestal) Thanks!

Hi @rem31, English only please on the forums here. You simple hover your cursor over the SPEED SELECTOR or HDG SELECTOR knob, and press A button to interact with it. Then follow the on-screen instructions to adjust, and finally press B to quit. Also as mentioned above, you must have filled in the require information on the MCDU for MANAGED mode to work. Otherwise the AP will only work in SELECTED mode. Thanks!

Hi @Trane For your example of Runway29 at CYYC, if you look at the approach plate you'll note that ILS (IAQ 110.9) does not have any DME associated with it. This is why you see 0.0 on your PFD. Instead the approach uses a separate source for DME (IGY 110.55), and you can see that mentioned as the distance read-out for all the corresponding waypoints as well. So in this scenario, you'd tune the RADNAV page on the MCDU as follows: - IAQ/110.90 in the ILS/FREQ section - IGY/110.55 (enter it as /110.55) in either VOR1/VOR2 section on the top (as you prefer) Once you see that, enable VOR on the Glareshield and you will use that DME on the bottom left/right of your ND instead. I am not noticing this issue, just tested at CYYC RWY 29. Please ensure your RADNAV page is setup properly, that you arm APPR and intercept the glide from below the glideslope (it won't capture if you're already above it). Are you using Default or Navigraph Navdata? Also are you using any sceneries for the airports where you notice this issue? Also ensure your sceneries are up to date and do not have any add-on affecting all the airports, that may be causing conflicts. Thanks!

Hi @danlee957 Try again with the latest update. In case you see this again, please share a screenshot of it, along with where it happened (which gate number/Terminal) Thanks!

Noted. Thanks for the suggestion.

Hi, Are you using any addons like FSRealistic? That is known to cause issues for manual entry sometimes, the only fix being to exit to main menu and restart the flight. If you are having this issue on every flight, then please try with an empty community folder: rename your existing one to '_Community' whilst testing. When finished testing, delete the new 'Community' folder and rename your old one back to 'Community' If you do not have this issue with an empty community folder, then it is likely some addon that is causing conflict. Most likely culprits are outdated liveries or outdated version of Horizon Simulations 787 addon. Thanks!

Hi @BillM Are you using Navigraph or default navdata? Also can you specify which Airport + Runway + SID/STAR/APPROACH combination you had problems with? It is the correct behaviour to receive a NOT ALLOWED warning when trying to remove a F=PLN DISCONTUNUITY which has MANUAL entry above it. So you need to erase the MANUAL entry first . Once you have CLR on your scratchpad, clicking the L LSK next to the MANUAL waypoint should get rid of it. I'm not noticing any such issues on my end. Below is a video of KJFK DEEZZ5 SID out of RWY 04R with Navigraph Navdata: 2024-07-09 22-43-06(1).mp4 Also if you're on PC, please ensure your A320Neo V2 is updated to the latest version (1.0.17) in the Content Manager: Also lastly, if that doesn't work. Please try to delete the contents of this folder, as that will force the plane to re-compile the WASM next time you load it. Just to ensure it wasn't corrupted on initial launch: Steam Version %APPDATA%\Microsoft Flight Simulator\Packages\microsoft-aircraft-a320neo MS Store Version %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\microsoft-aircraft-a320neo Thanks!