despondent_purple_

After loading the game a third time trying to sort out the cause it appears to have fixed itself. I'll thank the kraken and consider myself lucky for now.

Ran into a bug on attempting to edit craft in SPH. Right clicking on the x-1 cockpit is now broken (menu pictured) and subsequently breaks all right click in any assembly building. Leaving and reentering enables right click for all other parts, but upon edit from KCT menu or even the standalone cockpit the menu remains bugs and disables all other right click. I wasn't sure if this was something worth raising an issue on the github over or if I should just try and verify file integrity and maybe reinstall the mod sweet first?

Curious if anyone else has had issues with warp till morning with new update (2.1.0.0)? I'm thinking I probably just jacked something up with my most recent new save but figured I'd check with the community as well.

Final update: After doing a full reset on everything ksp related, installing the express install via ckan, deleting the folder titled "RP-0" in game data and replacing it with the folder titled "RP-1" from the latest stable release on github, I can report full functionality so far. Super stoked to see what the new experience will be like. I've spent half an hour already just looking at the setup for all the new additions. Best of luck to all!

So I tried the manual install and still had issues. I completely deleted all ksp files and ckan including all directories, verified integrity with steam, reinstalled ckan, and now the express download is working fine. Haven't finished downloading to test functionality but this at least fixed the "incompatible RO-xx 2.0.0.0" issue and allowed the install. Worth a shot maybe.

From what I've gathered (very little experience so take with a grain of salt) it appears the express install link in ckan is routing to the previous stable build version (1.13.2.1) of RP-1 which is dependent on RO Solar (im assuming the other modules that updated 2.0 today also) being the previous compatible stable versions for the build. The way the express install is handled through ckan doesnt let you chose to use a previous version (im assuming its suppose to to automatically select it somehow when it walks you through the install and the code just doesnt quite work or something) so therefore it flags an error for an incompatible dependent module. Again horrible, speculation on my part from a less than sound knowledge base but thats what I gathered. Currently installing all dependencies manually and attempting to manually install the RP-1 2.0.0.0 from the zip file on the github. Will update with progress. I should note that the express install is SUPPOSED to flag with the previous version to prevent breaking old saves on startup. I found this out when I first installed the updates and tried to open KSP today. So it is doing the thing. I'm just not sure in the right way/order. Meh. Computers make brain hurt. lol

Edit: it is SAVE-BREAKING. To prevent accidental save-breaking, it is not offered as an upgrade in CKAN. In order to upgrade to it, either create a new Express install, or uninstall the Express Install and then reinstall it. When given the choice make sure to select the regular RP-1 option, not Legacy RP-1.

I'm pretty sure I read something about it not being supported on ckan yet. Probably while everything is finalized to avoid breaking things. Could be wrong though, I'm sure it'll be good to go in the next couple days.