Eddie

Hello, Forwarded to the team. Thank you! 🙂

Hello, Thanks for the report! Will pass this along 🙂

Hello, Apologies Luke, seems this post was missed. Can you provide a few more details on the issue?

Hello, Like Alex mentions, we're aware and a fix will roll out with the next update as we are providing the option to enable/disable ANF via the OIS; unfortunately the toggle option didn't make it into 1.0.8. Apologies for the inconvenience gents. Thank you

Hello, What is your turbulence setting at? Is "AP DISCON PROTECTION" on in the OIS?

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

Hello, Thank you for the report. Apologies for the inconvenience!

Hello Bill, This happens sometimes as the new WASM compiles over the old with new versions. Have you tried clearing your WASM folder and attempting this again? If yes, can you please send your routing and I'll try to reproduce. Guide on how to clear WASM folder: Please let me know how it goes. Thank you! 🙂

Hello, Thank you. Forwarded to the team 🙂

Hello, Thank you for the extensive post! I've forwarded this to the team and we'll take a look 🙂

Thank you, Also logged 🙂

Thank you, logged.

Hello, Apologies for the late reply to this. Forwarded to the team. Thank you

Hello Matt, We're aware of the no auto brake off call out as well as the ANF as per Haza's comment. Your suggested fix is what we've been suggesting people do but with the next update we'll have a little more customizability for this.

Hello, Passed this on to the team as well, thank you.

Hello, Thanks, forwarded to the team.

Hello, Will forward your suggestion to the team. Thank you!

Hello, I have tried now on 3 different flights to reproduce this but have never had an issue with the input disappearing. All I can think is that there's perhaps some binding on a peripheral that is messing with it occasionally. I'll check in with the team if they can reproduce this as well.

Hello, Sounds interesting. Do you have a scenery installed for this airport?

Hello again, This is tied to the issue you reported the other day. We have already resolved it for the next update. I gotta admit, that second shot made me laugh. Regardless, apologies for the inconvenience. I'm sure doing longer turn-arounds are not fun when this happens.

Hello Lukasz, Is this something you're still experiencing on 1.0.8? Thank you

Hello, Thank you for the follow-up. I've forwarded this again to the team.

Hello again, Team has gotten back to me regarding this - the logic for when these lights are in use has changed to better match the FCOM. We've made a guide (linked below) on how to operate these in the latest version. Thank you

Hello, I'll forward this suggestion to the team 🙂

@Seth2413 Tagging you for visibility incase you missed the above reply 🙂