MMAACCXX

Hello iniBuilds, I experienced a bug regarding the initialization of the flightplan in the MCDU: Yesterday, I flew a flight between EDDM and KSFO. I aborted the flight in cruise. Today, I wanted to fly the flight again, with an other route. I loaded the flightplan as usual, using the the tablet -> My flight -> import from simbrief and then going to MCDU INIT page -> Inserting EDDM/KSFO. It loaded the old flightplan from yesterday, not the new one I created today. I deleted the flightplans in the WASM directory and started the flight again, now it loaded no flightplan in the MCDU. The solution was to also delete the simbrief.json, after a restart, the new flightplan could be loaded into the MCDU. Many thanks for resolving this bug! Best regards

Dear iniBuilds-Team, may I ask if it is possible to provide the MCDU data via SDK like it is done by other aircraft developers? I use the hardware MCDU by Winwing in combination with a Mobiflight profile, and at this time it doesn't seem to be possible to read the display data (https://de.flightsim.to/file/98668/mobiflight-pack-for-inibuilds-a340-300-winwing-fcu-efis-l-mcdu). It would be great for all users of hardware MCDUs! Many thanks for considering this possibility! Best regards

I had the same Problem and also I was able to see the response in BATC (with SU4 Beta). Thereafter, I flew the Fenix A320, and I got the missing CPDLC Response from the flight with the A340, so the message was definitely created, but not picked up by the A340...