Reported Version: v0.1.5 (latest) | Mods: See description for full list | Can replicate without mods? Yes
OS: Manjaro Linux + Steam Proton | CPU: AMD Ryzen 7 5800X | GPU: AMD Radeon RX 6700 XT | RAM: 32 GB
Spicat Edit: This bug work with no mods and on windows (see below)
Initial bug report (hidden for visibility)
Craft file:
Test.json
Video evidence (from Spicat with the craft file provided):
Spicat Edit:
Steps to reproduce:
In the vab, put a pod
Attach a launch clamp to it (optional but it's to see the bug better)
Attach a hub on top
Next to the craft (in a different subassembly), put a tank and attach a decoupler
Take the tank and attach it to the hub so that the decoupler is the part separating the hub and the tank - Important
Copy the decoupler (thus, with the tank)
Attach the copied part to another hub connection
Launch and decouple
Result: When the copied part is decoupled, he thinks that it's still part of the craft, so the camera follow and the part still reacts to the input.
Video evidence (with all the steps):
2023-11-01 00-05-18.mp4
Steps to reproduce (Docking port version):
In the vab, put a pod
Attach a clamp to it (it's not mandatory like above)
Attach a docking port to the pod (or any other part, a truss in the video below)
Attach an engine to that docking port (to detach it)
Copy the docking port (with the engine on it) and attach it next to other one
Go to the launchpad
Undock the docking port (the one that was copied)
Video evidence:
Additional Information:
The version with the docking port also work if you attach another docking port instead of an engine but it triggers another bug (You can see what does the version with only docking port in it):
