Linas Martusevicius
Linas Martusevicius
Fells more like a hack than a solution. Would it not make more sense for this to be part of the "suite"? That way the developer can control the gaps...
The Start/Stop button performs multiple actions in the plane, almost like a macro. Opening/closing the fuel valves is one of them - just need to figure out which other actions...
Nice! Edit: looks like the button state changes, but the engine doesn't start - guessing there's a third step.
In my case I'm trying on the Longitude - startup stops at 22% N2 and stays there, unless I turn that button to start via mouse. I'm going to download...
Looks like in the longitude, when I change engine 2 to `RUN` these events fire... - MIXTURE2_RICH - TOGGLE_FUEL_VALVE_ENG2 - TURBINE_IGNITION_SWITCH_SET2:1 The starter is just TOGGLE_STARTER2 The same for the...
Hmm.. side note here, but wonder why the turbine igintion switch event is coming from a different domain - `MSFS` in stead of `SIMCONNECT`...
It's weird - `TURBINE_IGNITION_SWITCH_TOGGLE` works, but not `TURBINE_IGNITION_SWITCH_SET` and not `TURBINE_IGNITION_SWITCH_SET1` or `TURBINE_IGNITION_SWITCH_SET2`. My guess is the `MSFS:` events are faked by the plane and not part of simconnect. Only...
Oh if only MS followed conventions! The event sniffer in the screenshot above shows the event names and parameters that were fired by the sim when clicking cockpit buttons.
Guess the CJ4 doesn't need `TURBINE_IGNITION_SWITCH_TOGGLE`. Longitude is the same a CJ4 except it needs that one as well. Mixture and fuel valve only allow it spool it up to...
Just out of curiosity (I'm a C# dev by profession myself), how does interop via lvars differ from standard simconnect? Maybe I could help out somehow.