CaribeanSoul

Not sure if you changed anything but on a whim I refreshed the one drive page today (that I still had open in my browser with the super helpful something went wrong message) and the files appeared. \o/ So I was able to grab the beta.

Ok, must be something on my end. I appreciate you checking on it.

Is anyone else having trouble with the onedrive link to download the beta? It just tells me "something went wrong" (super useful, thanks MS) and there's nothing there.

It looks like support for procedural parts has been removed... it would be helpful if the mod description at the top of the thread as well as on github were updated to reflect this. Might save people some time trying to figure out why it isn't working.

Are the parameters/values inside the renamed modules the same so that all is necessary to convert a renamed module is to change the name? (and add the three additional part modules)

Is there a post or some documentation anywhere that shows what conversions have to be done to existing patches to change them over to the new modules?

Be sure to check any other part mods as well. If this release is the same as the most recent constellation release then it may break many existing USI-LS compatibility patches.

Perhaps something like this: // Add bulkheadProfiles to parts that don't have it @PART[*]:HAS[~bulkheadProfiles[]]:Final { bulkheadProfiles = srf }

I think I understand. So in that version it wasn't used to give the user a choice of which toolbar to use for a particular mod?

I'm running this on 1.3.1 version 0.1.4.7 as installed by CKAN and not getting an icon for the toolbar controller on either toolbar. No log errors so far. Is this known to work ok in 1.3.1?

Will playing without remote tech break everything? I've fallen in love with the CommnetConstellation mod and it only works for stock commnet. Just curious if I could work around the RT requirement.

I have an enhancement request. Not sure how difficult it would be, but I think it would be nice to have a tick box on the constellation list to enable/disable connection lines for that constellation. As an example use case: I have a bunch of satellites in orbit as a result of CleverSat contracts. I have them on a separate frequency from other probes and relays. They need to stay connected as I get contracts to move them and whatnot but I could care less about their connection status most of the time and it is just cluttering up my map. The ability to shut down connection lines for that network when I'm not placing or moving one of those sats would be really nice.

I was just here to try and add another data point. If it remains a mystery then that's just how it goes sometimes.

Well I did, obviously. I just thought it might be interesting that the dll was hung up like that in relation to these freezes. Removing science relay got rid of my freezes, btw.

If I had to bet it would be on some interaction between science relay and CommNetConstellation. Probably something related to checking connectivity between vessels that would normally be connected in stock but aren't because they are on different networks in constellation.