Eddie

Hello, This is on the to-do list for a future update, yes. 🙂

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, Thank you. Forwarded to the team 🙂

Hello, I'm not sure I understand. Just tried it on my end and it works just fine. Are you using an axis on the joystick or a button?

Hello, I'm very sorry to hear. Please use the linked guide on how to report these appropriately, that way we can help 🙂 Thank you

@mark75 @dectenor1 Hello again, For now, please use the "ATC COM" button on the KCCU, just below the screens. That should not cause any issues and let you use that page normally. Thank you

Hello, To you all that are having this issue, please attempt the flight in which you crashed using SIM DEFAULT NAVDATA instead of Navigraph source and let me know if that makes a difference. Apologies for the inconvenience. Thank you

Hello, Unfortunately that isn't possible due to how the scenery in its entirety is structured. We continue to look at ways to mitigate the LOD-popping, however, as it stands, Rich's comment above is the latest information regarding this. Apologies for the inconvenience gents. Thank you

Hello, Looks like I can reproduce this too. Apologies for the inconvenience gents. I've forwarded it to the team.

Hello, Thank you for the follow-up. I'll try to reproduce and report to the team in that case. Thank you!

That suggestion has already been made and the team is aware. No promises but we'll look into fuel persistence 🙂

Hello, Happy to hear. Enjoy! 🙂

Hello, Not sure as I haven't heard this before. I'll ask the team! 🙂

Hello, How is performance in the 1.0.4 version of the aircraft?

Hello. Yep, known issue! 🙂

Hello, Please try using the default navdata instead of Navigraph and let me know if that makes any difference.

Hello, Are you using NAVIGRAPH navdata as a choice in the OIS? Please try changing to default sim navdata and try again. Let me know if that doesn't happen anymore. Thank you!

Thank you. I've taken a look 🙂

Thank you for the detailed report. I've passed this on to the team and apologies for the inconvenience!

Hi, Forwarded. Thank you 🙂

Hello, Unfortunately no way to roll back, no. For testing purposes, can you please try using default sim navdata and see if you can reproduce these crashes? Thank you and apologies for the inconvenience!

Hi again, Forwarded to the team. Thank you for the effort as always 🙂

Alright. We'll look into it 🙂 Thank you!

This is intended behaviour, yes.

Hi, I've forwarded this to the team 🙂