With the new release a fresh new set of questions.

How would you handle the fuel flow switches?  They for me they move to whatever state they are not in when the button I press is activated.  In other words the same event ID puts them in ON or OFF mode.  If ON then OFF, if OFF then ON.  I would like to assign them to my HC rocker switches with something like the rocker up is up and the rocker down is down.  Any ideas? 

Also, I can't seem to get the landing lights and nose taxi/landing lights to work.  Typicall I would assign the nose taxi position to my HC Alpha taxi light switch in the down position and that would also put the L/R landing lights in the extended position.  Then when I hit the landing light button, it would put the nose taxi into takeoff and put the L/R into the complete down. Reversing this procedure with using the On Release to reverse this. I know I will need to script this, but can't even get them to come on one at a time.  

4 hours ago, Crabby said:

Any ideas? 

This has been covered above. When dealing with toggle events, you have to find a variable that contains the actual state of the switch. Then make two scripts, one for ON the other for OFF, where you query the variable and only call the event when necessary (=in the OFF script, only call the event when the variable shows the ON state)

 

Edited January 15Jan 15 by Lorby_SI

4 hours ago, Crabby said:

I know I will need to script this, but can't even get them to come on one at a time.  

Here are some scripts. They operate all three switches at the same time (L - R - TAXI), so you can extract from them whatever snippet you need.

LDG + Taxi UP

0·(>K:#90257)·0·(>K:#90257)·
0·(>K:#90259)·0·(>K:#90259)·
0·(>K:#90261)·0·(>K:#90261)·

LDG + Taxi MID

(L:MD11_OVHD_LTS_LDG_L_SW,·Number)·0·==·if{·0·(>K:#90258)·}·
(L:MD11_OVHD_LTS_LDG_L_SW,·Number)·2·==·if{·0·(>K:#90257)·}·
(L:MD11_OVHD_LTS_LDG_R_SW,·Number)·0·==·if{·0·(>K:#90260)·}·
(L:MD11_OVHD_LTS_LDG_R_SW,·Number)·2·==·if{·0·(>K:#90259)·}
(L:MD11_OVHD_LTS_NOSE_SW,·Number)·0·==·if{·0·(>K:#90262)·}·
(L:MD11_OVHD_LTS_NOSE_SW,·Number)·2·==·if{·0·(>K:#90261)·}

LDG + Taxi DOWN

0·(>K:#90258)·0·(>K:#90258)·
0·(>K:#90260)·0·(>K:#90260)·
0·(>K:#90262)·0·(>K:#90262)·

 

5 hours ago, Crabby said:

How would you handle the fuel flow switches? 

Again a few scripts. These also move all three switches. Curiously enough, TFDi's own custom events don't seem to work, I have to use their custom "CEVENT" LVar. Which means that I have to leave a bit of time between actuations, so the aircraft logic can process the value first, before I send the next one (hence the SPLIT in the script)

Fuel ON with a 1 second delay

(L:MD11_THR_L_FUEL_SW,·Number)·0·==·if{·77834·(>L:CEVENT,·Number)·}·(SPLIT:1000)·
(L:MD11_THR_C_FUEL_SW,·Number)·0·==·if{·77835·(>L:CEVENT,·Number)·}·(SPLIT:1000)·
(L:MD11_THR_R_FUEL_SW,·Number)·0·==·if{·77836·(>L:CEVENT,·Number)·}

Fuel OFF with a 1 second delay

(L:MD11_THR_L_FUEL_SW,·Number)·1·==·if{·77834·(>L:CEVENT,·Number)·}·(SPLIT:1000)·
(L:MD11_THR_C_FUEL_SW,·Number)·1·==·if{·77835·(>L:CEVENT,·Number)·}·(SPLIT:1000)·
(L:MD11_THR_R_FUEL_SW,·Number)·1·==·if{·77836·(>L:CEVENT,·Number)·}

 

Edited January 15Jan 15 by Lorby_SI

Much appreciated info!

Really wish someone would publish some scripts foe this jet at fs.to. They are mostly available for most if not all of the payware tube liners now - maybe someday...