Eddie

Hello, What you're describing is a "WASM" crash. They're very unpredictable and highly dependant on specific scenarios that the user is performing. Nonetheless, we can fix them, we just need some more information. If you're able to reliably reproduce this issue, please have the following guide (linked below) ready to report the issue using the template. Thank you and apologies of the inconvenience!

Hello, Please try clearing your scenery indexes: 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. Let me know if this resolves your issue.

Hello, Have you tried a complete uninstall then reinstall?

Hello, Are you using GSX?

Hello, I've logged everything you mention here. Apologies for the inconvenience!

Hello Linas, Thank you for the detailed report. Will forward this to the team. 🙂

Thank you, we've let the team know.

Hello, That sounds very odd. Please refer to my previous message in that case and check if you can reproduce this, if yes, please grab us the error as described in the linked post. Thank you and again, apologies for the inconvenience.

Hello, I've forwarded this to the team. Thank you

Lovely. Happy to hear 🙂

Hello, Uninstalling the aircraft entirely then reinstalling it usually fixes significant FPS issues such as these - please give that a go. Thank you

Hello, @Karl Lepp Please contact direct support like nixda has done. https://inibuilds.com/pages/contact Thank you

Hello Alex, You mean L-CTRL no longer working for you?

Hello, Looks like you may have a third-party mod installed, something to do with "lower res textures" etc. The mod author must update this mod to the later versions of the aircraft as we made changes to the model. Remove the mod and it'll be back to normal. Thank you!

Hello, Thank you, forwarded to the team. 🙂

Thanks, we'll take a look. I have yet to be able to reproduce this which still leads me to believe there's a binding issue (on keyboard for example) but alas, I've forwarded to the team.

Hello, Please uninstall the aircraft entirely and reinstall it. Seems like corrupt files. Thank you

Hello, This is a known issue but a tad bit tricky to figure out as it's not 100% reproducible for everyone. We are looking into it however. Thank you!

Hello, Thank you for the follow-up. Passed this on to the team 🙂

Hello, This does unfortunately boil down to either MSFS damage settings or key binds. Have you triple-checked nothing is bound to "mixture"? Are all your damage settings set to off? Thank you

Hello Ben, This sounds like a "WASM" crash. Please view linked post on how to report these appropriately so that we can action them accordingly. I am very sorry for the inconvenience. Also please state if this is the "PREMIUM" or "COMPATIBLE" version of the A300 for MSFS2024. Thank you

Thank you very much, Daniel. I've forwarded this to the team. Apologies for the inconvenience again!

Hello keino, This is a "WASM" crash. If you are able to reliably reproduce this, please report this to us using this "template" (linked below) so that we can action it appropriately.

Hello! In version 1.0.8, we have disabled the automated triggering of the ANF. We were meant to ship an update to the OIS for the user to be able to toggle whether or not they want the ANF to auto activate on landing, but that option didn't make it in unfortunately. So nothing you're doing wrong! We'll get this sorted for the upcoming update. Thank you and apologies for the inconvenience 🙂

Hello Lukáš, Thank you for the kind words! Would you mind grabbing me a screenshot of this happening? I've forwarded this to the team regardless. Thank you for the help! 🙂