I’m working on an MSFS 2024 in-sim panel pushback helper. It uses a JavaScript toolbar panel for route logic and a WASM helper to send commands to the native pushback tug.
The tug connects and starts pushing correctly, but then it visibly detaches before the route is complete. After that, the aircraft continues to behave like the tug is attached and finishes its route.
The confusing part is that the sim still appears to report the tug as attached, even after it is visibly detached. So the attach-state I’m reading may be stale, incomplete, or not the right variable for the actual physical/visual tug connection.
My control flow is basically:
- Plan and lock a pushback route in JavaScript.
- Attach/connect the native tug through the WASM helper.
- Run a JavaScript route loop that calculates speed and steering.
- Send separate commands to WASM:
motionDirection: forward / backward / none
steeringDirection: left / right / none - WASM applies those commands to the sim/tug.
I’m not teleporting or directly moving the aircraft. I’m trying to keep the native tug attached and continuously command it along the route.
What I’m trying to figure out is why the tug visually detaches while the sim still reports it as attached, and whether there is a better variable/event that represents the tug’s real attached/physical state.