Eddie

Hello, Please ensure your bindings are correct as well as any assistance options OFF in the MSFS settings. And you mention that you have set the EFB, you're referring to the "RUDDER CONTROLS TILLER" option, correct? Thank you

Hello, There is progress yes. Our iniManager guys are working on a complete software overhaul. No ETA unfortunately. I will personally update you all once this has shipped. Until then, this thread will be locked. Thank you 🙂

Hello, Apologies for the late reply. Is this still something you're experiencing? Thank you 🙂

Hello Benni, Thank you for the kind words! It is indeed on our internal roadmap. I cannot confirm when this feature will make its way to the aircraft but we want to implement it for sure. Happy flying! 🙂

Hello, Apologies for the late reply. There is currently a bug in SU3 Beta in regards to WASM aircraft in which the product may not behave as intended; this looks like a case of that. There should be an update to the SU3 Beta end of this week that may resolve these WASM issues. If you'd like a faster fix, rolling back to SU2, which is the stable simulator environment, will most likely resolve your issues. Thank you 🙂

I know you've mentioned already reinstalling, but for good measure, please try again. Delete the folder itself manually from the community folder then launch the iniManager to reinstall + clear WASM again. If all else fails, please grab me a video of this happening on the initial load-in. Thank you and apologies for the inconvenience 🙂

Hi there, Apologies for the late reply! Please see; Asobo is aware. As mentioned, there should be an update this week for the SU3 beta branch.

The joys of WASM crashes! 🥲

Hello, There is currently a bug in the SU3 Beta environment which does not allow WASM aircraft to properly initialise. There should be an update rolling out for the SU3 branch end of this week; whether it'll address this issue is unknown. The only "permanent" fix is to roll back to the SU2 stable version of the simulator. Thank you 🙂

Hello, Apologies for the late reply. Seems we missed this thread 😅 We are working on a massive overhaul of the iniManager already and are hopeful the new changes, including a new UI, will aid in better navigating your products page. Apologies for the inconvenience. Happy flying! 🙂

Hello, Thank you, logged.

Hello, Thank you, logged.

Hello, Thank you, logged.

Hello, Thank you, logged.

Hello Dylan, First of all, please ensure you do not have anything other than your intended key/peripherals binded to the spoilers. If that is correct, unfortunately we hit a roadblock of the hit-or-miss nature of replays in MSFS. Sometimes things function as intended and other times they do not. Unfortunately not something we can do as the replay system itself fails to register the correct movement of the flight surfaces. If you'd like to grab me a video just to take a closer look, be my guest and I'll try my best to help. Thank you 🙂

Hello, We're looking into what could be causing this. If you haven't tried already, please reinstall the aircraft. I will do my best to update you if we reach a solution. Thank you 🙂

Hello, Please try clearing your scenery indexes. This may resolve the issue. Let me know if not 🙂 To do that locate your folder by following the path below: MSFS 2020 MSFS 2024 Then delete the contents inside but leave the folder intact. The indexes will rebuild on next load of FS.

Hello, There is currently a bug in SU3 Beta in regards to WASM aircraft in which the product may not behave as intended; this looks like a case of that. There should be an update to the SU3 Beta end of this week that may resolve these WASM issues. If you'd like a faster fix, rolling back to SU2, which is the stable simulator environment, will most likely resolve your issues. Thank you 🙂

Hi there, Thank you for the effort. I'll forward this to the team and we'll see what can be done. We are however waiting for SU3 to stabilise further to dedicate more work on show-stopper issues. Thank you and have a lovely day 🙂

Hello David, Please ensure the iniManager is using the correct community-folder path. You can use the "Scan Now" button under settings (top left) to make sure the correct path is selected automatically. Let me know if that doesn't resolve it. Thank you 🙂

Hello, Very sorry to hear this. It is quite unfortunate seeing as many have had hundreds of flights with no issues. I am of course not dismissing your very valid concerns here. I've forwarded this to the team. Out of curiosity however, are you on the SU3 Beta? If yes, does completing the same flight on SU2 make any difference? Thank you

Hello, Thank you for the report. I'll forward this to the team. Apologies for the inconvenience, not very fun having to deal with these WASM crashes.

Hello, There is a bug in the current beta build (SU3 Beta) that is preventing planes that use WASM from initialising, which in turn, causes all this to happen. I believe there's an update to the beta branch this week that could potentially resolve this issue. For a faster "work-around" and to have general simulator-stability, it is recommended to roll-back to SU2 which is the stable simulator environment. Thank you 🙂

Hello, I'm afraid this would look too toy-ish in the simulator if we made this adjustment. I'll pass the feedback forward but I wouldn't count on this being implemented. Thank you 🙂

Hello! Please ensure no assistance options have been toggled on in the MSFS settings. Please also double check that you have nothing accidentally bonded to "mixture" in the settings as well. Alternatively, reinstalling the aircraft may help. Apologies for the inconvenience!