peteletroll

New version available: now engineers in EVA can weld docking port pairs. This can't work on same vessel docked pairs! For instance, if you build a ring structure, one of the couples won't be weldable.

I'm testing DockRotate with the fix: it works, apparently. See here:

Short answer: apparently it is. Long answer: I tested @JPLRepo's fix in my current career. It looks like DockRotate is not only compatible, but even necessary: after installing the fix, undocking becomes problematic ("Undock" button doesn't show up). DockRotate's port state checker can fix this. I still get NREs from deep inside ModuleDockingNode: [ERR 11:40:04.455] Module ModuleDockingNodeFixed threw during OnStartFinished: System.NullReferenceException: Object reference not set to an instance o> at ModuleDockingNode.get_VisualTargetAngle () [0x00014] in <4a4632fe4eb0471fa0f9f87bb7432bc2>:0 at ModuleDockingNode.OnStartFinished (PartModule+StartState state) [0x001f9] in <4a4632fe4eb0471fa0f9f87bb7432bc2>:0 at Part.ModulesOnStartFinished () [0x00042] in <4a4632fe4eb0471fa0f9f87bb7432bc2>:0 Thanks! Always appreciated.

Hi @Kyoung1229, welcome to the forum! My personal suggestion is to start by modifying an existing mod.

Hi @Kerbal2205, welcome to the forum! I moved your post to the modded tech support section.

I noticed yesterday. Too bad I tried setting canRotate to false with a MM patch, but there's drift anyway...

The only thing stock has and DockRotate hasn't is rotation motion via axis control - but I'm working on that.

@linuxgurugamer, if you mean how do I disable DockRotate when stock rotation is used, the code is here: https://github.com/peteletroll/DockRotate/blob/e407060144d6a47467a05345482524f8bb2f452d/DockRotate/ModuleDockRotate.cs#L263 If you mean how DockRotate works in general, that's a longer answer ;-)

New release! This will work only on 1.12.x. @jordanjay29's bug is fixed in this release. Also, DockRotate won't accept rotation commands if stock rotation is being used: in other words, if stock rotation angle is not zero, DockRotate rotation is disabled to keep the Kraken away.

Hi @WulfyKerman, welcome to the forum! There's many Canadarm mods around here: the best place to ask is the release post of the mod you're using.

Thanks for your report, @jordanjay29. Could you please try the DockRotate.dll you can download at the following link? https://drive.google.com/file/d/1URc6KgWP55BRsDXIGpklkqGQzR9g2uWY/view?usp=sharing Let me know if this works, and send logs!

Hi @GER FelixN, welcome to the forums! If you have a question about a specific mod, it's easier to find help on the mod post.

After some testing in 1.12, it looks like it's working. I'll release a recompiled version soon™. It has some problems when used together with the new stock rotation: if you rotate with DR then with stock, or vice versa, you get weird results. So, until I find a workaround, please use just one of them at a time!

Thanks @Hohmannson! I was considering this mod a failed experiment. Glad to see it can still be useful.

Hi @lil_henry, welcome to the forums! You may ask your CKAN question on the CKAN main post here too:

New release! This should solve a problem with missing rotation setup in some cases (i.e. rotation buttons not visible when they should).

Google translate: "Repair task: I cannot complete the satellite repair task." Welcome to the forums, @sanek10433! There's a Russian section in the International subforum, I recommend you to post your question in Russian there. Outside of the International subforum, English is preferred. I also moved your question to the "Gameplay Questions" section. Happy landings!

Locking at @DVQuill request.

We'll see, @Daniel Prates. I secretly hope they took a look at DockRotate code

Hi @Jr_kerman303, welcome to the forums! There's a Portugese section in the International subforum, I recommend you to post your Portugese question there. Outside of the International subforum, English is preferred. Happy landings!

Becoming stock is the best thing that can happen to a mod! But I'm going on with DockRotate, because it apparently has features that KSP 1.12 has not. And because I'm having fun mantaining it. Fly safe!

Both would be great By the way, this is the problem from your log: [LOG 11:58:34.870] [DR:81296] [DockingStateChecker] Check report: ################################################################################ checking vessel IKSS checking node octans.docking.port.s0p5.2.female-2740319917 "Ready" checking node octans.docking.port.s0p5.2.female-2835895857 "Docked (same vessel)" has docking joint -4557630, octans.docking.port.s0p5.2.male-1309863526 > octans.docking.port.s0p5.2.female-2835895857 other is octans.docking.port.s0p5.2.male-1309863526 "Docked (dockee)" fixing octans.docking.port.s0p5.2.male-1309863526 "Docked (dockee)" -> octans.docking.port.s0p5.2.female-2835895857 "Docked (same vessel)" fixed to octans.docking.port.s0p5.2.male-1309863526 "Docked (dockee)" -> octans.docking.port.s0p5.2.female-2835895857 "Docked (docker)" *** redundant same vessel joint -4591844, octans.docking.port.s0p5.2.female-2835895857 > octans.docking.port.s0p5.2.male-1309863526, same vessel *** checking node octans.docking.port.s0p5.2.female-2972025719 "Ready" checking node octans.docking.port.s0p5.2.female-660780187 "Ready" checking node octans.docking.port.s0p5.2.male-1309863526 "Docked (dockee)" has docking joint -4557630, octans.docking.port.s0p5.2.male-1309863526 > octans.docking.port.s0p5.2.female-2835895857 other is octans.docking.port.s0p5.2.female-2835895857 "Docked (docker)" pair already checked checking node octans.docking.port.s0p5.2.female-3157629700 "Ready" checking node B10.APASv2-797386492 "Docked (same vessel)" has docking joint -4559572, B10.APASv2-2601923201 > B10.APASv2-797386492 other is B10.APASv2-2601923201 "Docked (dockee)" fixing B10.APASv2-2601923201 "Docked (dockee)" -> B10.APASv2-797386492 "Docked (same vessel)" fixed to B10.APASv2-2601923201 "Docked (dockee)" -> B10.APASv2-797386492 "Docked (docker)" *** redundant same vessel joint -4591848, B10.APASv2-797386492 > B10.APASv2-2601923201, same vessel *** checking node ht2.CBM-1928871713 "Ready" checking node ht2.CBM-2062850118 "Ready" checking node B10.APASv2-2601923201 "Docked (dockee)" has docking joint -4559572, B10.APASv2-2601923201 > B10.APASv2-797386492 other is B10.APASv2-797386492 "Docked (docker)" pair already checked checking node ht2.CBM-2952942123 "PreAttached" has docking joint -4561294, ht2.CBM-2952942123 > ht2.CBM-3140945412 other is ht2.CBM-3140945412 "PreAttached" checking node ht2.CBM-3127560415 "Ready" checking node ht2.CBM-3140945412 "PreAttached" has docking joint -4561294, ht2.CBM-2952942123 > ht2.CBM-3140945412 other is ht2.CBM-2952942123 "PreAttached" pair already checked checking node ht2.CBM-4004225601 "Ready" checking node B10.APASv2-47190655 "Docked (same vessel)" has docking joint -4562156, B10.APASv2-710710778 > B10.APASv2-47190655 other is B10.APASv2-710710778 "Docked (dockee)" fixing B10.APASv2-710710778 "Docked (dockee)" -> B10.APASv2-47190655 "Docked (same vessel)" fixed to B10.APASv2-710710778 "Docked (dockee)" -> B10.APASv2-47190655 "Docked (docker)" *** redundant same vessel joint -4591852, B10.APASv2-47190655 > B10.APASv2-710710778, same vessel *** checking node B10.APASv2-710710778 "Docked (dockee)" has docking joint -4562156, B10.APASv2-710710778 > B10.APASv2-47190655 other is B10.APASv2-47190655 "Docked (docker)" pair already checked ################################################################################ The misbehaving port pairs are connected by two PartJoint instead of one: they have the regular joint between parts (Part.attachJoint), and a joint that is usually present only when you have multiple dockings, i.e. there's a loop in your craft structure (ModuleDockingNode.sameVesselDockJoint). Since the docking pair is somehow docked twice, you get two "undock" buttons. And if you press one of them, you release one of the two joints, but the other one keeps connecting the ports together. I had this problem once, and DockRotate is configured to solve it. It's weird it doesn't fix it for you. A possible solution could be to "undock" the "multiple docking" joint (only way to find the right button is to try), then F5/F9, and check if the warning is gone. Backup your save file first!

@Hachiro, your log shows some of the docking ports are misbehaving in a way DockRotate should be able to fix: it happened to me too. Is the problem still there if you F5/F9 or timewarp a little?

Hello @Jebediah Studios, welcome to the forums! This is a pretty old thread, you may try asking your question on the Kopernicus main thread.

The clean solution is to use reflection: big topic!