richboy2307

Hi @Timm Turner Please ensure all your AI assists are disabled (Assistance Options). The conditions that could trigger an AP disconnect include input on your stick (elevator or aileron axis) or also on the rudder (rudder axis). Please check your bindings as well for any conflicts/double binding or "noisy" axis inputs that could be causing this. Thanks!

Thanks for the feedback, noted and shared with the team.

Hi @chard757 Just to confirm, you are only noticing this issue on the ONUR AIR liveries, and not on any other liveries for the A300? Thanks!

Hi @michel racicot This is a known issue and will be addressed in the next update. For now you can clear the message by pressing the 'CLR' key on the MCDU. Thanks!

Hi @Luvbeers, In which phase of flight, and where (cockpit, cabin, external cam)? Would be ideal if you could record a quick video clip (with audio) for when you are noticing the issue. Thanks!

Hi @WallyWalt, Can you share a screenshot of your PFD + FCU when you are noticing the issue? Also is this happening regardless of which procedure (STAR/Approach) or only on a specific one? Thanks!

For testing purposes, can you also mention the data you entered for your custom PBD waypoint? As currently i'm not able to reproduce a WASM crash (MCDU module freezing) after adding a PBD, and then deleting the "wrong" waypoint which was part of the VOR Y 29 procedure. Thanks for the other detailed write-ups @Azlog. Logged for further investigation, thanks!

Hi @CDM Firstly, welcome to MSFS! Hope you have a great time flying around! Secondly, you cannot install "add-ons" (or Mods as some call it) from PC/Mac to Xbox version of the sim. You can only download add-ons (usually via purchase, but some are free) for MSFS on Xbox through the in-game marketplace itself. You may watch some videos on youtube to help understand the marketplace better: https://www.youtube.com/results?search_query=msfs+marketplace+explained Thanks!

Hi @Concord This will only happen with 'GSX Pro' add-on installed, also only on the user aircraft. There is no simulation of boarding/deboarding for statics or AI planes in this scenery. The people modelled are also static, and not moving dynamically inside the terminals. Please check your iniManager. Select the EGGW from 'My Products' section on the left, and ensure all the options are enabled (such as 'Detailed Interiors' and '3D People'). All changes will take effect next time you restart the simulator. Thanks!

No there are no plans to develop for P3Dv5 currently. Thanks!

Hi @lfrivera Please ensure you are running the latest version of FSUIPC 7. I have been running the A320neo with FSUIPC v7.4.11 without issues for the past few months. (Specs: 5800X3D, 3090, 32GB DDR4 RAM) Thanks!

Hi @Andy J, The glass avionics are disabled by MSFS (hence black screens) on X Box whenever you are running out of memory (RAM). What that means is you have too many things loaded into your sim, perhaps too much traffic, or scenery objects (dense scenery) for example. So try to reduce traffic (Aviation/Airport Life/Land and Sea Traffic categories) to see if it helps in such situations. Thanks!

Hi @kekki Yes that is correct, the plan imported/inserted manually into the MCDU will not be read by the in-game ATC. This is because the A320neo (v2) is not using the in-game planner for LNAV. For the in-game ATC, you need to import/set your flightplan on the World Map before loading into the flight. Then you need to import/manually insert your flight plan on the MCDU/EFB seperately. Thanks!

Hi @neagabi Could you try to delete the contents of these folders? It should regenerate these files when you load into the A310. Steam: %APPDATA%\Microsoft Flight Simulator\Packages\microsoft-aircraft-a310-300 MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\microsoft-aircraft-a310-300 Thanks!

Hi @Superdraco2 Please ensure you don't have any assists enabled (Options > Assistance Options > Piloting). Even if you didn't have them enabled before, do cross-check as MSFS has a tendency to re-enable them sometimes whenever it updates. Other users who reported such issues were able to resolve it after disabling the AI assists. Thanks!

Thanks, @Mathlets, can you also post your specs? (CPU/GPU/RAM/Storage Type (ssd or hdd))

It means the bug is logged internally for the dev team, and they will address it in a future update if possible. Unfortunately that is not something that would be user configurable, and will not be implemented as an option. Thanks for the suggestion though.

Hi @SylentPG, Perhaps try to clear the contents of this folder. It should regenerate these the next time you try to load into the plane: Steam Version: %APPDATA%\Microsoft Flight Simulator\Packages\microsoft-aircraft-a320neo MS Store Version: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\microsoft-aircraft-a320neo Thanks!

Hi @tut123 For which airport are you noticing this issue? Can you post the route used (e.g. YBBN/01R N0265F040 DCT CITEE DCT NOMEV DCT VERIK DCT IRPOD DCT YBCG/32) Also are you using Navigraph or default navdata? Thanks!

Hi @Giuliano Arruda I haven't noticed this myself, nor seen it reported by any other users till date. Are you landing with the AutoThrust (AT) enabled, or is this happening with manual throttle control? If manual, can you check your throttle calibration? It seems like the "IDLE" position on your throttle axis may be configured to TOGA perhaps. Toggle the 'REVERSE ON AXIS' setting to force reset the existing calibration, then calibrate again with your desired settings. If with AT, as if conducting an auto-land, you will be able to regain control of throttles by disconnecting AT. Also ensure you have retarded your physical throttle levers (if using hardware axis) to IDLE prior to touchdown as during ROLLOUT, the AT will disconnect and then your hardware axis becomes active. So if the lever wasn't already in IDLE, but instead at TOGA as set during takeoff, then the problem can occur. Thanks!

Hi @Geoffrey Hargreaves You need to use the rudder axis to steer, and before that ensure you have ``RUDDER CONTROLS TILLER`` option enabled on the EFB. Additionally, the A320neo uses the new ground-handling as introduced in SU15, meaning for tighter turns you need to go slower (~10kts or less) or else the inertia of the plane will cause the wheels to skid and reduce turning ability. As for Simbrief, you need to enter your Simbrief Pilot ID (Numbers only) on the EFB (Options Page) & MCDU (MCDU Menu > ATSU > Pilot ID). For Xbox, ensure you have enabled the ``ON SCREEN KEYBOARD`` from the EFB options, and use that to fill in the ID on the EFB. If you use the 'Xbox Overlay Keyboard", it may not accept the value entered, even if it shows on screen. Thanks!

Hi @Skycowboy You could reach out to support (or reply to the email) with other means of proving proof of purchase/identity. As for making changes manually, I'm not sure if the marketplace version will encrypt these files (usually not), but you could manually disable the statics .bgl file. You will find it in the 'Official' packages folder under ``inibuilds-airport-omdb-dubai`` folder. Rename the ``omdb-scene-statics.bgl`` to something like ``omdb-scene-statics.disabled``, then update your layout.json file (please keep a backup of the original before making changes). Thanks!

Hi @mido2040 The team is already aware of the reports of performance issues by some users and looking into it. Thanks!

Hi @Timm Turner The flightplan you set/import in the World Map will not be loaded automatically into the plane. You need to either: Enter it manually in the MCDU, OR Import your Simbrief flightplan into the EFB (Dashboard Page > Simbrief Icon) and MCDU (INIT Page > select INIT Request) To import from Simbrief, you need to set your Simbrief ID on the EFB & MCDU first as follows: EFB - Go to Options page > enter Simbrief Pilot ID (Numbers Only). You can enable the ON SCREEN KEYBOARD option too from below to help you fill it in. MCDU - Press the MCDU Menu button > select ATSU > Enter your Simbrief Pilot ID (Numbers Only) Thanks!

Thanks for sharing @skydiver6547 Ok I found the issue. If you're using a single `Throttle Axis``,, then the issue you described occurs. However if you are using ``Throttle 1 Axis`` and ``Throttle 2 Axis`` (which is what I was doing as I have 2 separate levers on the BravoTQ, one for each engine), then it is working properly. The bug is logged and we'll look into it. But in the meanwhile, you can get around this by assigning the same axis (Joystick L-Axis Z as you mentioned above) to both ``Throttle 1 Axis`` and ``Throttle 2 Axis``. Do not use `Throttle Axis`. As below: Thanks!