Eddie

We're working hard on the 1.0.9 update doing our best to ensure this no longer happens! Your patience is very much appreciated. Thank you

Hello, Thank you for the follow-up. This should be resolved with the coming 1.0.9 update 🙂

Oh my.. so.. I may or may not have misread the category. So used to replying to A350 threads. Terribly sorry!! Unfortunately, the A400M does not support physical input, no. I believe it has been requested to MS/Asobo in the past. We'll see if we'll be asked to implement this or not. Again, apologies and thank you 🙂

Ok thank you

Hello, Apologies, missed this. Can you clarify which of the autosaves is more relevant? We preferably need one. Thank you!

Hello, Can you specify what sounds specifically? Perhaps a short video of the problem so that we can investigate. Thank you 🙂

Hello, It should work simply by pressing it once. That'll enable physical keyboard entry. Are you sure you're selecting the field you want to edit prior to clicking LCTRL?

Hello, Thank you for the follow-up. I'll check in with the team on what could be happening here. It would be EXTREMELY helpful if you could record us a short video of this happening; easier to diagnose that way. Thank you!

Hello, You can press LEFT CTRL to enter the field you want to input data into, then ENTER to finalise. There is not a mappable command for the checklist, as far as I'm aware. Let me know if you have any more questions! Thank you 🙂

Thank you. I can still see it on our logged bug-list. Seems like it didn't make it into this update, unfortunately.

Hello, Please attach your full RTE OFP and which aircraft you're in (900/1000?); this way we can attempt to reproduce. However, if this does happen again, please create an autosave and share the file with us 🙂 Thank you!

Hi, Forwarded this too. Thank you 🙂

Hello, Thank you. Forwarded to the team! 🙂

Hi Seth, This will be resolved shortly as we finally found the issue. Thank you for your patience 🙂

Hello, I'm sorry to hear that you've experienced this. Your report as well as effort is very much appreciated. I've forwarded this to the team 🙂

Hello, Please update to 1.0.4 to fix the flickering issue - if it still is present, please try a complete uninstall then reinstall. As for the cloud issue, the team is aware. Thank you for the report! 🙂

Hello, I am very sorry to hear that you've been experiencing this. It's hard to pinpoint these issues because thousands do not have the issue you describe. Can you check "Event Viewer" if you're getting any crash error through there? See image: If its a WTF.DLL or CoherentUIGT.dll as the Faulting module in the crash, that is something to do with rendering engine memory+graphics drivers unfortunately as far as I've seen reported. Let me know. Thank you 🙂

Hello, The team is aware of the delay and mixup with the EXT button. As for the issue that you describe with the showcase camera, if it was an easy fix, it would've been implemented already. The showcase camera in its essence is not really supposed to be placed there regardless. Thank you

Hello, Thank you for the follow-up. This sounds like some kind of simulator issue in regards to fuel. When a device disconnects, the variable state is getting practically destroyed. I am not able to reproduce this whatsoever, and I MAY have a fix: For longer flights, double check your USB device sleep settings as it may disconnect automatically when no input is detected for a while. Let me know if that makes any difference. Thank you!

Hello Marcus, We'll take a look. Thank you 🙂

Hello, Apologies for the late reply. Can any of you please grab me a video when you are attempting engine start on turn-around? May help to see exactly what leads up to it. Thank you and apologies for the inconvenience 🙂

Hello, We're already aware. CU10 just came out 3 days ago. Also, apologies about the lack of attention to the LOD issue, I will prod the team regarding that again. I do want to note that I cannot see where I "promised" anything. I did exactly what I said. Thank you

Hello, Sorry to hear you're experiencing issues! Could you please record me a quick video demonstrating this? I'm thinking there may be some kind of binding issue or peripheral messing with your controls, but without a video I won't know for sure. Thank you 🙂

Hello, Thank you for the kind words! I'll check in with the team and see what we can come up with. Thank you for the suggestion! 🙂

Thank you, forwarded to the team!