Summary: the /+turbo command will get "stuck" in an psuedo-on state when the turbo disengages for any reason other than executing "/+turbo 0".

There's two main situations where this happens:

After running out of energy:
- Get a ship without infiturbo
- Execute /+turbo
- Wait until energy runs out (can shoot energy weapons to make this happen faster)
- Turbo will disengage when ship runs out of energy
- Execute /+turbo
- Turbo is not engaged

After jumping:
- Execute /+turbo
- Jump (in-system or wormhole doesn't matter)
- When you arrive, turbo will be off*
- However, you will be unable to turbo until you execute "/+turbo 0"
*Rarely turbo will immediately re-engage after the jump

Perhaps relatedly, the logoff timer will be insta-cancelled while in this state.

Workaround: tap and release the turbo key an extra time to "unstick" it.

Replicated 2023-07-04 without any plugins (VO version 1.8.649)
Device: Dell laptop running Windows 10 Home with NVidia GeForce GTX 1050 Ti graphics card.

If you want to toggle turbo, you should instead use the /turbotoggle command (or the /toggleturbo command, I always forget which way the command is oriented).

Luxen, even that command will "stick". It has to do with the turbo disengaging because the energy is too low, but the command is not changing state along with it. Same with jumping.

FYI that this was released last week in 1.8.657:

- The /+turbo command now automatically turns off when turbo is disengaged when typed in.