March 13Mar 13 @Lorby_SI Tis is an exemple of what is coded inside the XML file of the model for the switch of heater number 1: <Component id="VC_Window_Heat_Switch_1_SW_Obj_01" NODE="VC_Window_Heat_Switch_1_SW_Obj_01"> <UseTemplate Name="ASOBO_GT_Anim_Code"> <ANIM_NAME>VC_Window_Heat_Switch_1_SW</ANIM_NAME> <ANIM_LENGTH>10</ANIM_LENGTH> <ANIM_CODE> (L:VC_Window_Heat_1_SW_VAL,number) </ANIM_CODE> <ANIM_LAG>81</ANIM_LAG> </UseTemplate> <UseTemplate Name="ASOBO_GT_MouseRect"> <CURSOR>Hand</CURSOR> <TOOLTIPID>WINDOW HEAT Switches</TOOLTIPID> <MOUSEFLAGS>LeftSingle+RightSingle+WheelUp+WheelDown</MOUSEFLAGS> <CallbackCode> (M:Event) 'LeftSingle' scmp 0 == if{ 81 (>L:VC_Anti_Ice_trigger_VAL,number) } (M:Event) 'RightSingle' scmp 0 == if{ 0 (>L:VC_Anti_Ice_trigger_VAL,number) } (M:Event) 'WheelUp' scmp 0 == if{ 7 (>L:VC_Anti_Ice_trigger_VAL,number) } (M:Event) 'WheelDown' scmp 0 == if{ 8 (>L:VC_Anti_Ice_trigger_VAL,number) } </CallbackCode> </UseTemplate> </Component> Mauro
March 13Mar 13 Commercial Member 19 minutes ago, zetato said: dedicated switch I would use dedicated assignments instead of a toggle (= use two scripts for each value that deterministically turn on or off) Key Down: 7·(>L:VC_Anti_Ice_trigger_VAL,·Number)· Key Up: 8·(>L:VC_Anti_Ice_trigger_VAL,·Number)· (or the other way round, depends on your switch) You can also use the LVars directly (either switching to MAN or by collecting the LVars first and then selecting them from the AAO lists) plus dialling in the value into the numerical box to the right of the event selection. Edited March 13Mar 13 by Lorby_SI LORBY-SI
March 13Mar 13 Commercial Member 19 minutes ago, zetato said: @Lorby_SIThanks for interesting, those are the sequence provided in the script I found, but I tried extracting others variable from the file xml of the model with the same result. (L:VC_Window_Heat_1_SW_VAL,·Number)·0·==·if{·8·(>L:VC_Anti_Ice_trigger_VAL,·Number)·}·els{·7·(>L:VC_Anti_Ice_trigger_VAL,·Number)·} (L:VC_Window_Heat_2_SW_VAL,·Number)·0·==·if{·10·(>L:VC_Anti_Ice_trigger_VAL,·Number)·}·els{·9·(>L:VC_Anti_Ice_trigger_VAL,·Number)·} (L:VC_Window_Heat_3_SW_VAL,·Number)·0·==·if{·12·(>L:VC_Anti_Ice_trigger_VAL,·Number)·}·els{·11·(>L:VC_Anti_Ice_trigger_VAL,·Number)·} (L:VC_Window_Heat_4_SW_VAL,·Number)·0·==·if{·14·(>L:VC_Anti_Ice_trigger_VAL,·Number)·}·els{·13·(>L:VC_Anti_Ice_trigger_VAL,·Number)·} Looks OK to me, except that the toggle is probably not what you need. Fact of the matter is, that using LVars for switches requires some logic to run inside the aircraft to process them. That is prone to errors and potentially unreliable. But - I can't really help you. I can only point at the basics. Only you can find out if you have interfering scripts or if something is wrong with the internals of the sim. Or if your buttons aren't initialized correctly. Btw. you could assign virtual keyboard events to the buttons in AAO - to then control the iFly logic. Not ideal, but it may be a solution. LORBY-SI
March 13Mar 13 41 minutes ago, Lorby_SI said: Looks OK to me, except that the toggle is probably not what you need. Fact of the matter is, that using LVars for switches requires some logic to run inside the aircraft to process them. That is prone to errors and potentially unreliable. But - I can't really help you. I can only point at the basics. Only you can find out if you have interfering scripts or if something is wrong with the internals of the sim. Or if your buttons aren't initialized correctly. Btw. you could assign virtual keyboard events to the buttons in AAO - to then control the iFly logic. Not ideal, but it may be a solution. I tried both the suggestions of you previous post, but nothing changes... I tried also with the virtual keyboard, but I'm struggling... My swithes are conneted to a Leo Bodnar BU0836X card, Lorby recognise it and when I add the button it is correctly shown in the "press button/key" box, but then I click in the "virtual event" box, choose for exemple NumPad3, click close and in the "Press button/key" box the switch number is disappeared replaced by NumPad3, so if I click ADD, only NumPad3 appears in the Assigned Button list and the switch does not work.. At the present only the NumPad4 has worked correctly, binded on my BU0836 Interface Button 12, no luck with NumPad1,2 and 3... So strange... Mauro
March 13Mar 13 Commercial Member 12 minutes ago, zetato said: Bodnar There is an issue with Bodnar boards: AAO cannot read the initial state of the switches. Make sure to turn all of them ON or OFF at the beginning of the flight. LORBY-SI
March 13Mar 13 12 minutes ago, Lorby_SI said: There is an issue with Bodnar boards: AAO cannot read the initial state of the switches. Make sure to turn all of them ON or OFF at the beginning of the flight. Do you mean all the switches binded on the Bodnar Card? Or all the erratic Heaters switches? In the first case I'm not sure i can, I have three Bodnar Cards with more than 60 switches of different types.. The heaters switches are always off at the beginning of the flight, some other probably not... Mauro
March 13Mar 13 Commercial Member 31 minutes ago, zetato said: Do you mean all the switches binded on the Bodnar Card? All of them. Normally, when the first switch is moved, all the others are synchronized with AAO too. That didn't work with the Bodnar boards that we are using in our current simulator build. Could be different Bodnars though. I may be able to improve this in a future version of AAO, but not at the moment. LORBY-SI
March 13Mar 13 14 minutes ago, Lorby_SI said: All of them. Normally, when the first switch is moved, all the others are synchronized with AAO too. That didn't work with the Bodnar boards that we are using in our current simulator build. Could be different Bodnars though. I may be able to improve this in a future version of AAO, but not at the moment. Understood, thank you, I check if I can solve in some way waiting for a future release of Lorby! Mauro
March 13Mar 13 @Lorby_SI Good news! Using your suggestions I found the two wipers knob were setting the relevant switch in close position and they were the only two closed at the loading of the plane in the sim. I removed the binding and now the heaters are working perfectly! Thank you very much once more! Mauro Edited March 13Mar 13 by zetato
Create an account or sign in to comment