Fuel Valve command only working every second time
-
Hello,
I'm using SPAD.neXt and the SET_FUEL_VALVE_ENGx commands:
This works fine for engine 1, but I have to trigger the same command twice for the other three engines. In other words, they only work every second time.
This is the same profile, as I use it for 146, where it worked fine.Also, NAV_LIGHTS_ON and NAV_LIGHTS_OFF seems to be inverted, again this used to work fine in the 146.
-
I'm not an FSUIPC/SPAD user myself, but I believe the control assignments and Lvars used for the fuel valves are the same between the 146 and RJ. Certainly, there shouldn't be any difference in logic between engine 1 and engines 2-4. I will double-check with our development team though and get back to you.
The NAV LIGHTS ON / NAV LIGHTS OFF control assignments do appear to be reversed, so I have logged that on our internal bug tracker for the next update. Thanks for reporting that!
Mark - Just Flight
-
Thanks Mark. I just did a few more tests. Indeed, only engine 1 is behaving as expected and engines 2-4 require two commands to trigger. So there must be a difference here. I observed this behavior in the -85 and in the -100 (haven't tried the -70 yet).
The commands still work as expected in the latest version of the 146, so there must be a difference here as well. -
I ran into the same problem in the RJ and ended up changing the command to using LVARS
Ignore the condition on the Button Pressed that just prevents me from turning the engine off without holding down a button on a different controller, while the condition on the Button Released just makes sure nothing weird happens if I accidentally trigger Button Released when the engine isn't off.
I don't think the Latch commands are required either I just added them to make it look right ;) -
Having spoken to our development team, there is extra code in the RJ's fuel valves compared to the 146 (required due to the extra FADEC simulation in the RJ), however, the LVars and triggers themselves are exactly the same between the two aircraft, and there are no differences we can see between each of the engines (other than the engine numbers).
@falcon71 Could you try the suggestions @Matchstick kindly listed above and see if that resolves the issues you are experiencing?
Mark - Just Flight
