Little help on hardware assignments- boots, AP trim, FD switch, alt selector
-
Hey,
using FSUIPC, I set L:var_SurfaceDeiceSwitch to "2" for automatic cyle with a spring loaded switch. The switch in the panel is not moving, but I can see the boots pressure rising. Ok, better than nothing, even though I'd prefer the switch moving as well.
Now.. if I set FSUIPC to set the var back to "1" upon release, the cycle immediately stops upon release. If I set it to do nothing upon release, the cycle never ends (boots stay inflated).For the flight director, I set K:TOGGLE_FLIGHT_DIRECTOR as in the manual, but the FD won't turn on/ off as expected. Only the Ap modes flicker off and on again, but the FD itself won't turn off/on.
For the alt selector I set K:AP_ALT_VAR_INC / DEC, which turn the 100's. But when I toggle the L:var_AltitudeSelectorKnobPushed variable, the pushbutton toggles as expected, but still the 100s are turned, not the 1000s.
Regarding AP trim, I already follow the other thread.
-
I see the issue with the airframe deicing switch. That's something easy I will fix in the first update. In the meantime, if you also set L:var_airframeDeiceMode along with L:var_SurfaceDeiceSwitch, the switch will move with your setting. As for the actuation of the boots that you're describing, I will have to open the simulator to take a look at that. I'll get back to you shortly.
That's old information on the flight director, sorry. You should use (L:var_FlightDirectorVisible, bool).
I don't have any automation for the altitude selector, so you will need to detect the state of (L:var_AltitudeSelectorKnobPushed, bool) in your script. You can send the amount you want to increment the altitude by to the K:AP_ALT_VAR_INC / DEC command. For example...
(L:var_AltitudeSelectorKnobPushed, bool) if{ 100 (>K:AP_ALT_VAR_INC) } els{ 1000 (>K:AP_ALT_VAR_INC) }