Bug #10045: Clamp-O-Tron Fails to Function - Kerbal Space Program - Squad Bugtracker

Bug #10045

Clamp-O-Tron Fails to Function

Added by zwieg88 over 8 years ago. Updated about 8 years ago.

Status:

Closed

Severity:

Normal

Assignee:

Claw

Category:

Gameplay

Target version:

1.2.0

Start date:

06/25/2016

% Done:

100%

Version:

1.1.3

Platform:

Windows

Expansion:

Language:

English (US)

Mod Related:

Votes:

Description

Description:

To simply put it: the Clamp-O-Tron is NOT working whenever the 'Undock' button is pressed. And if the button is pressed it outright disappears.

Link to pictures illustrating the issue:

http://imgur.com/a/ZPGo1

The problem occurred after I had successfully docked with the lander can after achieving LKO, which wasn't an issue at all. After travelling to the Mun and getting ready to separate the lander module from the main ship the clamp-o-tron simply failed to work. No amount of reloading or different testings helped to solve the problem.

Since then I have terminated flight, however the issue is persistent with every new ship I put into orbit that resembles the same one the issue started with (so far I haven't tested different assemblies, though I doubt it'll make much difference). The craft file is added as an attachment to this report as well as the save file with the persistent problem and the system information info sheet (DxDiag.txt).

Through the forums I have confirmed I am not the only with one experiencing this issue as well as the issue being repeated with the Clamp-O-Tron Sr, so that rules out this being an isolated incident.

My version is 1.1.3 updated through the Steam client from 1.1.2, NO MODS APPLIED.

I hope that through the information provided in this report a solution to this problem may be found.

Thanks in advance!

Unmodded Sandbox CLAMP ISSUE.sfs (442 KB) Unmodded Sandbox CLAMP ISSUE.sfs	Main Save File	zwieg88, 06/25/2016 05:09 AM
quicksave.sfs (442 KB) quicksave.sfs	[email protected]	zwieg88, 06/25/2016 05:10 AM
persistent.sfs (442 KB) persistent.sfs	[email protected]	zwieg88, 06/25/2016 05:10 AM
Apollo K 03.craft (391 KB) Apollo K 03.craft	Craft File	zwieg88, 06/25/2016 05:10 AM
output_log.txt (632 KB) output_log.txt	[email protected]	zwieg88, 06/25/2016 05:11 AM
settings.cfg (26.3 KB) settings.cfg	[email protected]	zwieg88, 06/25/2016 05:11 AM
KSP.log (292 KB) KSP.log	[email protected]	zwieg88, 06/25/2016 05:12 AM
DxDiag.txt (79.3 KB) DxDiag.txt	System Information	zwieg88, 06/25/2016 05:17 AM
Quick Save Before Undocking issue.sfs (2.88 MB) Quick Save Before Undocking issue.sfs	[email protected]	Anth12, 06/26/2016 02:12 AM
Quicksave after undocking problem starts.sfs (3.16 MB) Quicksave after undocking problem starts.sfs	[email protected]	Anth12, 06/26/2016 02:15 AM
BUG.sfs (2.92 MB) BUG.sfs	Quicksave of my Career in it's bugged state.	Trekkerjoe, 06/30/2016 09:45 PM
Undocking Glitch.craft (40.2 KB) Undocking Glitch.craft	The rover I used to test my fairing theory.	Trekkerjoe, 06/30/2016 10:00 PM
quicksave.sfs (312 KB) quicksave.sfs	A save of my bugtesting world containing the six craft stuck together.	Trekkerjoe, 06/30/2016 10:02 PM

Related issues

History

#1 Updated by Anth12 over 8 years ago

File Quick Save Before Undocking issue.sfs Quick Save Before Undocking issue.sfs added
File Quicksave after undocking problem starts.sfs Quicksave after undocking problem starts.sfs added

I had the same problem yesterday with my space station. But i had just tried out hyperedit and mechjeb and kerbal alarm for the first time and assumed it was related to that.

At the time I also had a big drop in frame rate...the game became nonresponsive for moments at a time...to the point I used Alt F4 to end KSP. (Windows 10)

Again note my save had mods at the time the problem started.

With no mods I found the following results for the quick saves I supplied

If docking port A has undock as an option and docking port B doesnt...they wont undock when undock is pressed and the undock option disappears forever

If docking port A had decouple as an option and docking port B has decouple as well as an option they will undock

Also my station only has the following docking ports: junior, standard and senior.

#2 Updated by Int_10h over 8 years ago

Status changed from New to Confirmed
% Done changed from 0 to 10

I fixed this bug in my saved game, immediately after using the "Undock" button, exiting the game, editing by hand the persistent.sfs file, reconnecting both dockUId's and changing their state to "Docked (docker)".

I hope this can be useful to someone.

#3 Updated by sal_vager over 8 years ago

Status changed from Confirmed to Need More Info
% Done changed from 10 to 0

Guys, can you help by finding a means to reproduce this in a stock install and a new save (not a save that used to be used with mods), I have not had success reproducing this so far.

Things to note:

Does this only occur after loading a docked vessel, or can it occur before?

Does it only happen with one docking port type?

What is the simplest method of reproduction? (fewest parts /steps)

Does it only occur in space?

#4 Updated by Int_10h over 8 years ago

It occurs after loading a docked vessel and before.
It occurs at least with both Clamp-O-Tron Docking Port and the Clamp-O-Tron Shielded Docking Port. I have not observed it with Jr. version, but I would not dismiss that option.
It occurs after docking two vessels in space, but not always. I could see a couple of times while creating a space station orbiting Kerbin (with a lot of docking ports), but I can't help with the exact way to reproduce it.
I hope this can be useful.

sal_vager wrote:

Guys, can you help by finding a means to reproduce this in a stock install and a new save (not a save that used to be used with mods), I have not had success reproducing this so far.

Things to note:

Does this only occur after loading a docked vessel, or can it occur before?

Does it only happen with one docking port type?

What is the simplest method of reproduction? (fewest parts /steps)

Does it only occur in space?

#5 Updated by Trekkerjoe over 8 years ago

File BUG.sfs BUG.sfs added
File Undocking Glitch.craft Undocking Glitch.craft added
File quicksave.sfs quicksave.sfs added
Status changed from Need More Info to Updated
% Done changed from 0 to 10

Trekkerjoe here, I happen to have found a reliable way to reproduce this bug on a new instance of my game.

I am running KSP 1.1.3.1289 on a 64-bit Windows 10 desktop, equipped with 32 gigabytes of RAM, and a GTX960. The CPU is an i7-6700K

I first encountered this bug when I was tried to undock a ferry from my space station. When I tried to disembark, the docking ports jammed in the exact same way as described in the OP. I was able to fix it by editing the save file (included as BUG.sfs). All I did was change 'State = Docked (same ship)' to State = Docked (docker).

I went digging around the save file, and cross-referencing different threads on different threads when I realized what might be happening. It could be the fairings! After I realized this possibility, I immediately created a new game solely for bugtesting and created a rover with a fairing covering the port. Sure enough, when I docked them together, I got the exact same bug. I reproduced this two more times just to be sure. All of them are now bugged.

The rovers in their bugged state.

I have the quicksave as well as the .craft file used in my example.

To summarize, the steps to reproduce are as follows:
1 -Build a small rover with an attachment point on the front.
2 -Attach a fairing, but don't create it just yet.
3 -Attach the dock to the base of the fairing.
4 -Create the fairing so that it overlaps the dock.
5 -Save(you should always save) and launch two of these craft.
6 -Dock them, quicksave, and observe what happens when you try to undock them.

Things to try:
-Using different docking ports.
-Putting the entire rover inside of a fairing, instead of just the docker.
-Changing the save file to reflect that it is docked to get them undocked.
-Decoupling the fairing from the craft to see if it fixes the dock.
-Etc.

Possible workaround:
0 -Back up your save file, or create a named quicksave to work on.
1 -Disable crossfeed on the docking ports and quicksave.
2 -Use control-F to find the docking port you selected. It will have the state 'active = True' Under the tag 'EnableXFeed'
2b -Alternatively, you can search the name of the docked craft if the names are unique.
3 -Make note of it's UIDs.
4 -Follow the UIDs of the docking ports until you find the one with 'State = Docked (same vessel)'
5 -Change the state to 'Docked (docker)'
6 -Save your work and load up the quicksave.
7 -When you click undock, they should behave as normal.

Notes:
-It appears that if both rovers keep their fairings, they reliably break, even if you decouple them afterwards.
-This is not the case when the fairings are decoupled beforehand. This should be tested further, as they successfully undocked even when only one of the fairings was decoupled beforehand.