Atul

Hi @Eddie Creating a new topic here since an identical topic seems to have been tagged as resolved. However other uses except the author still face the same problem. And therefore this topic. Came back to A350 after a long while only to be greeted with the following message on EFB. - I'm currently on AIRAC cycle 2511 rev3. - My navigraph subscription is valid through 26 Nov 2025. Then I did the following: - Uninstalled the A350 and deleted its WASM folder. - Reinstalled the latest build via inimanager. - Booted up, the problem persists. - This happens when navigraph is attempted in linking through "open in browser" option. - Manually inputting the displayed code here Link Your Navigraph Account doesn't do anything. Could you please take a look at this?

It actually freezes. I haven't done a flight on A340 with their latest SimApp Pro update but my MCDU froze 2 out of 2 times in my previous flights once the compatibility was released. Liked you mentioned, buttons on the physical MCDU were responsive and made changes to the in-sim MCDU despite being on a frozen state. The only way I could get it working again during the flight was unplugging and replugging the MCDU. However, it took no longer than some 20-30 minutes until it froze again and again. Don't wish to be frustrated, but it appears that consumers are required to debug or fly with workarounds with literally everything that are brought to the sim nowadays. Or, maybe that's just how the software world is these days. The sim that you were able to fly finally after debugging things for 2 hours require debugging/ implying workarounds in other areas the next time you touch the sim. While it's okay to do so given the hobby itself. sometimes it does get tiring to the point where you just give up the idea of doing a flight. Haha.

Oh and also have to re-link & verify the plane with Navigraph from the EFB under Options> Third Party. Make sure you update the NAVDATA under the same page once linked and restart the sim. Hope it helps.

Just to understand better, are you using the Simbrief ID (digits) and not the alphabets? If yes, maybe try resintalling the aircraft (remove any A350 liveries from community folder) and clear WASM folder specific to A350. There's an official tutorial in the forum and also mention of SU Beta being mandatory. I was having upgrading NAVDATA from the EFB and only a clear installation as mentioned above helped sort that issues. Reading through a lot of issues throughout the forum, it also appears that the process above helps to resolve a lot of those issues. However, there's like a patch upcoming later today that should fix some items.