-
-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mod Installations being forced to AD, Autodetect #2262
Comments
Any clues how it got to that point? The issue template headers you deleted might have been pretty helpful... |
I had unchecked ModuleManager to force the uninstall of dependent mods then unchecked the rest. When I went to reinstall some mods for testing this happened. |
Yeah, that's essentially it. I did it with ALL those mods; not just one at a time. I'll keep a keen eye out for future occurrences. |
OK, maybe there's something weird with those relationships then. What's the full mod list? |
Are you sure you want to know that information? Okay ...
|
Thanks! |
OK, I managed to pare that list down to things that are actually in CKAN and change the names to match their identifiers. It looks like there's a conflict, though. Did you install these two mods with CKAN? Maybe something weird happens if we add a conflict to two mods that are already installed...
|
Get back to you in the am with mods the mods that were manual. But, if memory serves, both IFS & CC were installed a while ago via CKAN. There was not notification of conflict. Since I know IFS is a dependent of some others, I'll uninstall CC, test with a bunch of un/installs and report then too. |
Just .noticed this discussion; might it be related? Throw explanatory message when user selects incompatible mods (Sorry for the crude link, don't know how to do it the right way.) |
True manual installs include: Amazing Curve Editor |
Still haven't been able to replicate. |
I might be able to help here. I am new to KSP and mods but I got autodetect on the very first mod I ever installed. I manually installed mechjeb into my mod free installation. Afterwards I learned about CKAN and installed it. MechJeb has always showed as autodetect, but other mods installed with CKAN can be added and removed without issue. |
You need to manually remove Mechjeb by deleting the entire directory, restarting CKAN, and then you will be able to install it via CKAN |
No reproduction of this since January. Closing; please let us know if it happens again. |
Background
CKAN Version:
1.24.0-PRE
KSP Version:
1.3.1
Operating System:
Linux Jupiter 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Have you made any manual changes to your GameData folder (i.e., not via CKAN)?
No.
Problem

CKAN is forcing AD, autodetect on mods install by CKAN. All mods in this shot were selected for install by CKAN.
The text was updated successfully, but these errors were encountered: