Vibora

In fact, that was not the issue. It was a problem with one specific file that for some reason didn't commit.

Yes, other fixes are included in this update. For some unknown reason this one didn't make it through, though it should have been the case. As Javier said, we apolozige. It should be included in next third parties update.

Input command added. Wait for a next update (definitely not immediately next one but the one after most likely).

It is "Declare" command in the AWACS radio menu.

Hi Hrundel. We already have a "declare" command and it works.

Thanks for your report. The BE doesn't have that switch, so there should be no binding for it in that version. Fixed internally.

To save you time, I suggest you start/try with this version of the trk provided (saved as mission file). I narrowed it down to two triggers. Deleting a few rules inside those triggers recovers fps, but the ultimate reason is yet unknown.LastMissionTrackUSER-used only two red INCREASE FLAG triggers-lowfps.miz

Did you try a simple mission? Just and F1 with no triggers in the mission? It seems that there could probably be an issue with triggers, specially AI TASK PUSH trigger, though it's not confirmed yet, it needs investigation.

It is planned, working on it but we can't provide a timeline.

CC and EB have different ways to control the pitch to hold. In CC, the TCS button is used to set a new pitch. In EB, the attitude pitch knob on the ADI is used for that.

Both fixed internally. Thanks for your report.

Thank you very much for your feedback GrayFox23! This is really out of the ordinary.

Thank you for your report, we'll fix it.

You won't have to wait too long.