Solution to assign a button to preoiler
-
It should be as simple as setting L:var_PreoilerSwitch. 0=Left, 1=Off, and 2=Right.
-
It should be as simple as setting L:var_PreoilerSwitch. 0=Left, 1=Off, and 2=Right.
@Black-Square L:var_PreoilerSwitch does not exist, I searched for all Lvar variants and I can't find a solution.
-
It should be as simple as setting L:var_PreoilerSwitch. 0=Left, 1=Off, and 2=Right.
@Black-Square It's solved now. Thanks for responding and helping.
-
It should be as simple as setting L:var_PreoilerSwitch. 0=Left, 1=Off, and 2=Right.
@Black-Square said in Solution to assign a button to preoiler:
It should be as simple as setting L:var_PreoilerSwitch. 0=Left, 1=Off, and 2=Right.
Can you elaborate on exactly how to do this ?
-
I'm not an avid cockpit builder, so hopefully someone else will chime in, but there are many applications that exist for control bindings, and this should be one of their most prominent features. Virtually all cockpit building involves setting simple L:Vars, so there should be many tutorials on the subject.
-
@Black-Square said in Solution to assign a button to preoiler:
It should be as simple as setting L:var_PreoilerSwitch. 0=Left, 1=Off, and 2=Right.
Can you elaborate on exactly how to do this ?
@jfri said in Solution to assign a button to preoiler:
@Black-Square said in Solution to assign a button to preoiler:
It should be as simple as setting L:var_PreoilerSwitch. 0=Left, 1=Off, and 2=Right.
Can you elaborate on exactly how to do this ?
I suppose I should use FSUIPC. I have done similar things with the Milviz 310 and got things working. Tried doing the same with the Duke failed.
Do you know is should be
L:Duke_PreoilerSwitch (in 310 it was L:C310_) or is it var_ ?
Also I would like to the the same with the two Fuel boost pumps. I find no entry called left right fuel boost pump and no L: variable name. -
The prefix should be "var_". There is no universally adopted naming convention, so each developer names the variables as they see fit. There are several ways to toggle the fuel pumps. Any of the following should work:
>A:CIRCUIT SWITCH ON:58, bool)(58 for left, 59 for right)
>K:TOGGLE_ELECT_FUEL_PUMP1
>K:ELECT_FUEL_PUMP1_SET
>B:FUEL_Pump_1_ToggleYou can find many more examples of the exact code in this database. Let me know if you have any more questions, though!
-
The prefix should be "var_". There is no universally adopted naming convention, so each developer names the variables as they see fit. There are several ways to toggle the fuel pumps. Any of the following should work:
>A:CIRCUIT SWITCH ON:58, bool)(58 for left, 59 for right)
>K:TOGGLE_ELECT_FUEL_PUMP1
>K:ELECT_FUEL_PUMP1_SET
>B:FUEL_Pump_1_ToggleYou can find many more examples of the exact code in this database. Let me know if you have any more questions, though!
@Black-Square said in Solution to assign a button to preoiler:
The prefix should be "var_". There is no universally adopted naming convention, so each developer names the variables as they see fit. There are several ways to toggle the fuel pumps. Any of the following should work:
>A:CIRCUIT SWITCH ON:58, bool)(58 for left, 59 for right)
>K:TOGGLE_ELECT_FUEL_PUMP1
>K:ELECT_FUEL_PUMP1_SET
>B:FUEL_Pump_1_ToggleYou can find many more examples of the exact code in this database. Let me know if you have any more questions, though!
I try to use a macro file and then offset byte set in FSUIPC. No success so far. But I found out that I under WASM menu could set a Lvar. There I found
var_PreoilerSwitch 0491
and from there I could control the switch
What is 0491 there ?
I am familiar with L: but what is K: and B: ? -
Again, I'm not an expert, and I might be wrong about this, but I think you are approaching this in an overly difficult way. That's not a criticism (I seem to approach everything in my life from a difficult angle too), but there are numerous applications that should allow for very easy L:Var manipulation. I'm sure FSUIPC can do it too, but I'm not sure that it requires register manipulation.
The B:Var is the new MSFS interaction system, which can be very useful, but it's also incredible abstract and convoluted for developers to set up, so it tends to be underutilized. Not all 3rd part applications have access to B:Vars, so I would try to avoid them wherever possible.
