So unfortunately went into hospital a few weeks ago, then home then back in so apologies if this has been addressed in the past few weeks.  

I use the VRI 737 overhead and a number of Opencockpits modules including MCP, Dual EFIS, Nav, Com, ATC modules along with the rest of my standard HW.

I use a combination of Spad.next for the overhead and OI4FS for the opencockpit modules.   

Does anyone know if all of this HW is supported and configurable for the iFly?   

Fingers crossed they are all supported!  

Thank you in advance.  (Mods, can you please leave this here instead of moving to HW support, it is more related to HW support for iFly and far more likely to get an answer here....)

 

 

There are SPAD profiles in beta testing right now.  Originally it was thought they’d be available last week so hopefully we’re getting close.

I think if you have a higher version of SPAD (can’t remember the name, complete subscription maybe?) you can access them now.

I have it running to a certain extent via spad.  Though I will admit I look at the programming others have figured out and scratch my head.  Certain planes like PMDG are very logical.  This one is very strange.  

I used to be able to do some basic stuff in FSX/P3D setting up profiles for the Goflight Interface tool but when I tried to look under the hood at SPAD it made my head spin.  Glad there are smarter people out there doing this work 😀

I've been using it for a while.  But yes.  So many people over there are so smart that I still feel like a novice.  The maddog used to be the toughest plane for me to program.  But the iFly got that beat

It looks like some profiles are released if I understand what's said on discord properly.  Nothing for my GoFlight MCP PRO as far as I can figure out.

On 11/5/2024 at 11:02 AM, micstatic said:

I have it running to a certain extent via spad.  Though I will admit I look at the programming others have figured out and scratch my head.  Certain planes like PMDG are very logical.  This one is very strange.  

They way they use LVARS is a little different than other developers but once you get the hang of it programming hardware in SPAD is pretty easy.

Let's say for instance you are trying to assign a switch in SPAD to the left landing light, if you use something like notepad ++ search for "Landing Light" in the ifly737Max_Interior_178.xml file and look for the following block of text

What threw me at first is the first LVAR (VC_Landing_Light_1_SW_Obj) you would think that is what you need for SPAD ..... Wrong

 <Component  id="VC_Landing_Light_1_SW_Obj"  NODE="VC_Landing_Light_1_SW_Obj">
    <UseTemplate Name="ASOBO_GT_Anim_Code">
        <ANIM_NAME>VC_Landing_Light_1_SW</ANIM_NAME>
        <ANIM_LENGTH>20</ANIM_LENGTH>
        <ANIM_CODE>
        (L:VC_Landing_Light_1_SW_VAL,number)
        </ANIM_CODE>
          <ANIM_LAG>81</ANIM_LAG>
    </UseTemplate>
    
    <UseTemplate Name="ASOBO_GT_MouseRect">
      <TOOLTIPID>LANDING Light Switch</TOOLTIPID>
      <MOUSEFLAGS>LeftSingle+WheelUp+WheelDown</MOUSEFLAGS>
        <UPARROW>UpArrow</UPARROW>
       <DOWNARROW>DownArrow</DOWNARROW>
      <CallbackCode>
        (M:Event) 'LeftSingle' scmp 0 == if{
         (M:RelativeY) 0 &gt;
                            if{ 18 (>L:VC_Miscellaneous_trigger_VAL,number) }
                            els{ 19 (>L:VC_Miscellaneous_trigger_VAL,number) }
     }

 

If you scroll down further you will see the following:

 (M:Event) 'WheelUp' scmp 0 == if{
        18 (>L:VC_Miscellaneous_trigger_VAL,number)
        }
        (M:Event) 'WheelDown' scmp 0 == if{
        19 (>L:VC_Miscellaneous_trigger_VAL,number)
        }

The LVAR you need to search for in SPAD to turn on the left landing light is:

VC_Miscellaneous_trigger_VAL (Add this as an action)

Now you need to have the "Operation" box to "Set"

and the "Static Value" set to 19 

This simulates a mouse wheel scroll down event on the left landing light switch, if your aircraft has 2 positions for the landing light just enter a pause of around 800 ms then add the exact same action again and Voila 

If you want to turn off the landing light then you use the exact same LVAR 

VC_Miscellaneous_trigger_VAL

But this time use the number 18 in the set value field.

 

Landing light 2 uses the exact same LVAR but different event numbers

M:Event) 'WheelUp' scmp 0 == if{
        20 (>L:VC_Miscellaneous_trigger_VAL,number)
        }
        (M:Event) 'WheelDown' scmp 0 == if{
        21 (>L:VC_Miscellaneous_trigger_VAL,number)

 

Hope the helps

 

Edited November 6, 20241 yr by RJC68