Have flown the A220 on four flights now, and on three of them, long after takeoff and cleanup, I get the MSFS system malfunction pops up on the screen. On this last flight it happened later in the cruise portion, and my ACARS system for my airline doesn't pick up on the flaps being used at all. On Descent, the slats will deploy but the flaps will not. After landing, the visual of the aircraft shows the flaps fully deployed on the exterior model, but inside the flight deck, it shows fully retracted. Hardware is all Virpil and no issues show up in the synoptic pages. Any help would be appreciated as it's causing me some issues on landing.

Edited Saturday at 12:03 AM2 days by Korz

I completed my first flight today and had the same issue. The warning message in the OP's screenshot was shown, then on landing the slats deployed but not the flaps. At some point during the landing rollout the flaps then deployed, but stayed at flaps 4 regardless of what position was selected.

Edited yesterday at 11:02 AM1 day by Pabsbabs

I have the same issue on my flight when I tried to lower my flaps on approach.

Going to test this tomorrow by using the flaps only with my mouse instead of my Virpil hardware assigned switch. That should help with troubleshooting a bit.

I had the same issue and turning off crash and damage detection fixed the issue for me. Most payware planes like the PMDG's the Fenix and this A220 all have their own damage detection that interfear with the default one.

Try turning off crash and damage detection and verify if the problem can be replicated.

1 hour ago, Lerimer said:

I had the same issue and turning off crash and damage detection fixed the issue for me. Most payware planes like the PMDG's the Fenix and this A220 all have their own damage detection that interfear with the default one.

Try turning off crash and damage detection and verify if the problem can be replicated.

I fly PMDG on the regular, my crash detection has been off the whole time. Thank you though, that is important for 3rd party add ons.

I believe this was a reported bug to Synaptic and should be addressed in the upcoming patch, thanks!