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,
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!
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,
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
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! 🙂