6 minutes ago, Lorby_SI said:

You don't have to do that anymore. See above, when using the AAO InGame Panel, you can target BVars directly. No need for mappings.

If you are using v3.00 of AAO, there is a conflict between the new MSES LVar logic and the LVar to BVar mapping. If you are using the mappings, turn off the MSFS SU12 LVar processing in the "Application" menu.

AAO 3.0 bug list - AxisAndOhs Support - The AVSIM Community

Perfect! Working. Needed to update and RTFM.

My ATR config

Condition lever

Throttle (mind the Axis Min!)

 

Reverser (Button action, mind the Repeat:fast setting!)

Edited April 29, 20233 yr by Lorby_SI

18 minutes ago, Lorby_SI said:

The BARO knob is a weird one

aaah..couldnt get that to work...how exactly do we implement what you found ? not sure how that would be added  (sorry ) 

20 minutes ago, vsukpadman said:

aaah..couldnt get that to work...how exactly do we implement what you found ? not sure how that would be added  (sorry ) 

1. Go to "Scripting->RPN Script Editor"
2. Click on the "ATR" group in the list on the left - which you should have if you've imported Guenselis Scripts. If not, create it with the "Manage script group" button - or just select the default group "Scripts". It doesn't really matter.
3. Copy&Paste my code into the editor box. For example "(L:MSATR_BARO_1_DELTA,·Number)·3·+·(>L:MSATR_BARO_1_DELTA,·Number)" for an INC script
4. Give the script a unqiue name (box at the top) 
5. "Save as New"

When you are connected to the sim you can also test the script right then and there with the "Test" button.

Now you can assign the script to a hardware control, it shows up in the normal event treelist under the group that you've selected.

Also check out the chapter about "Scripting" in the AAO manual... 🙂

Edited April 29, 20233 yr by Lorby_SI

1 hour ago, Lorby_SI said:

Now you can assign the script to a hardware control, it

Brilliant..thank you..I had read the scripting part of the manual , but a lot of it was a little too deep  for the simple things I was trying to achieve ... again appreciate it ! 

On 4/29/2023 at 1:13 AM, Lorby_SI said:

You don't have to do that anymore. See above, AAO manual, Chapter 6 "InGame Panel": when the AAO InGame Panel is acvtive (you can hide it), you can target BVars directly. No need for mappings with AAO V3 and beyond.

Trying to get the condition levers programmed to no avail. Set them up as B: variables as in your screen shot. So I assume I have to have the in-game panel open. But it has a red border that stays on screen so I can't hide it. I must be doing something wrong. Even with it open the B: var doesn't move my condition levers. 

Thanks!

EDIT: Wasn't running AAO in Administrator mode. Seems to work now! 

Edited April 30, 20233 yr by haskell
RTFM

Hello @ll,

just as a reminder, you can make the InGame Panel disappear automatically by setting a special LVar:

1·-·(>L:AAO_PANEL_HIDDEN,·Number)

If you don't need the actual functionality of this panel (it does more than just pass through the BVars), call this script as either an Aircraft or Global Automated Script (see menu "Scripting") set up as "On Shot - Beginning". 

 

6 hours ago, haskell said:

EDIT: Wasn't running AAO in Administrator mode. Seems to work now! 

Correct. The InGame Panel wants to access the AAO WebAPI, and that is only active when the app is started with the "Run As Administrator" option (the two small green LEDs on the bottom right of the AAO screen have to light up).

Make sure to take a look at the chapter about the InGame panel in the AAO manual.

10 hours ago, Lorby_SI said:

Make sure to take a look at the chapter about the InGame panel in the AAO manual

Yep. If you notice the “reason for edit” I read the manual right AFTER I posted. LOL. Someday I’ll get that order correct. 🙂

It would be great to have some sort of AAO central repository to share control configurations for popular add-ons and hardwares like other tools offer. 

8 minutes ago, GCBraun said:

It would be great to have some sort of AAO central repository to share control configurations for popular add-ons and hardwares like other tools offer. 

I agree. I have found some on flightsim.to but I find myself often thinking surely someone has done this one already! 

37 minutes ago, GCBraun said:

It would be great to have some sort of AAO central repository to share control configurations for popular add-ons and hardwares like other tools offer. 

The only thing that could be shared are scripts. As AAO is working on a relativly low level of DirectX where controllers are concerned, you can't just share your config with another person - he/she would have to confirm each setting anyway, which is only marginally better that just doing it from scratch. You can do it, using Templates, but I'm not sure that it is really convenient. It works OK for exotic/unique hardware.

All the other stuff, like LVars, BVars, HVars are "common knowledge", and there are already websites hosting them.

In my experience the script packages on flightsim.to are ideal - because they are more or less complete. As scripts are organized into groups, it is desireable to keep them together. If you collect scripts for a certain aircraft from 10 different people, you will probably end up with 10 different script groups too. Plus scripts getting in conflict with each other...

Ideally the aircraft developers would provide a simple PDF that lists all custom controls and how they are to be operated from the outside (like PMDG, Leonardo, FBW do). It doesn't feel right that we as the end users have to figure this out ourselves, every time and again with every update. 

Edited May 1, 20233 yr by Lorby_SI

On 4/29/2023 at 8:24 AM, Lorby_SI said:

As always, it would be really great if the developer of the aircraft would add a simple PDF that lists all BVars and or LVars and required procedures. It doesn't feel right that we as "the community" have to invest a significant amount of our time into figuring this out ourselves. IMHO of course

I might be wrong but some of the variables look like they could have just been dealt with by the built-in variables of MSFS. If that is the case it is a shame since we could have (re)use an existing profile which would have made things a lot easier.

And you are right, when custom variables are necessary please make them readily available on the product page or the manual. Even a simple text file in the addon folder  would do.
 

Something weird here:

After installing 3.01 the Ingame Panel has a red border ALTHOUGH I run AOA in Admin Mode (the confirmation window opens when I start it). With the result that the condition levers don't work anymore. When I close the panel (not deactivate), the red border is still on the screen.

I tried so far:

Installed 3.00 again.

Read LVARS and HVARS+BVARS after a new installation

 

I'm a bit clueless now after trying this afternoon...

 

2 hours ago, Otto Groschenbügel said:

Something weird here:

After installing 3.01 the Ingame Panel has a red border ALTHOUGH I run AOA in Admin Mode (the confirmation window opens when I start it). With the result that the condition levers don't work anymore. When I close the panel (not deactivate), the red border is still on the screen.

I tried so far:

Installed 3.00 again.

Read LVARS and HVARS+BVARS after a new installation

 

I'm a bit clueless now after trying this afternoon...

 

The read border says that the InGame Panel can't communicate with the AAO WebAPI - did you change the WebAPI Port at some point? This will be reset to default 9080/9081 in the panel after a fresh install.

Are the two small green LEDs on in the bottom right corner of the AAO main windows?

Did you install any new software lately?

Sometimes Windows can decide to block the port for a while, try restarting the computer. Or change the port.