hello

translated by google

thank you for this very good software that improves day by day

my wishes for evolution

here is what I would like as evolution in AAO

support for the powershell language

possibility to copy and paste a button assignment or axis assignment from a template to another template

to be able to resize the left column in the script edition window (we can resize the window but not the column which is annoying if we have long script names.

i don't know if these evolutions are possible but but still thanks for the regular updates

2 hours ago, ptimale said:

support for the powershell language

AAO will always only offer what the Windows Script Host can do, sorry. RPN is the only exception, where AAO has a processor of its own.

Windows Script Host - Wikipedia

You can call PS scripts from AAO, but you will have to figure out a way to transmit and receive data. (WINVARs, text files, IP stack?) I am currently thinking about an option to pass data to/receive data from an external script using the console/standard I/O. We'll see how that works out.

2 hours ago, ptimale said:

possibility to copy and paste a button assignment or axis assignment from a template to another template

You can already do that, with the template and the configuration editor dialogs.

2 hours ago, ptimale said:

to be able to resize the left column in the script edition window

OK, I will look into it.

Edited August 4, 20241 yr by Lorby_SI

thanks, for the feedback

i didn't quite understand the method to copy and paste button or axis assignments from the main AAO window

i don't want to copy the scripts from the script edition window but an assignment from template A to template B

with you a page number in the manual?

19 minutes ago, ptimale said:

thanks, for the feedback

i didn't quite understand the method to copy and paste button or axis assignments from the main AAO window

i don't want to copy the scripts from the script edition window but an assignment from template A to template B

with you a page number in the manual?

Page 42.

This is not done from the main dialog. There are separate dialogs, called from the Templates menu

Templates->Edit Templates

Templates->Edit Configs

The difference between a Template and a Configuration is understood?

Edited August 4, 20241 yr by Lorby_SI

I'm trying to understand the manual
for now I haven't managed to copy and paste
I don't understand

34 minutes ago, ptimale said:

I don't understand

• A "configuration" is the container that wraps the axis and buttons that you have assigned to a specific aircraft.
• A "template" is just a blueprint, a wrapper that contains a number of axis and/or buttons that you wish to organize separately. A template is not related to any particular aircraft!

Here is the main use case for templates:

Quote

Let us assume that you made a configuration for the default Cessna 152. When you load the 152 in the sim, AAO will look into its configuration database and load the associated config, so you can operate the axis and buttons within. When you add an axis or button to an aircraft, you are adding it to the configuration. This process has absolutely nothing to do with templates, those are an entirely separate thing.

Now let us assume that you have 4 buttons that always do the same thing in every aircraft that you have. Ideally you would now save these four buttons as a "template" - and then "link" this template to every aircraft that requires these four buttons. A "linked" template has the benefit that all changes that you make to this template are automatically present in all aircraft configurations that have it linked.

 

There are dozens of use cases between configurations and templates to utilize them, and there is no limit to your imagination. And each item has its own editor dialog, where you can add and remove things, and move them over from other templates or configs.

Here is another use case:

Quote

Imagine you made a configuration for an aircraft. Now you load a new aircraft, where you know that the controls will be the same. But as it is a new plane, axis and buttons lists are empty.
You have several options now:
1. "Templates->Apply other config to this aircraft" This will create a copy of another configuration for your current aircraft
2. If you have saved the previously existing configuration as a template, you can now either "apply" or "link" that template.
"Applying" will again create a new configuration that contains duplicates of all buttons and axis. Every change that you make for this aircraft is only valid for this aircraft, nowhere else. 
"Linking" means that the template is only "virtually associated" with the aircraft. You cannot change anything in this config. Every change must be done to the base template - and it will then be present in every aircraft linking this template.

Editing templates and configs can either be done with the aforementioned dialogs, or in AAOs "Offline Mode".

And there is one more use case: templates are the data items that can be shared with other users, by exporting and importing them.

Yes, this is a complex matter. Initially AAO only had the configurations. The templates are a later addition by request of some AAO users. Together they form a very powerful set of tools - but all that flexibility also makes it easy to lose your way. Not a lot that I can do about that though. 
 

 

Edited August 4, 20241 yr by Lorby_SI

thanks for this explanation

i finally managed to make a copy in my configuration

i will have to understand the difference between models and configurations

thanks again for your help

36 minutes ago, ptimale said:

for now I haven't managed to copy and paste

Apparently one can only copy items from a template to either a config or another template. I will look into that for the next version of AAO.

For you this means that you have to save the configuration that contains the desired button as a template first ("Templates->Save current setup as template")
Then you can use this sequence:  "Templates->Edit configs->select the target + double click it->"Apply template"->select the source and then the button you want using the checkboxes->"Merge"

But.
When you are saving the config as a template, give the first use case above some thought. Maybe this is a button that you want to share multiple times. Maybe there is even more than one button. Consider reducing the template to only those buttons you want to share and then "linking" it to every aircraft that needs those buttons.

Edited August 4, 20241 yr by Lorby_SI

I forgot a request

I have a mouse with Razer type buttons

https://www.razer.com/fr-fr/gaming-mice/razer-naga-left-handed-edition

would it be possible for the buttons to be recognized in AAO?

13 minutes ago, ptimale said:

I forgot a request

I have a mouse with Razer type buttons

https://www.razer.com/fr-fr/gaming-mice/razer-naga-left-handed-edition

would it be possible for the buttons to be recognized in AAO?

Sorry, no idea. Aren't those buttons programmable? If so, can't you program them to emulate joystick buttons or keyboard keys?