SilverlightPony

As best I can tell, the Ares Cap docking port is not crew-passable. Is there any way I can fix this on my end with a .CFG tweak or something? If not, consider this an update request. [EDIT] Couple of side-notes: CLS and Waterfall support would be awesome. Overall, still digging the mod.

Possibly related to ShadowMC2's problem above, when I tried launching KSP a few minutes ago, I got this over top of the main menu. Couldn't seem to click on anything, had to kill the process.

I just ran into the same issue with one of the SSPXr size-adapter crew tubes. Tried to get around it by going EVA, but that locked up the game* and I had to kill the process. Will edit this post with a pad-test screenshot once I'm back in-game. * (in retrospect, may have just been an input lock issue? Game was still processing, just couldn't move camera or kerbal, or re-board the pod) [EDIT] Two screenshots. One in the VAB showing the "more info" parts list popout with CLS info, the other on the pad with the CLS window and highlights up showing not passable. Side-note, the CKAN metadata still links to the old "CLS (adopted)" thread. [EDIT 2] Well, now it's working with those example parts. Not sure if I just misunderstood what I was looking at, or if something I did during various restarts (mostly unrelated to either of these mods) fixed it. Having a crew-transfer issue with other mod parts in my career save; checking configs and patches on that now.

I was just coming here to report the same thing with one of the size-adapter crew tubes. At least I know I'm not alone.

GU has rescale settings in its own configs, but they seem to be less comprehensive than what's offered here. I get the impression that's what's conflicting with the 2.5x config I've been using. Someone in the GU discord gave me the config below, which seems to rescale the stock planets, but not the orbits or SOIs--I backed up my save and tried this on my main install, and a bunch of my comsats were no longer in Kerbin orbit, and the ones that were still there were much closer to the edge of SOI than before (at least one was now on an escape trajectory). I tried modifying this with stuff from this thread's 2.5x config, but that resulted in no rescale happening at all (at least for the Kerbol system).

Are you referring to just adding science points in the cheat menu, or is there a way to specifically mark [$experiment in $biome/$situation] as completed and claim the science from it? 'Cause the latter is what I'm thinking of.

Anyone else wish there was something like this, but for the entirety of Kerbin?

Got an issue between Rescale Continued and Galaxies Unbound. For now, I'm testing the setup with a fresh, clean KSP install. That said, my goal is to eventually add GU to an existing save (stock system + OPM + MPE + 2.5x rescale + a bunch of part and QOL mods). Created new KSP install instance, and added it to CKAN. Installed Kopernicus. Installed GU following instructions on GitHub. Launch game. Game starts up fine. Create new sandbox save. Loads into KSC just fine. Exit game, close KSP. Add Sigma Dimensions, leave its configs at stock. Test game, still works fine. Add 2.5x Rescale! Continued config. Test game, encounter problem: "Loading Expansions" step completes fine. Game hangs at pre-main-menu loading screen (black screen, loading animation at bottom-right keeps going). KSP.log shows Kopernicus-related logspam. Kopernicus log shows that it gets through the "loaded body" steps for all the stock planets, then breaks with: [LOG 18:53:29]: [Kopernicus]: Configuration.Loader: Failed to load Body: Anuq: Object reference not set to an instance of an object ... when it gets to the first GU planet. GU configs include options for rescaling GU stuff with SD, and folks over in the GU discord offered suggestions for using that to also rescale stock stuff (including a cfg that might do the trick, in the spoiler below), but I'd like either a solution from the Rescale Continued side of things, or at least a second opinion on the provided cfg to hopefully ensure it won't screw up anything in my existing save. [EDIT] Well it at least loads to the main menu with the cfg they gave me, so that's a start. [EDIT 2] Gave it a shot. It loads the save (which I had backed up, to be safe), but it doesn't rescale the orbits or SOIs, so it's a no-go as it is.

Unrelated to the above, with Filter Extensions and Moar Filter Extension Configs installed, the 0.65m, 1.25m, and 1.875m Wheel-O-Decoutron ACDs all show up under the 2.5m size filter rather than the filters for their respective sizes.

Got a setup issue. For now, I'm testing GU with a fresh, clean KSP install. That said, my goal is to eventually use it with an existing save (stock system + OPM + MPE + 2.5x rescale) Created new KSP install instance, and added it to CKAN. Installed Kopernicus. Installed GU following instructions on GitHub. Launch game. Game starts up fine. Create new sandbox save. Loads into KSC just fine. Exit game, close KSP. Add Sigma Dimensions, leave its configs at stock. Test game, still works fine. Add 2.5x Rescale! Continued config. Test game, encounter problem: "Loading Expansions" step completes fine. Game hangs at pre-main-menu loading screen (black screen, loading animation at bottom-right keeps going). KSP.log shows Kopernicus-related logspam. Kopernicus log shows that it gets through the "loaded body" steps for all the stock planets, then breaks with: [LOG 18:53:29]: [Kopernicus]: Configuration.Loader: Failed to load Body: Anuq: Object reference not set to an instance of an object ... when it gets to the first GU planet.

Sorry, I got a solution (or at least a workaround) from Reddit but forgot to post it here. Turns out, the problem wasn't the fairing/payload-bay. I was trying to run the experiments via ScienceAlert without realizing that the experiments in question need to be manually deployed via the parts' right-click menu first. The last time I was doing a career or science playthrough, triggering a deployable experiment by any method would automatically deploy it if needed. This still works for some experiments (even US ones, like the Magnetometer Boom), but the US Atmospheric Science Unit (the 2Hot/PresMat thing) and US Materials Bay needed to be deployed manually. Once deployed, running the experiment via ScienceAlert worked fine.

Just wondering, is there a particular reason this isn't available on CKAN?

Very annoying issue: I've got some Universal Storage science parts inside a Universal Storage payload fairing. The fairing is open. Some of the experiments give the error "Cannot perform experiment while part is shielded." and refuse to run. So far it's happened with at least 3 different US science parts and 2 different US payload fairings. I've asked about this in a few other places, and have gotten no response. Any ideas?

Same issue cropping up with the cylindrical 2.5m fairing and an 8-wedge center bit. Some experiments worked, some complained about being shielded. Very annoying.

Make it an option, then--switchable either via a config edit or an in-game thing. I'd just really like a way to tell which engines have Waterfall configs and which ones don't while still in the VAB/SPH.