Project

General

Profile

Bug #2321

Claw part inverts when used to attach ship to itself

Added by Kasuha about 7 years ago. Updated about 3 years ago.

Status:
Not Fixed
Severity:
Normal
Assignee:
-
Category:
Gameplay
Target version:
-
Start date:
04/02/2014
% Done:

50%

Version:
Platform:
Any
Expansion:
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

When attaching multiple claws to the same object, the second claw to be attached gets inverted. After releasing the object the claw is unusable until it is disarmed and armed again.

In this image, left claw is attached, right one is not yet.

Both claws are attached now. Notice the right claw is inverted, it looks like the object is clawing the claw base.

After releasing the left claw, both connections break. The right claw stays inverted and will not attach to anything until it is disarmed and armed again, after which it returns to normal position.

quicksave.sfs (117 KB) quicksave.sfs [email protected] Kasuha, 02/28/2016 03:07 PM
screenshot15.png (1.87 MB) screenshot15.png [email protected] Kasuha, 02/28/2016 03:08 PM
screenshot0.png (1.05 MB) screenshot0.png Bug is still present in KSP release 1.2 Kasuha, 10/13/2016 05:20 PM
screenshot51.png (3.2 MB) screenshot51.png [email protected] Avera9eJoe, 04/11/2018 09:39 AM
11417
25447
35314

Related issues

Related to Kerbal Space Program - Bug #2378: Graphical glitch with multiple clawsClosed04/10/2014

History

#1 Updated by Kerolyov about 7 years ago

  • Status changed from New to Confirmed
  • Severity changed from Low to Normal
  • % Done changed from 0 to 10
  • Platform Any added
  • Platform deleted (Windows)

I can confirm this, thanks for reporting

#2 Updated by diomedea almost 7 years ago

Issue confirmed even if only one claw is used. In the video linked, a probe with one claw on the back and a docking port presents this, as soon as the docking port is engaged, the claw already connected.

https://www.dropbox.com/s/xrblzka75kclwih/Filmato.mp4

#3 Updated by Kasuha about 5 years ago

11417

The issue is still present in 1.0.5, only the part that the Claw remained turned after disconnecting appears to be fixed.

Could be probably reclassified to "very low" priority as it's just visual problem with no gameplay consequences.

Attaching quicksave for easy reproduction on runway.

Note: types of ships being connected appear to matter. I am getting different results depending on whether I leave both rovers as "probe" or if I change one or the other to "station".

#4 Updated by TriggerAu almost 5 years ago

  • Status changed from Confirmed to Needs Clarification
  • % Done changed from 10 to 0

#5 Updated by sal_vager over 4 years ago

  • Status changed from Needs Clarification to Ready to Test
  • % Done changed from 0 to 80

Should be fixed now in 1.2

#6 Updated by Kasuha over 4 years ago

25447

sal_vager wrote:

Should be fixed now in 1.2

Negative, the bug is still there. I loaded the quicksave I attached in update #3 and when I made sure both claws connect, one became inverted.

Attaching screenshot.

#7 Updated by JPLRepo over 4 years ago

  • Status changed from Ready to Test to Not Fixed
  • % Done changed from 80 to 50

#8 Updated by Avera9eJoe about 3 years ago

35314

To add to this, the joint strength of effected claws becomes extremely springy at times.

#9 Updated by jclovis3 about 3 years ago

I see this as a node tree conflict. Every part needs to traverse a node tree in one direction to reach the root, and circular references are not logically sound so only one connection can be maintained at a time. This seems to be the case when using multiple docking ports to strengthen a connection as well. One will become disconnected when reloading the ship and until such a mechanism is put in place that allows multiple node branches to parallel and reconnect on both ends, this will always be a problem. In the mean time, just think of every construction and docking like this...
1. There is always one root part.
2. The root part has no parent.
3. Every part has exactly one parent.

So look at your double docking problem and ask yourself, what would your node tree look like following this rule set?

Also available in: Atom PDF