Merge Block incorrectly reports itself as Connected when it's touching another merge block.

TheVindicar shared this bug 10 months ago
Considered

Merge block reports itself as connected the moment its hitbox intersects with the other merge block, but it actually takes a push further for the grids to merge properly and for lights to turn green.

Example:


before docking

fcc4d94c0ee15ef120a56d4443b48a4a


Almost docked, notice that merger status (measured via IMyShipMergeBlock.IsConnected property) is reported as connected:

bacb218bf5dc98085b74760616b83a05

Properly docked (by nudging the drone in manually):0d1acbadda7a15a4158e0523f8d0748a

Comments (4)

photo
1

Hello, Engineer!


Thank you for your feedback! Your topic has been added between considered issues.

Please keep voting for the issue as it will help us to identify the most serious bugs.


We really appreciate your patience.


Kind Regards

Keen Software House: QA Department

photo
1

Any update on this issue? Monumentally infuriating trying to script with merge blocks at the moment

photo
1

this is still an issue...