Hello,

I see a weird behaviour when I want to merge a template into an aircraft configuration when the template already includes a linked template.

When I do not merge but replace (or apply to an empty config) everything works fine.
But when I merge, the linked template is not added as a linked template to the aircraft but the content is instead applied hard to the aircraft config (including e.g. aircraft automated scripts).
Also during the merge dialog when I can select what entries from the template should be merged there is nothing mentioned from the linked template.
I would expect to be added as an linked template (ignored when that aircraft already has that template linked), or at least offer to de-select those entries in the merge dialog.

And another thing regarding templates, when during export I de-select a script group related to that template, it still gets added to the exported file.

Seems a bit confusing to me.

Edited August 10, 2025Aug 10 by touchdown84

Those sound like bugs, I will put them on the list for the next version of AAO.

So I've taken a look at those items.

The first one was actually done on purpose. But they way you expect it to work makes more sense I guess. This will be changed in a future version.

Quote

And another thing regarding templates, when during export I de-select a script group related to that template, it still gets added to the exported file.

That is by design. The checked items in the list are those scripts that are bound to buttons, axis or autoscripts in the template. Removing them from the list would break the template. To avoid inconsistent exports you can only add scripts, not remove the ones that the template requires.

Edited August 11, 2025Aug 11 by Lorby_SI