[1.12.x] Connected Living Space v2.0.2.0 (12 Feb 2022)

[dlrk]

Fair enough, I'll probably hold off on using CLS and just treat it as a self-imposed limitation until it's fixed.

[Gordon Dry]

Out of curiosity, but am I the only one with this issue?

And yes, I know, this is not updated to KSP 1.5.1 yet.

So, a part gets the module

		MODULE
		{
			name = ModuleConnectedLivingSpace
			passable = true
		}

and then shows this wall of text in the VAB:

This happens with every part that got the ModuleConnectedLivingSpace.

[Tonka Crash]

  On 11/20/2018 at 11:29 PM, Gordon Dry said:

Out of curiosity, but am I the only one with this issue?

Expand  

@Gordon DryYou might be.

I have CLS on 1.5.1 and only get one block of CLS info in the VAB. As far as I can tell CLS works normally in 1.5.1. Have you looked in the ModuleManager.ConfigCache to verify that there is only one CLS module added to each of your parts? 

[Gordon Dry]

  On 11/21/2018 at 2:12 PM, Tonka Crash said:

Have you looked in the ModuleManager.ConfigCache to verify that there is only one CLS module added to each of your parts? 

Expand  

That's what I did prior posting the above.

[Tonka Crash]

@Gordon Dry Do you have any mods that are supposed to modify the information displayed in those the VAB part tooltips? Did it start recently or has it been there since you updated to 1.5.1? I'm not seeing the problem and I know you run a lot of mods with custom patches, so I don't really have any idea what it could be. 

[Gordon Dry]

@Tonka Crash @linuxgurugamer I use this mod for some time now:

The issue occured vaguely at the same time I added this mod, afaik when looking back.

[Tonka Crash]

@Gordon Dry I just installed that mod and still don't see the issue. I do get the extended science information, but nothing unexpected, still only one entry for CLS.

[Gordon Dry]

Well, there is at least one badass mod in my install.

As always ofc.

[taniwha]

@Papa_Joe: I've sent a PR with a few fixes: CLS now updates properly when a hatch is opened or closed and multiple docking ports on a part are supported (and ModuleDockingHatch is generally cleaner).

[Papa_Joe]

  On 11/28/2018 at 5:56 AM, taniwha said:

@Papa_Joe: I've sent a PR with a few fixes: CLS now updates properly when a hatch is opened or closed and multiple docking ports on a part are supported (and ModuleDockingHatch is generally cleaner).

Expand  

Thanks!  I saw the pr pop up. I'll look at it this evening US Pacific time.

[Krastynio]

Hello, i have had a minor problem with CLS.
All the parts i am using for a subassembly are passable in the VAB but somehow (moving some part around probably) a few became impassable and i didn't realized it until i was in flight.. i am trying to use KML to edit the config but still the CLS does not "extend" to the parts in question..
The same subassembly in the VAB simply needed to reattach the parts in question to be fully passable, so it was a "bug" of the subassembly.
There is a way to change the CLS inflight?
Otherwise i have to deorbit the subassembly and relaunch another one =( the Kermanity!!
(the problem occurred beetween the octocore of USII and an adapter from SSPR.. but i have those same modules on the same vessel who are working just fine.. sooo)

p.s. i think Jeb created an impassable wall with empty snacks box and didn't told me

ERRATA CORRIGE: i cried wolf too soon; meddling in the config and rebooting corrected the issue

Edited December 4, 2018 by Krastynio

[Darkherring]

Is it working for 1.6? As I'm having some issues - I cannot transfer crew after docking.

[taniwha]

@Darkherring: This is a bug central to CLS (I had the same problem in 1.5.1). I've sent @Papa_Joe a PR that fixes it.

[Tonka Crash]

  On 1/7/2019 at 8:03 PM, Darkherring said:

Is it working for 1.6? As I'm having some issues - I cannot transfer crew after docking.

Expand  

To get around the bug, EVA and board someone after opening your docking ports. 

[Jacke]

  On 1/8/2019 at 7:11 AM, taniwha said:

@Darkherring: This is a bug central to CLS (I had the same problem in 1.5.1). I've sent @Papa_Joe a PR that fixes it.

Expand  

Alas, @Papa_Joe hasn't logged in since November.  Perhaps you could post an updated compile?

[taniwha]

Yeah, I might have to.

[Tallinu]

Taniwha, that would be very much appreciated.  

I've been using "allow unrestricted transfers" rather than just uninstalling since I wanted to make sure I was still building out of parts that were passable, for when it was working properly again. I didn't know you could force it to update by exiting and re-boarding though. Thanks for pointing that out, Tonka!

Actually, I can't get that to work. However, the next time any changes are made like docking/undocking or decoupling, that seems to force an update to whatever was already connected.

For instance, on this test rig I made while trying to work out the details of the bug so I could report it (which turned out to be unnecessary), it starts with a command pod, two docking ports coupled together, and another crewed part with a third docking port on top. Then there's a framework going up to a decoupler holding another capsule with a docking port just above it, so that when decoupled, the slight fall brings the two unmated ports together. If I close the hatches which start out coupled together before firing the decoupler, the result is three separate living spaces. Boarding and exiting any of the pods doesn't seem to do anything. But then if I decouple the ports that start out attached (after opening both hatches on the newly docked parts), then the two sections still attached to each other finally merge into one space.

Still easier to just use the unrestricted transfers option for now though.

 

Edited January 31, 2019 by Tallinu
Correction

[taniwha]

Ok, I have done up an unofficial build. Note that it is a zip of CLS from my working KSP directory, so it might not be quite pristine, but that should be limited to cls_settings.dat and the main dll (of course). I have not touched CLSInterfaces.dll at all, so I hope it still works

Download patched CLS

my github fork

Edited January 31, 2019 by taniwha

[Tallinu]

Thanks, now it seems to work just fine, so far!

[dlrk]

Taniwha, what version is your build for?

[taniwha]

@dlrk: Built against 1.5.1 but seems to work in 1.6.1, probably works in 1.4.x.

[Murdabenne]

Any hope of a 1.7? Or even a 1.6.1? I really miss this and Ship Manifest

[Tonka Crash]

  On 5/5/2019 at 10:39 PM, Murdabenne said:

Any hope of a 1.7? Or even a 1.6.1? I really miss this and Ship Manifest

Expand  

It's still working the same as always in 1.7 for me, installed from CKAN.

[wat4_dor]

  On 5/6/2019 at 12:49 AM, Tonka Crash said:

It's still working the same as always in 1.7 for me, installed from CKAN.

Expand  

The СКAN says that the latest version of the mod 1.4.9

[Tonka Crash]

  On 5/6/2019 at 9:43 PM, wat4_dor said:

The СКAN says that the latest version of the mod 1.4.9

Expand  

It really doesn't matter what CKAN says, CKAN doesn't really know. It's "compatbile" mods are based on a text file the mod maker included the last time the mod was updated. This has little to do with what versions of KSP the mod will actually work with. Last time I looked I have mods from 1.4.1 running fine on 1.7. 

Since 1.4 most mods will work with the latest versions of KSP. There are exceptions: Kopernicus has a unique release for each KSP version and KSP 1.7 did break a handful of mods like KAS, KPBS and Wind Tunnel. It's usually safe to assume mods are compatible with new KSP versions unless you see problems and the forum thread is filling up with people claiming the mod is broken.