Updated with demonstration ship attached/new instructions. Ready for review! Build: v1.4 3259 Mode: Survival & Creative (All?) Mode: Dedicated Server Reproducibility: Always (but only under very specific circumstances, read on) Severity: Moderate Type: Thrusters/Torque Summary: It's possible for a player/client to lose all Thruster Torque on a CV, while another player can pilot the ship just fine. Description: This bug seems incredibly fiddly, random and hard to replicate. It took hours of work to isolate what factors were involved and how to set up a test case with minimum steps that should lead to 100% reproduction ability. I've been experiencing it for about a year now and nothing would please me more than providing enough information that it can be tracked down and fixed. When this bug occurs, thrusters that were off when a player enters a playfield will not respond for the purposes of turning the ship. Movement still works fine. If a CV had all thrusters off, that player cannot rotate in any direction (pitch/roll/yaw). If all were off except Up and Down, then only Pitch responds, and so forth. HVs and SVs appear to be unaffected. Other players that didn't enter the playfield while Thrusters were off can still pilot the ship normally. The affected player(s) entering the playfield again or rejoining with the Thrusters switched *On* corrects the issue for them, allowing them to turn the ship again. Note that RCS units seem to continue to be responsive and turn the ship normally, even if they were also turned (and even remain) off. I've observed this happening during game play with two of my own CVs, and also the built-in CORE Sparrow, but between my blueprints and the stock ones I could only find a single CV blueprint that both myself and another player could reliably reproduce this bug with in a test environment: My own design, a T2 CV that I designed for deep space exploration and mining back around A12. I named her the Calypso. Some of the hull exterior and the warp drive compartment drew visual inspiration from the beautiful MSS Ambry-CT. The rest of the ship is my own crazy idea. I'm attaching it to the thread now for testing. Although we'll use Creative as the reproduction environment due to how shy this bug is, keep in mind that it isn't limited to Creative mode. I'm positive I've experienced this in Survival games at least 6 times or more. It's gotten to the point I just don't switch Thrusters off any more on CVs. Steps to Reproduce: 1) Start and join a new Creative Coop game/dedicated server. Climate and Empty World don't matter. If you want to skip Step 2, just pick Arid and Empty World = No. 2) If you set Empty World to Yes and have no starter base, -OR- chose White Canvas and do have a Starter Base: Use the Item Menu to fetch any Starter Vessel Block (HV, SV, CV, just not a BA) and place it down anywhere nearby. This step is important to reduce the chaos factor and make sure the CV torque breaks. 3) Spawn the attached capital vessel (Calypso) nearby and use the Panel to deactivate all its Thrusters. 4) Either use god mode (do NOT spawn another vessel for travel) and leave, then return to the CV's playfield, or disconnect and rejoin the server in the same playfield. 5) Reactivate the Thrusters and try to steer the ship. Thrusters will move the ship but not turn it in any direction. At this point, if you leave the Thrusters on and re-enter the playfield again, the ship will resume working as normal. If you turn them back off and re-enter, the bug appears once more. It seems you can also pluck one or more thrusters off the ship (small, medium, doesn't matter) and the bug stops being reproducible. I also tried removing all 8 medium thrusters (4 face forward, 4 back) with 4 large thrusters, and in this case the bug didn't go away and torque remained unresponsive. I tried copying and pasting all the thrusters back into place, replacing them all manually and resaving the blueprint - nothing seems to prevent it from happening again in the repro scenario above. A big thank you to both @Darinth and @Nimmanu for their assistance verifying the reproducibility of this bug in their own games.