Flight altitude dec

38 (>L:VC_Air_Systems_trigger_VAL, number)

Flight altitude inc

39 (>L:VC_Air_Systems_trigger_VAL, number)

Land altitude dec

40 (>L:VC_Air_Systems_trigger_VAL, number)

Land altitude inc

41 (>L:VC_Air_Systems_trigger_VAL, number)

 

But in my experience if you load via Simbrief these are set automatically.

Edited June 19, 2025Jun 19 by pegeka

5 minutes ago, pegeka said:

But in my experience if you load via Simbrief these are set automatically.

In that case you could acess the SimBrief variables, using the Simbrief Download feature in AAO (=the app can download your simbrief package and you can access all values in it via LVars)

I don't think that you can access the values in the iFly plane, most of them only "live" inside their WASM - no need for extra LVars. You could access the LVar that is controlling the animation, but that one "rolls over" each full turn, so you never know the actual value that has been dialled in.

Edited June 19, 2025Jun 19 by Lorby_SI

I can use the LVars quoted above to dial in the altitudes in the plane.

What I meant is that you don't need to dial them in yourselve when using simbrief to load the route.

8 minutes ago, pegeka said:

I can use the LVars quoted above to dial in the altitudes in the plane.

What I meant is that you don't need to dial them in yourselve when using simbrief to load the route.

Sorry, post mismatch. My answer was to the question that @Bam2000 asked earlier, which was how to acccess the current value of those altitudes. And since there are no sim variables, the alternative would be reading them from SimBrief - assuming that those are really set automatically. Of course that doesn't help when the use case is displaying the value somehwere else (StreamDeck, Gauge, etc.) while you are turning the knobs. That's not possible with these particular values.

Edited June 19, 2025Jun 19 by Lorby_SI

For anyone interested, I made a template for the HoneyComb Bravo today (=for the iFly 737). It is available on flightsim.to and the axisandohs.com website.

Hi Lorby,

I tried to programm a joystick button to set TOGA on Ifly MAX using your exemples above, but no results. But when I press the test button on your program that send command to the Ifly, so the Variable works.

Any idea?

Thanks

Arnaldo

16 minutes ago, Bagarie2 said:

Any idea?

Not without a lot more information about what you did and how you did it.

I added a TOGA button to the new template just 20 minutes ago, no issues.

15·(>L:VC_Automatic_Flight_trigger_VAL,·Number)·(SPLIT:100)·16·(>L:VC_Automatic_Flight_trigger_VAL,·Number)

Please note that the iFly is not like other planes. It doesn't have singular variables for each button or lever. Instead, it only uses a handful of LVars that you have to set to specific values for key up and key down. The most important part with the iFly is not finding the variable - but finding the specific code/value that you have to use to make it operate a specific switch or button.

 

Edited June 19, 2025Jun 19 by Lorby_SI

I used your examples above you posted for the HDG SEL button, I just only changed the value 15 (for key press) and 16 (for key release),at (VC_Automatic_Flight_trigger_VAL,number) according to the values I read on the xml file on Ifly folder, as you wrote. 

I try to post a picture of what I did. 

Thanks,Arnaldo

 

10 minutes ago, Bagarie2 said:

I used your examples above you posted for the HDG SEL button, I just only changed the value 15 (for key press) and 16 (for key release),at (VC_Automatic_Flight_trigger_VAL,number) according to the values I read on the xml file on Ifly folder, as you wrote. 

I try to post a picture of what I did. 

Thanks,Arnaldo

 

To avoid typos, use "Scripting->Read LVars from sim" first. After that process completes, you can simply select the LVar(s) from the normal event treelist with the mouse/double click.

Edited June 19, 2025Jun 19 by Lorby_SI

Sorry, but I don't typo, I copied and past directly to the "Key down event" box and "Key up event" box. The strange is that if I press the small "TEST" button below the Key event Box, that send correct value to the Sim and select TOGA on Ifly. I hope I had explain well.

Arnaldo

43 minutes ago, Bagarie2 said:

Sorry, but I don't typo, I copied and past directly to the "Key down event" box and "Key up event" box. The strange is that if I press the small "TEST" button below the Key event Box, that send correct value to the Sim and select TOGA on Ifly. I hope I had explain well.

Arnaldo

Sorry, no idea. Working absolutely fine for me.

 

Edited June 19, 2025Jun 19 by Lorby_SI

Hi,

I solved the question. I don't know exactly how, but doing many things, finally I figure out to make to work. 

Thanks for  your help

Arnaldo

Hi, 

I know this topic is almost one year old, but I have a question regarding My licensed Lorby AAo Vs VRI MCP COMBO II.

Using the Combo Bridge I've been able to bind almost all the functions of the iFly B737 MAX to my MCP COMBO II, but a couple of things are remained unsolved;

1) The course encoder is not sending data to the plane, it shows always 000, but if I turn the Course knob in the virtual cockpit the value comes correctly shown on my display.

I tried to edit the Combo Bridge profile, but I'm not able to write the correct instructions.

This is what I found in the iFly737Max_INTERIOR_178.xml

<Component id="VC_Course_1_SW" NODE="VC_Course_1_SW_Obj"><UseTemplate Name="ASOBO_GT_Anim_Code">

<ANIM_NAME>VC_Course_1_SW</ANIM_NAME>

<ANIM_LENGTH>120</ANIM_LENGTH>

<ANIM_CODE> (L:VC_Course_1_SW_VAL,number) </ANIM_CODE>

<ANIM_LAG>120</ANIM_LAG>

<ANIM_WRAP>True</ANIM_WRAP>

</UseTemplate>

<UseTemplate Name="ASOBO_GT_MouseRect">

<TOOLTIPID>Course Selector</TOOLTIPID>

<MOUSEFLAGS>LeftSingle+WheelUp+WheelDown+DownRepeat+RightRelease</MOUSEFLAGS>

<LEFTARROW>TurnLeft</LEFTARROW>

<RIGHTARROW>TurnRight</RIGHTARROW>

<CallbackCode> (M:Event) 'LeftSingle' scmp 0 == if{ (M:RelativeX) 0 > if{ 12 (>L:VC_Automatic_Flight_trigger_VAL,number) } els{ 11 (>L:VC_Automatic_Flight_trigger_VAL,number) } } (M:Event) 'WheelUp' scmp 0 == if{ 12 (>L:VC_Automatic_Flight_trigger_VAL,number) } (M:Event) 'WheelDown' scmp 0 == if{ 11 (>L:VC_Automatic_Flight_trigger_VAL,number) } (M:Event) 'LeftRelease' scmp 0 == if{ 89 (>L:VC_Automatic_Flight_trigger_VAL,number) } </CallbackCode>

 

But, wich is the code to be used to increase and decrease the course value in the DME function of the Combo bridge Radio Editor (in the same window I have DME with speed and Course selection, all is working except the course).

 

2) in the Autopilot section of the MCP COMBO II the Speed Encoder sends correctly outputs to the Virtual Cockpit, but without show the value, in the COMBO display is always shown 000, while in the VC the value changes.

 

Ty for your help.

 

Mauro

1 hour ago, zetato said:

1) The course encoder

I would use the Mouse Wheel code

12 (>L:VC_Automatic_Flight_trigger_VAL, Number)

and

11 (>L:VC_Automatic_Flight_trigger_VAL, Number)

1 hour ago, zetato said:

2) the Speed Encoder

Sorry, no idea. You would have to find the correct variable that contains the desired value and enter it in the display profile on the VRI bridge program.

Edit: apparently, iFly does not expose certain values, including this one. There is a tool on flightsim.to that creates the missing values as LVars, and those should then be available to AAO too. Look for "add lvar for ifly" on fs.to

*****************************************************************

Disclaimer: I don't have any VRI hardware, I am just guessing

Edited March 2Mar 2 by Lorby_SI

Thank man, it works!!

I tried something similar before but I was wrong in the syntax!!

Thank you very much!!

Mauro

 

Edited March 2Mar 2 by zetato