To clarify:
The Strobe Light simvars (specifically LIGHT STROBE:1, LIGHT STROBE:2, and LIGHT STROBE:3) are what actually control our ballast valve system. These aren’t just alternative inputs — they are the core variables driving our ballast logic. The reason for this is multiplayer compatibility and custom control. MSFS doesn’t provide custom L:Vars or events that are shared across the network, so like many third-party developers, we use a workaround by leveraging light-related simvars. These variables are synced in multiplayer, which lets us simulate real-time drainage per valve using our own custom logic. This approach allows each ballast valve to drain at realistic, independent rates instead of all dumping at once. By tying the system to the strobe light indexes, we can fine-tune each valve’s behavior — and more importantly, you can actually see your friend dumping water during a multiplayer flight, just like in real life.
The problem, as you noted, is that users can’t directly bind to individual strobe indexes (e.g., no default control binding exists for “Toggle Strobe Light #2”). To make ballast control user-friendly, we had to intercept other sim events:
We chose “SET VOR 1/2/3” to control individual ballast valves (mapped to each strobe light).
We also intercepted “TOGGLE WATER BALLAST VALVE” to trigger all three valves at once for users who prefer a simple “open all” option.
As a side note, “TOGGLE STROBE LIGHTS” also affects all three since MSFS toggles every strobe index simultaneously by default — which is why it’s listed in our docs as an “alternative keybind,” even though it’s technically the underlying system.
So calling it an “alternative” is more of a simplification for users. Behind the scenes, the strobe lights are the ballast control system.
As for your Alpha unit — it sounds like Honeycomb has internally mapped the strobe switch to LIGHT STROBE:0, even if no binding shows up in the MSFS control settings. This is likely a firmware-level hardware mapping, not something configured by us or Asobo. Because of that, assigning a separate action like “TOGGLE WATER BALLAST VALVE” to another switch can cause conflicts, even if nothing looks wrong in the UI.
In short:
If your Alpha’s strobe switch is already toggling the ballast system, you don’t need to bind anything else. Avoid assigning VOR controls or the water ballast toggle — doing so will likely cause overlapping inputs.
It sounds like you’re seeing a conflict between the Alpha’s built-in strobe switch and your manual binding to the ballast toggle simvar. Since both are trying to control the same system, they’re likely interfering with each other.
Honestly, I’m a bit surprised to see this behavior on the Alpha, as most of the hardcoded mappings we’ve run into have been with devices like the Logitech Switch Panel.
If the Alpha’s behavior can’t be changed through the MSFS settings alone, your best option may be to use third-party software like FSUIPC or SPAD.neXt to remap or intercept the switch logic.
Let us know if the issue persists after cleaning up the bindings — happy to help dig further if needed.





