Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Profile for the iFly 737 MAX

Featured Replies

Hi,

I know it is freshly out.

But any planning to add AAO script for this addon ?

  • Replies 68
  • Views 11.3k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Always happy to help out the competition. 

  • clarklidbury
    clarklidbury

    I am not sure which software you are using but here is the general idea of how i achieved this: To set the position lights to strobe and steady I would send the LVAR VC_Miscellaneous_trigger_VAL

  • iFly 737 MAX StreamDeck XL & PLUS profile & AAO Scripts for Microsoft Flight Simulator | MSFS   A little bit patience ... I will implment hopefully as much variables as possible the

  • Commercial Member

OK, so I got the preview.

It looks like iFly is making use of LVars, but in a novel way, not seen before. 

From what I can see you will have to model both the key down and the key up for them to work properly. The LVars are supplied with different values for the press and release actions. That also means that if you are using single action scripts (=scripts that have to do both actions), there will have to be a delay between the press and the release action.

There is not one single LVar per button/lever/switch, instead there are genereal purpose LVars that have a multitude of functions, depending on the supplied value.

Example: (L:VC_Automatic_Flight_trigger_VAL, Number)

  • 31: AP Alt down
  • 32: AP Alt Up
  • 55 followed by 56: trigger alt hold
  • 33 followed by 34: Alt INTV
  • 51 followed by 52: trigger HDG SEL
  • etc.

You can assign that directly in the AAO buttons (I will post screenshots about how to do that).

In scripts, it would look something like this:
51 (>L:VC_Automatic_Flight_trigger_VAL, Number) (SPLIT:100) 52 (>L:VC_Automatic_Flight_trigger_VAL, Number)

To find out about the values, use the MSFS developer mode, Tools->Behaviors->Component Search
Or take a look into the behavior file itself: ifly-aircraft-737max8\SimObjects\Airplanes\iFly 737-MAX8\model.178Seat\iFly737Max_INTERIOR_178.xml

Edited by Lorby_SI

LORBY-SI

Thank you so much for this post! It pointed me in the right direction to getting this set up!!! Thank you thank you thank you! The functionality can be easily achieved inside of Spad.next also (my program of choice). In my mind each unique value for a particular Lvar is associate with type of click on a switch. So some switches like the battery, need to be left clicked once to turn on (the cover closed behind it automatically) which is calling the Lvar:VC_Electrical_trigger_Val at a value of 8. Whereas to turn the battery switch off you need to right click pause and right click again to first open the cover then move the switch to off. In this case you call the same Lvar:VC_Electrical_trigger_Val but to a value of 7 then a pause of 100ms followed by the same again and voila! The XML file posted above lists them all. I simply search for what the tooltip is for the switch in the cockpit then a little trial and error for things with the same tooltip might be needed - although they seem to be organised underneath the appropriate animation code, so you can also use that to determine the values to plug into the given Lvar! Hope this helps anyone else just as the above post did for me!!! :D

  • Author

Thank you for quick replay and shots.

Will take a look once I get the chance.

iFly 737 MAX StreamDeck XL & PLUS profile & AAO Scripts for Microsoft Flight Simulator | MSFS

 

A little bit patience ... I will implment hopefully as much variables as possible the next days

Guenter Steiner
--------------------------------------------------------------------------------------

Betatester for: A2A, LORBY, FSR-Pillow Tester
--------------------------------------------------------------------------------------

  • Commercial Member
On 10/15/2024 at 6:05 PM, clarklidbury said:

The functionality can be easily achieved inside of Spad.next also (my program of choice).

Always happy to help out the competition. 

Edited by Lorby_SI

LORBY-SI

  • Commercial Member

Word of caution: these numbers look generated, as if iFly has a database/tool that is creating the behavior file. Let us keep our fingers crossed that the numbers stay the same across future updates of the 737. 

As I wrote above, I wouldn't put too much effort into scripts now, better to wait for the final release.

Edited by Lorby_SI

LORBY-SI

  • Author

I managed to find the L: and Lvars...  

I have an issue when assigning MFD buttons... it is pressed but nothing happens on the plane... only when pressing the mouse it self...

VC_MFD_ENG_SW_VAL Value 10.0

  • Commercial Member
2 hours ago, Raam1234 said:

How do I add the L: please ?

There is nothing to "add". You switch to "MAN" and just type it into the box, as shown in my screenshots. Don't forget the unit, in this case ", Number" and dial in the correct value into the box on the right. 

Edited by Lorby_SI

LORBY-SI

  • Author

I managed to get it all sorted 🙂

Thank you.

Wow, this is really a different implementation...If you just map LVARs, you won't hear the sounds. Wwise sounds are handled via separate LVARs that you can find in the sound.xml file.

Here is an example of a script to press aileron trim left:

0·(>L:VC_AILERON_Trim_SW_VAL,·Number)
1·(>L:WASMVAR_iFly737MAX_AileronTrimSwitch,·Bool)

With the script to release the switch

10·(>L:VC_AILERON_Trim_SW_VAL,·Number)
1·(>L:WASMVAR_iFly737MAX_AileronTrimSwitchRelease,·Bool)

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.