Hello,
when you're in the aircraft (for example, TFDI MD11 in AAO), you can see the axis and button assignments.
If you switch to the "avatar" camera view, the axis and button assignments disappear, and if you return to the cockpit, they reappear.

Here's the problem: if you assign the "EXT_POWER_DOWN_UP" function to a joystick button using this script:
"0·(>K:#90142)·(SPLIT:100)·0·(>K:#90143)·" and you're in the cockpit and press the joystick button, "EXT_POWER" turns ON. If you switch to avatar view in AAO, the axis and button assignments disappear and become inactive (I should mention that the joystick button is still ON for "EXT_POWER"). Then, if you return to the cockpit in AAO, the axis and button assignments reactivate, and you press the "EXT_POWER" button in the overhead cockpit, "EXT_POWER" turns OFF. If you've assigned the same function to the battery, everything shuts down. It's quite inconvenient. Is there a way to work around this? Thank you in advance for your reply.

10 hours ago, target111 said:

should mention that the joystick button is still ON for "EXT_POWER").

So it is a switch, not a button? For that you need proper On/Off scripts. A single toggle, like you have there, IMO won't work. 

10 hours ago, target111 said:

the axis and button assignments disappear

That is because the Avatar is handled as its own vehicle, with his own set of controls. Changing back and forth between lt and the cockpit is the same to AAO as changing into a whole new aircraft. TMBK none of the events assigned in the plane would work when you are in the Avatar.

Edited February 16Feb 16 by Lorby_SI

Yes, it's a switch, and the script presses and releases the EXT_POWER button in the simulator, just like a mouse click. So, I set the joystick switch to ON (this presses and releases the EXT_POWER button in the simulator and sets it to ON), and I leave the joystick switch in the ON position.
When I switch to avatar view, the assignments in AAO disappear because AAO considers it a completely new vehicle.
And when I return to the cockpit and the joystick switch is still in the ON position, it presses the EXT_POWER button in the simulator again and sets it to OFF. So, it would be good to leave the axis and button assignments in the avatar view as they are in the drone view; this would avoid conflicts. It was just an idea. What do you think?

Edited February 16Feb 16 by target111

2 hours ago, target111 said:

And when I return to the cockpit and the joystick switch is still in the ON position, it presses the EXT_POWER button in the simulator again and sets it to OFF. So, it would be good to leave the axis and button assignments in the avatar view as they are in the drone view; this would avoid conflicts. It was just an idea. What do you think?

The assignments won't work with the Avatar, so there is no point in keeping them. Avatar is not just a view like the drone, it is a completely different "mode", essentially a different vehicle. It is not AAO just treatingt it as one, it actually is in the simulation.  Your aircraft cockpit doesn't exist in this mode. 

As I wrote, you need proper ON/OFF scripts. You cannot call the toggle on every action of the hardware switch, only when the ext power is actually on or off and you need it to change. Know what I mean? You have to query the state of the ext power, and then use an if{ clause to make sure that the button is only pressed when it needs to be pressed. 

If you don't do it this way, the switch will definitely get out of sync with the cockpit at some point. For example, just operate the button in the cockpit with the mouse and your switch will already be reversed.

Edited February 16Feb 16 by Lorby_SI

So these are the scripts

Ext Pwr On:
(L:MD11_OVHD_ELEC_EXT_PWR_ON_LT,·Number)·0·==·if{·0·(>K:#90142)·(Wait:100)·0·(>K:#90143)·}

Ext Pwr Off:
(L:MD11_OVHD_ELEC_EXT_PWR_ON_LT,·Number)·1·==·if{·0·(>K:#90142)·(Wait:100)·0·(>K:#90143)·}

Assign these scripts to your switch. The On script goes to the Key Down, the Off script goes to the Key Up action. Now it will have a deterministic behavior and can't get out of sync.

 thank you for your reply.