BlooSkies

So at least part of the problem with the Steam reviews, I would imagine, is that the Steam storefront loudly proclaims that the last update you've provided was on the 24th. Obviously that isn't the case, provided people care enough to come here, but that relies on an expectation for the Steam user to first go to the forums and then see the pinned topic over there AND click the link in that topic that links here. Important updates about the state of the game like this should really be crossposted on the Steam announcement feed.

The full list is pretty extensive and probably not super helpful, but judging from your previous post, you're installing CommNet Manager, which the release version of Constellations is not compatible with. You'd need to use the beta. And that might be broken. Or CNM itself might be broken. No other mods ever implemented CNM as far as I know, so there's no benefit to installing it in the first place anyway. I'm just using release 1.5.7 from CKAN, no CNM.

Y'all have something else going on there. Mod is working flawlessly for me on 1.12.5, installed through CKAN.

Apologies if this has been addressed in the past, but, are there any known mod conflicts that result in ships getting torn apart when the rotation is imparted back to them? Or, recommendations for building ships better to avoid them succumbing to this? No logs or anything, because it's not strictly an error. Probably just my inability to build a ship. But I thought I'd ask anyhow.

A rudimentary parsing of the code for this particular issue on the Git still does this if that file is present, regardless of its content. I feel like an ass for even suggesting this but, did you actually push the changes for this?

Atlas updated KIFA's patch to not run if PartVolumes is in, and LGG said that this particular check was removed. I can only assume that's why this got brought up. Because, yeah, it certainly sounds like that screen should no longer have any reason to come up.

I just meant in terms of, between 1.10 and 1.11. I had -- perhaps wrongly -- assumed you had been testing in 1.11 and not encountered the bug yourself or such. The VesselNaming per command module thing goes all the way back to version 1.4, so I'm surprised this is only coming up now.

To note, the same thing is occurring for me on 1.11.2 so it's not a KSP version thing. Haven't gotten around to the beta yet, I'll do that and try to mock up a craft file with minimal mods when I'm free, but that won't be until Tuesday. I'm using ReStock, so that may be part of it, as I believe I have at least one of the inline probe cores it adds in every ship I make.

For what it's worth, I have it installed through CKAN with no issues, so I'm presuming this is something a little more complex. Maybe a corrupted cached download on their end?

Hey, congrats on the release! Looks like MM is mad about the Wormhole re-homing config, though [WRN 13:47:16.573] more than one :NEEDS tag detected, ignoring all but the first: StrangeNewWorlds/KopernicusConfigs/Wormhole re-homing/@Kopernicus:AFTER[StrangeNewWorlds]:NEEDS[KopernicusExpansion]:NEEDS[BeyondHome] [WRN 13:47:16.574] more than one :NEEDS tag detected, ignoring all but the first: StrangeNewWorlds/KopernicusConfigs/Wormhole re-homing/@Kopernicus:AFTER[StrangeNewWorlds]:NEEDS[KopernicusExpansion]:NEEDS[WhirligigWorld] [WRN 13:47:16.574] more than one :NEEDS tag detected, ignoring all but the first: StrangeNewWorlds/KopernicusConfigs/Wormhole re-homing/@Kopernicus:AFTER[StrangeNewWorlds]:NEEDS[KopernicusExpansion]:NEEDS[GPP] [WRN 13:47:16.574] more than one :NEEDS tag detected, ignoring all but the first: StrangeNewWorlds/KopernicusConfigs/Wormhole re-homing/@Kopernicus:AFTER[StrangeNewWorlds]:NEEDS[KopernicusExpansion]:NEEDS[AlternisKerbolRekerjiggered] [WRN 13:47:16.574] more than one :NEEDS tag detected, ignoring all but the first: StrangeNewWorlds/KopernicusConfigs/Wormhole re-homing/@Kopernicus:AFTER[StrangeNewWorlds]:NEEDS[KopernicusExpansion]:NEEDS[GEP_Primary]