I'm trying to map the Starter, which has three states: START, OFF, MOTOR which is 0, 1, 2. 

With (>L:XMLVAR_Starter1,·number) I'll get it to switch to desired position, but it switches back at once.

The AIRCRAFT ENGINE VARIABLE named GENERAL ENG STARTER:1, type bool, is 1 when switch is at START or MOTOR, 0 when at OFF.

I've found variables by MSFS DEV->Behaviour, but can't use ENGINE_Starter_Ignition_1_Set in a script in any way that works.

I tried using LVar to Bvar, which worked for Condition lever, but here it will only set it to MOTOR (2). LVar: (L:AAO_Start, number), BVar get:(B:ENGINE_Starter_Ignition_1, number), BVar set: (>B:ENGINE_Starter_Ignition_1_SET).

Below is also what I found in the XML file.

Here is what I see in Behaviour.

Is it just probably not possible with this model, or may I have missed anything?

Thanks again for all help, support and education.

 

 

-<Component ID="ELECTRICAL_PANEL">
-<UseTemplate Name="ASOBO_ENGINE_Switch_Starter_Template">
<WWISE_EVENT>electrical_switch_battery_master</WWISE_EVENT>
<AUDIO_DIRECTION>Both</AUDIO_DIRECTION>
<ANIM_EVENT_EFFECT_NAME>CAM_ENGINE_START</ANIM_EVENT_EFFECT_NAME>
<NORMALIZED_TIME>0.01</NORMALIZED_TIME>
<DIRECTION>Forward</DIRECTION>
<TYPE>3Values_StarterIgnition</TYPE>
<NODE_ID>ENGINE_Switch_Starter</NODE_ID>
<ANIM_NAME>ENGINE_Switch_Starter</ANIM_NAME>
<ANIM_LAG>800</ANIM_LAG>
<TT_DESCRIPTION_ID>@TT_Package.ENGINE_STARTER_ACTION_SET_1ENG</TT_DESCRIPTION_ID>
</UseTemplate>

 

46 minutes ago, Jackiie said:

I tried using LVar to Bvar, which worked for Condition lever, but here it will only set it to MOTOR (2). LVar: (L:AAO_Start, number), BVar get:(B:ENGINE_Starter_Ignition_1, number), BVar set: (>B:ENGINE_Starter_Ignition_1_SET).

Sorry, I don't have that plane. But I think that your BVar mapping is incorrect. IMHO it should be

LVar: (L:AAO_Start, Number)
BVar get:(B:ENGINE_Starter_Ignition_1)
BVar set: (L:AAO_Start, Number) (>B:ENGINE_Starter_Ignition_1_SET).

In your code, the starter ignition is probably set to 0, and that's it? There is nothing in there that would assign a new value to the BVar.

Thank you, it worked! I'm so happy when it's just me missing something 🙂

Side question, when I've just started the game, loading an aircraft cold and dark, the application doesn't seem to "see" what my levers and switches are set to. I need to move them once before AAO sees their position. E.g, I have the detent on the bravo (a button) set as Condition Lever Cutoff, but it doesn't see the button press before I move it out and in once. Also, it reads all the axes as being in the middle, not where they are IRL. Is this something that is possible to work around? Right now I'm moving everything after loading so everything will be set in the right place.

That happens with a lot of devices. They don't reveal the inital state until you move 'something'. On my devices I only have to move one lever to wake up the whole thing. There doesn't seem to be a technological solution within the library.

Edited August 23, 20223 yr by Lorby_SI

1 hour ago, Jackiie said:

when I've just started the game, loading an aircraft cold and dark, the application doesn't seem to "see" what my levers and switches are set to.

I'm still a noob to AAO, but the way I dealt with this issue in P3D/FSUIPC was to write a "Cold and Dark" script. Would do a cockpit check to put all switches in the cold and dark position, then run the script to set all variables to that position. (Many of the sim aircraft did not load in a complete cold and dark state.)

Not optimal but did the trick. 

Based on Oliver's response, AAO is more globally aware if only a single event change is required.

9 minutes ago, hs118 said:

I'm still a noob to AAO, but the way I dealt with this issue in P3D/FSUIPC was to write a "Cold and Dark" script. Would do a cockpit check to put all switches in the cold and dark position, then run the script to set all variables to that position. (Many of the sim aircraft did not load in a complete cold and dark state.)

Not optimal but did the trick. 

Based on Oliver's response, AAO is more globally aware if only a single event change is required.

Sounds like something I may try. It doesn't pick up the Honeycomb Bravo more than one axis at the time, and the problem may be that I always have the handles in the bottom position. It can't read condition lever as it's in the detent and not on the axis, e.g.