richboy2307

Hi, thanks for reporting. The cause unfortunately is core-sim related, specifically in the way it handles certain elements of WASM on termination of a flight session. As such, this issue can affect any aircraft using WASM and not just limited to any made by us. Reporting it on MS Forums is sufficient. We will be happy to make any adjustments if required on our end to give effect to such fixes. Thanks!

@Nuno Pinto Update, please see following post for instructions how to remove co-pilot: Thanks!

Please see below post for suggested solution:

Hi, yes the wingflex issue affecting all airbus planes is noted. Team's already working on a fix. Thanks!

See for reply:

Hi everyone, We are not able to reproduce these issues however other users have noted the potential cause is that the "streamed package" hasn't finished loading in full: Alternatively, you may try the following: Clear WASM folder: Re-download package: Try to Run the sim as Administrator and add exclusions for sim installation folders to your antivirus program. If all else fails, try a full sim reinstall. Thanks!

Hi @Prophet That is be design. The only way to silence is to hit the red "AP DISCONNECT" switch on the sidestick twice. This can also be used by assigning a key to "AUTOPILOT OFF" keybind in the control settings. Thanks!

Hi, Regarding this issue, this was recently also addressed on our discord by my colleague. I'll quote the reply given on discord below (it is applicable to all the default airbus aircraft): Thanks!

Hi @Kevin B/ @togapowerr I have tried TFFR -TFF and LFPO - LFRS on my end and did not experience any CTD or sim freezes (through simbrief import, SID/STAR selected). These sound like potentially issues caused by incompletely streamed packages or sim components. Please try the following: Clear WASM folder: Re-download package: Try to Run the sim as Administrator and add exclusions for sim installation folders to your antivirus program. If all else fails, try a full sim reinstall. Thanks!

Hi @specialsk Can't say I've seen this. Can you please check your assistance options to ensure that the AI Pilot settings aren't conflicting with the autopilot? Also under the Assistance settings, please turn the turbulence to "LOW" as the effect of the winds can be a big exaggerated for larger aircraft on the "REALISTIC" setting by default. Thanks!

That sounds like a control bindings issue, potentially conflicting inputs. Try to recycle your control profiles, and if you have other controls assigned with axis, ensure that the rudder axis is disabled on them. Alternatively it could be the auto-rudder fighting you, so please check the Assistance options and ensure all are disabled as suggested here: As for the nosewheel steering, if you're only using the rudder axis, please ensure the option is enabled on the aircraft EFB: As for rudder sensitivity, it will depend on individual hardware and you should adjust the curves/sensitivity to your liking. Thanks!

Hi @Norwenkel On the A330 there are effectively 2 switches for Dome Lights control: CTL Switch turns the Dome Lights ON or OFF. STORM / BRT / DIM controls the various brightness levels of Dome Lights when the CTL switch is ON. The lights are confirmed working on all the planes. However in some instances they may not show because of streaming issues. You may try to reload the aircraft, or force a re-download of the package by following these steps: Thanks!

As long as the "twist" is assigned to "RUDDER AXIS" in the MSFS control settings, then you should set the EFB option 'RUDDER CONTROLS TILLER' to YES. This will ensure that when you twist, it moves both the rudder and tiller together. When 'RUDDER CONTROLS TILLER' is NO then the "twist" only controls rudder, not the nose-wheel. Thanks!

Hi @Swagger897 Thanks for the feedback. Shared with the team.

Yes on airbus aircraft it is a pre-requisite for a lot of the AP modes, especially managed. Thanks!

For this use the Rudder Axis, and ensure the EFB setting is enabled. Please see guide here: All of these again sound like issues caused because the plane hasn't initialized properly as the necessary components haven't streamed in full yet. Please try the suggestions in the first reply to try and remedy that. Thanks!

Hi @johna320, please try: Thanks!

Hi @flying_dude Thanks for the feedback, but unfortunately at the moment not possible to define a fixed size for co-pilot avatars as they change dynamically. Moving it any lower would cause the co-pilot to simply clip into the seat. You can however disable the co-pilot if you wish. To do so: On the Main Menu, click your Username on top right corner to access the Pilot Profile page. Here, select 'Customize Identity' > 'Co-Pilot' and select the first option (/). Hit 'Save and Back' to confirm the setting. Thanks!

Duplicate post, for answer see:

Hi @ozzy s Thanks for the feedback, however that is not currently possible as the SDK documentation for integration of its features outside of the default EFB is not available. In any case, the decision for such feature implantations on A320Neo and the other Microsoft Airbus aircraft rests solely with them. So please post on the MS Forums for such requests. Thanks!

Hi @ffortin Unfortunately no as the model itself is different, not just the file structure. Thanks!

Hi @knich Are you still having the issue? If so please try the following: Clear the WASM Folder: Re-download the streamed package: If all else fails, reinstall the sim as some core files may not have installed properly. We're not able to reproduce such CTDs on our end. Thanks!

Hi @Dave Mass Its hard to say what may the issue without any screenshots or videos as to what you were seeing in the cockpit. Can you confirm you're using LOCKED or LEGACY interaction? Also what was your phase of flight? When you're stuck as such, try a direct to another waypoint in the MCDU and see what happens. Thanks!

Hi, the sidestick AP disconnect is mapped to the 'AUTPILOT OFF' keybind. Please assign a key to that in order to operate the switch. Thanks!

Hi @vschwarz504 Thanks for your report. I've passed it on to our team to see if there's anything to do on our end. However at a glance, to me it does seem like possibly some conflict in the navigraph navdata itself. Can you please also report the same on the Navigraph forums? Thanks!