Inputs are sometimes ignored when Atmosphere Autopilot is installed and SAS is enabled

[digital-pet]

KSP version: 1.11.2.3077 (Windows x64)
OS: Windows 10 Version 10.0.19041.1052

Steps to reproduce:

• Starting from a fresh install
• Install the following mods and all dependencies:
• • Advanced Fly-By-Wire (Windows) version 1.8.3.3
• • AtmosphereAutopilot (Fly-By-Wire) version 1.5.16
• Open the attached vessel in the VAB and launch it

At the launchpad:

• Configure AFBW for pitch and yaw control
• Enable "AtmosphereAutopilot" compatibility in AFBW Settings
• Click the AtmosphereAutopilot toolbar button and select "Autopilot module manager"
• Verify that the window displays only two items: "MASTER SWITCH" and "Craft settings"
• Verify that with SAS disabled you see a response to pitch and yaw controls
• Verify that with SAS enabled you see a response to pitch and yaw controls
• Save and exit the game to desktop
• Relaunch the game and load the save you created and return to the launchpad

Issue:
Pitch and yaw controls from Advanced Fly-By-Wire will now be ignored on all subsequent loads only when SAS is enabled, and only until you open the AtmosphereAutopilot menu, select Autopilot module manager, and select "MASTER SWITCH" on every vessel load.

Workaround:
On every vessel load, open the AtmosphereAutopilot menu, select Autopilot module manager, and select "MASTER SWITCH"

Attachment:
AA conflict test.zip

[digital-pet]

Of note: In a game with far more mods, I am noticing that this workaround doesn't work when this issue presents itself, but I haven't yet found what additional mods out of the 100 or so are affecting input handling. Regardless, I've verified this happens reliably on my system with just the two mods listed installed.