15 hours ago, geoffda said:

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)

As I understand it - this is the wrong LVAR to trigger this switch. You are adjusting the object animation only this way. As I understand it to adjust the aileron trim you need to trigger L:VC_Flight_Control_trigger_VAL to either a value of 28 or 27. Im not sure which value does left specifically but 28 corresponds to scrolling your mouse wheel UP whilst over the switch and 27 to scrolling it down. Hope this helps 🙂 PS when you use the LVAR in this way, you will both see the animation and hear the sound. BUT you may need to script multiple events to deal with things like switches with guards over the top 🙂

On 10/16/2024 at 1:32 AM, Lorby_SI said:

Always happy to help out the competition. 

😆For the record I think Axis and Ohs is an exceptional product which I also own 😁

8 hours ago, clarklidbury said:

As I understand it - this is the wrong LVAR to trigger this switch. You are adjusting the object animation only this way. As I understand it to adjust the aileron trim you need to trigger L:VC_Flight_Control_trigger_VAL to either a value of 28 or 27. Im not sure which value does left specifically but 28 corresponds to scrolling your mouse wheel UP whilst over the switch and 27 to scrolling it down. Hope this helps 🙂 PS when you use the LVAR in this way, you will both see the animation and hear the sound. BUT you may need to script multiple events to deal with things like switches with guards over the top 🙂

You are absolutely right! Looking at the XML, they are using different LVARs for animation versus input.  Thanks for calling that out.

Edited October 17, 20241 yr by geoffda

Hi,

I'm trying to edit the script of Position Lights, I need only 2 postions

 

1. Strobe and Steady

2. Steady

I don't need OFF postion - i'm using Honeycomb Alpha and wants too set OFF postion on NAV button. Can you please help me with it?

 

0·1·2·0·(L:POSL1)·(L:iFly_PosL)·
4·iseq·(>L:POSL1)·(>L:iFly_PosL)

(L:iFly_PosL)·0·==
if{·31·(>L:VC_Miscellaneous_trigger_VAL,·Number)·}

(L:iFly_PosL)·1·==
·if{·30·(>L:VC_Miscellaneous_trigger_VAL,·Number)·}

(L:iFly_PosL)·2·==
·if{·30·(>L:VC_Miscellaneous_trigger_VAL,·Number)·}

(L:iFly_PosL)·3·==
·if{·31·(>L:VC_Miscellaneous_trigger_VAL,·Number)·}

 

I dont know which position of it should I delete, I tried many combination and no idea...

On 10/21/2024 at 7:37 AM, miiloisme said:

Hi,

I'm trying to edit the script of Position Lights, I need only 2 postions

 

1. Strobe and Steady

2. Steady

I don't need OFF postion - i'm using Honeycomb Alpha and wants too set OFF postion on NAV button. Can you please help me with it?

 

0·1·2·0·(L:POSL1)·(L:iFly_PosL)·
4·iseq·(>L:POSL1)·(>L:iFly_PosL)

(L:iFly_PosL)·0·==
if{·31·(>L:VC_Miscellaneous_trigger_VAL,·Number)·}

(L:iFly_PosL)·1·==
·if{·30·(>L:VC_Miscellaneous_trigger_VAL,·Number)·}

(L:iFly_PosL)·2·==
·if{·30·(>L:VC_Miscellaneous_trigger_VAL,·Number)·}

(L:iFly_PosL)·3·==
·if{·31·(>L:VC_Miscellaneous_trigger_VAL,·Number)·}

 

I dont know which position of it should I delete, I tried many combination and no idea...

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 to 30 then set a small delay then send LVAR VC_Miscellaneous_trigger_VAL to 30 again. Think of this as clicking the switch up twice. You need this in case the switch is in the steady position you need to move it to the OFF then to the STROBE position.

To set the position lights to steady I would send the LVAR VC_Miscellaneous_trigger_VAL to 31 then set a small delay then send LVAR VC_Miscellaneous_trigger_VAL to 31 again. Think of this as clicking the switch down twice. You need this in case the switch is in the strobe position you need to move it to the OFF then to the steady position.

 

hey @guenseli, thanks for your excellent AAO profile.. I have made some additions to it - mainly added many ON/OFF options.. this is because I use honeycomb alpha and bravo, which have a lot of ON/OFF buttons and less of TOGGLE switches.. So now you can flip the landing light switch on/off and it will operate both the Left & Right switches together with a single flip.. just like you had done for the PMDG 737.. so all lights are on/off and can still be mapped as toggle for those who prefer that.. I have also mapped the autobrake to the rotary switch on the yoke.. 

I think the wider community will benefit from this based on comments i've seen on flightsim.to where people kept asking for ON/OFF options.. can i email you my script and template files, so that you can upload an update to your AAO profile on flightsim.to? 

I w'd prefer if you upload this instead of me uploading a new profile since you have a wider reach in the community.. 

thx, sent you a PM

I have a question, when I want to use the flaps_axis that I use for example the pmdg 737 with this plane I cannot select flaps 0, the lowest is flaps 1. What should I do? I have set the complete axis range from -16384 to +16384 still the airplane won’t set flaps 0 when it’s complete up on my honeycomb bravo.

also I cannot use axis_brake_right and left correctly, I’m unable to for example deactivate the parking brake with pressing both. 

23 minutes ago, Bam2000 said:

I have a question, when I want to use the flaps_axis that I use for example the pmdg 737 with this plane I cannot select flaps 0, the lowest is flaps 1. What should I do? I have set the complete axis range from -16384 to +16384 still the airplane won’t set flaps 0 when it’s complete up on my honeycomb bravo

The iFly doesn't use the default SDK events, that's why. They made their own logic.

The flaps in particular require a complex setup with two assignments. One covers the "0" position using the HANDLING_Flaps IE:, the other the normal axis travel with AXIS_FLAPS_SET. Hard to explain. I made a template for the flaps a while back:

https://www.dropbox.com/scl/fi/tz0gga583mxtjq9pzc170/iFlyFlaps.zip?rlkey=27ex4dfmvxwa9sxlxlk345t8l&dl=0

There may be other solutions using the IE directly or its BVar counterpart, but this is what I have in my config.

Quote

also I cannot use axis_brake_right and left correctly, I’m unable to for example deactivate the parking brake with pressing both. 

Sorry, never looked into the brakes for this plane. I didn't know that you even could release the parking brake that way - I wouldn't expect this to work on any aircraft to be honest. The functionality could be constructed in AAO using scripts I guess.

AAO and the MSFS controller assignments are not related. Don't expect things to work the same in AAO than it does in MSFS assignments. AAO can only access the sim through the SDK - some items may have similar names, but they are not the same.

Edited February 22, 20251 yr by Lorby_SI

4 hours ago, Lorby_SI said:

The iFly doesn't use the default SDK events, that's why. They made their own logic.

The flaps in particular require a complex setup with two assignments. One covers the "0" position using the HANDLING_Flaps IE:, the other the normal axis travel with AXIS_FLAPS_SET. Hard to explain. I made a template for the flaps a while back:

https://www.dropbox.com/scl/fi/tz0gga583mxtjq9pzc170/iFlyFlaps.zip?rlkey=27ex4dfmvxwa9sxlxlk345t8l&dl=0

There may be other solutions using the IE directly or its BVar counterpart, but this is what I have in my config.

Sorry, never looked into the brakes for this plane. I didn't know that you even could release the parking brake that way - I wouldn't expect this to work on any aircraft to be honest. The functionality could be constructed in AAO using scripts I guess.

AAO and the MSFS controller assignments are not related. Don't expect things to work the same in AAO than it does in MSFS assignments. AAO can only access the sim through the SDK - some items may have similar names, but they are not the same.

Thanks for the File, will look into it later this day 🙂

For the Parking Brake that is the same principel like with the PMDG 737 set to Realistic Parking Brake behavour, and there it works with pressing down both Brakes will release the Parking Brake, in the iFly i cannot get it to work. Maybe i need to set it to non realisitc behavour (its in the EFB as an Option) for the iFly. 

1 hour ago, Bam2000 said:

Thanks for the File, will look into it later this day 🙂

For the Parking Brake that is the same principel like with the PMDG 737 set to Realistic Parking Brake behavour, and there it works with pressing down both Brakes will release the Parking Brake, in the iFly i cannot get it to work. Maybe i need to set it to non realisitc behavour (its in the EFB as an Option) for the iFly. 

Personally, I don't think that this won't work at all. It might be a PMDG specialty. I would use scripts to do this.

 

Any idea or tips for the Speedbrake ? This one is also behaving not like other Airplanes 😞

33 minutes ago, Bam2000 said:

Any idea or tips for the Speedbrake ? This one is also behaving not like other Airplanes 😞

On the Add Axis dialog:

Option 1:
- Open the Add Axis dialog
- Click on the box next to "Enter simulator Event"
- Go to "MSFS IEs->HANDLING_Spoilers", doubleclick that
- Set Axis Min = 0 , Axis Max = 1, Rounding: Float
- Move the desired Lever
- Save

Option 2:

- Click on the LED next to "Enter Variable"
- Type "B:HANDLING_Spoilers_Set" into the box
- Set Axis Min = 0 , Axis Max = 16383, Rounding: Int
- Move the desired Lever
- Save

 

Edited February 26, 20251 yr by Lorby_SI

Does anyone know if there is a variable for the flight altitude and landing altitude in the pressurization panel of the aircraft ? 

@Bam2000 I couldn't find the variable for flight altitude and landing altitude I am afraid. My solution to get this to display on my overhead panel was to note that what the default value iFly sets this to on aircraft load ( I think it's 32000 for flt alt and 0 for landing alt) and made my own local variable that initialises to that value. Then when I move the knob, I both send the command to the sim and also update my own local variable... It can loose sync if you're not careful...