Boris-Barboris

No (

https://github.com/Boris-Barboris/AtmosphereAutopilot/releases/tag/v1.6.0 Introduce AoA-Hold controller that holds desired AoA setpoint. Can be controlled by pitch hotkeys.

Small usability release. https://github.com/Boris-Barboris/AtmosphereAutopilot/releases/tag/v1.5.19 Make use_breaks globally serializable. Do not override manual breaks usage under target speed in ProgradeThrustController.

Hi, I suspect these are the problematic parts: You have FAR installed, but the parts under the spoiler do not use FAR control surfaces. Try looking into their modulemanager configs or asking a mod author for FAR compatibility.

Sorry, but they won't properly work together, it's just doesn't stack that way. Anyway, thanks @HebaruSan for a bugfix for non-alphabetical vessel names: https://github.com/Boris-Barboris/AtmosphereAutopilot/releases/tag/v1.5.18

Craft settings are just shortcuts to moderation parameters. If some craft misbehaves badly, editing them shouldn't help much. In general, AA's default tuning is best for agile crafts with a lot of authority and CoL close to CoM. Describing how exactly more advanced options work is quite laborious. If you have, let's say, pitch problem, you can try to play around with quadr Kp of the respective angvel controller. Don't expect wonders though. Most parameters are described on github readme: https://github.com/Boris-Barboris/AtmosphereAutopilot Parameters that have Kp in their name should probably help you the most. I'd say it's smarter to just use the right tool for the job, which is, apparently, SAS for some of your crafts.

Unfortunately, you can't. AA's code needs to be changed. If it's very important to you, you'll have to uninstall AA

It's not designed to handle quadrocopters, only conventional planes.

No. Not a bad idea though.

@Morse, do you think the problem of the guy one post above is the same as in your post?

1). Shift+<Hotkey> does that IIRC. 2). That would prevent you from pre-configuring stuff before enabling AA. Sorry, no, I just put my trust in Lisias's eventual victory and do other things.

test the release

You can also try to increase thrustProviderModuleIndex by 1 in part config. AA moves Gimbal modules to the head of module list, so all other modules before gimbal have their offsets increased by one. Oh, I see, AA already fixes thrustProviderModuleIndex, but only for first ModuleSurfaceFX it finds. That explains why deleting the second one fixes the problem. Can you give me the part config? I don't have a DLC.

Guys, logs.

What you see is Specedock's notification about me stating that old 1.5.16 (that was created to tackle KSP 1.8.0) still works under KSP 1.12.1 There is no new release.