Search the Community
Showing results for tags 'jammed'.
Found 1 result
-
This is a kind of ongoing saga. I have a theory that game files that are upgraded from one version to another (e.g. 1.7 -> 1.8 -> 1.11) may be subsceptible to creeping problems. One example is "stuck docks". Clicking Undock does nothing except start that "ticking noise" in the background that you know means you are logging exceptions. My state of the art was identifying the pair of docks and generally finding one in a "state = Docked (docker)" but its counterpart is in a state of 'Ready'. Simply resetting both to docker and dockee respectively has been enough in the past to unjam them. Not today. [EXC 21:08:46.250] NullReferenceException: Object reference not set to an instance of an object Part.Undock (DockedVesselInfo newVesselInfo) (at <dc0e5f458c0f4571ad839b9c4153f347>:0) ModuleDockingNode.Undock () (at <dc0e5f458c0f4571ad839b9c4153f347>:0) BaseEvent.Invoke () (at <dc0e5f458c0f4571ad839b9c4153f347>:0) UIPartActionButton.OnClick () (at <dc0e5f458c0f4571ad839b9c4153f347>:0) I have extracted the entire craft from the .sfs file and there are only three docks. One is legitimately Ready (forceTweak = 100) and the other pair (mutually docked) have force 145 and 55. Their dockUId fields point to the corresponding uid correctly. So this looks like a new situation to me. If anyone possesses more advanced magic and can identify the ailment and remedy, I would appreciate the knowledge.
