Dazpoet

D'oh, at this time there isn't really a solution to this that I know off short of manually removing the clashing files and then updating the mod. We're working on better handling of these situations though, see below. It sounds like you'll find https://github.com/KSP-CKAN/CKAN/issues/949 interesting and relevant

This looks amazing and might finally give me a good reason to build planes and proper biome hoppers

We've run into a snag somewhere, see https://github.com/KSP-CKAN/NetKAN-bot/issues/13 for tracking EDIT: Manually updated and grabbed the latest one just now, our latest version is now 2.1.

Aha so it's certain mods and not random ones, that makes life easier! I'm going to assume that those certain mods are perhaps, EVE, Astronomers Pack, TAC-LS, PlanetShine, DistantObject (yep) and anything else which has a multitude (>1) configs available through CKAN. You're running into the issue which https://github.com/KSP-CKAN/CKAN/pull/1002 will fix. Basically CKAN need you to also choose a config to solve the dependency for the mod in question. Somewhere we had a coderegression which made the GUI unable to handle these situations but the awesome RichardLake is fixing us up with a new better way of fixing it. For now you'll need to pick the configs manually, they are normally named <modname>-<config> or <modname>-<clouds <quality>> or something similar to those. AD means autodetected which all mods who are manually installed and located by CKAN are marked as. Basically CKAN doesn't play nice with AD mods and don't touch them since it cannot guarantee consistency since it has no idea how those mods where installed. Manually removing them and running 'ckan scan' followed by 'ckan update' in a terminal should resolve the autodetected status and then you'd be able to install them through CKAN clients. If they still show up as AD there might be some fragment of the mods left laying about which CKAN locates and thinks is the entire mod. Also you're correct about removing and reinstalling CKAN, that would be a bad idea since all mods will then be AD. Information about your installed mods are in the CKAN folder inside the KSP root directory so just messing around with the ckan.exe is ok but poking about inside the CKAN folder is not.

You need to manually choose one of the cloudpacks for it aswell, low med or high. There is a fix coming which Will remedy this problem but it is a release or two away still.

As you posted that I'm 99% sure I know what your error was. Did you by any chance have the Amsterdam Mirror in all your tests? That one throws that specific error since it's currently down.

Ok this does sound weird and at this time my best guess is a network issue. Are you perhaps behind a firewall? We've had a few reports that some countries block github, although if you managed to download CKAN I'm assuming you can access it? What is the exact error, can you perhaps provide a screenshot? As per your initial post I gather that commandline doesn't work either, does issueing 'ckan update --debug' provide any additional information?

Presumably nothing, it's not your problem that a mod states to be incompatible with yours. I just answered a question Sorry for intruding with othermoddly problems in your thread, I try my best not to.

Looks like something on the other side is saying "no mods for you", if you where on linux/os x I'd advise updating your certificates but that's not usually necessary under windows.. Is this a persistant issue (multiple hours) or something that happened intermittently? Just to clarify. You added these mods manually? Or did you add them through CKAN in an earlier version of KSP where CKAN kept track of them and now they are AD? Would you mind opening a github issue about this and include the exception? Sounds like something we should check for! Does commandline work, like can you do 'ckan update' followed by e.g. 'ckan install ModuleManager' ? Do you have any mods installed right now or is it a fresh install? As I posted in the thread you can track the progress of this over at https://github.com/KSP-CKAN/NetKAN/pull/1457 where I also link the PR which added the 1.2 versions of both. The reason it isn't showing up in CKAN is that it isn't merged yet (aka not added to our indexing service) because the upgradepath needs looking into. Your locally installed mod isn't showing up because the gui requires mods to exist in the upstream to be visible. Doing a 'ckan list' in a terminal should show CTN as installed and tracked still. GUI will get this functionallity added once https://github.com/KSP-CKAN/CKAN/pull/1005 is merged into the codebase. The reason the two older versions are conflicting is because they write the same data (same filenames, same location) but with slightly different information (and the same name on the pieces) in them so trying to install one while the other is installed would require overwriting (and break existing crafts) which CKAN doesn't do.

We're tracking the addition of a .netkan file over at https://github.com/KSP-CKAN/NetKAN/pull/1457 so -ctn- you need do nothing at all to resolve the situation save wait for us to solve our own screwup. Please tell me where information that this works was located so I can fix it. We do not currently have such a functionality. Also please put requests for mod metadata fixes into the CKAN thread or, preferably, onto the CKAN githut pages so we can adress them.

This would be why Fetched from https://kerbalstuff.com/mod/773/WarpShip

That picture just made me 5000% more hyped to visit Dres

Ugh that first part sounds terribly much like we might have a packaging error, I assume you had EVE installed while doing that? Did you have any of the EVE clouds installed? I'm trying to track this error down but can't quite wrap my head around it yet. Can you upload your registry.json somewhere so I can have a dev take a look at it and try to reproduce your error? It's in a folder named CKAN inside your KSP root directory and should be able to help us find out what is making things go wrong. Even better would be a github issue detailing any and all ways of reproducing your error together with your registry.json file. Are you using mono to run CKAN in windows? If that's the case try without mono since it's not needed there. I must admit that until right now I had never heard of Edge of Oblivion. I'm kinda unclear on what it is, is it another version of Astronomers pack (we currently only index Interstellar.V2 of it) or some kind of addon to it? As for right now EVE and Astronomers Pack - Interstellar are available in CKAN and looking at the metadata for them it would appear everything goes neatly into a single folder and that all readmes and other instructions are filtered out during installation.

pjf quite recently added his current thoughts about this to https://github.com/KSP-CKAN/CKAN/issues/481 so I recommend checking there.

Not sure I understand the question but do you mean stuff like Ven's stock revamp? As for skybox I know we have stuff for clouds but not sure about skybox.

I'm going to assume that is your list of installed mods and not the thing you're trying to install? So I managed to almost reproduce this issue by trying to install AVP on an old 0.90 testinstall... I did get a ModuleNotFoundKraken but it didn't mention KAE nor any other mod. However after running a refresh it resolved itself. When did you last run a refresh? I'm having some very weird errors with AVP where I had to choose both AVP and one of its Cloud configs (low, medium, high) before it allowed me to continue to the Changeset tab. This might be related to an issue we're currently tracking on github related to TAC-LS which has a not totally dis-similar issue. There is a PR in the works which will hopefully get merged in the coming days which migth also resolve this situation. I've been through the metadata a few times now and I'm continously unable to locate the link between KAE and AVP so if it's there it'll be either very well embedded in a depedency of a dependency or super obvious. Long-story short, try refreshing and picking both AVP and a Cloud config, see if that solves the gui problem. If not try using commandline and issuing the command 'ckan install AstronomersPack' and see if that works. The latter _should_ work 100% while the former might have some problems until https://github.com/KSP-CKAN/CKAN-GUI/pull/137 is merged into, hopefully, the next client. Why this problem keeps throwing a KSPAPIExtensions error is beyond me. - - - Updated - - - The readme.txt file is not created by CKAN, it's where KSP keeps its versiondata which we peek at to see which version is installed. Although I agree it might be a "casual" file I have yet found a reason to need to delete it, even before I needed it for CKAN :S

Second time today I hear about this and I'm unable to reproduce it on my end. Can you provide a copy of the error and explain the steps leading up to it so I can squash it once and for all?

I must admit I don't know how KSP-AVC installs work but it is _NEVER_ recommended to install in any other way than through CKAN if you want CKAN to properly work.

We have a fix in the works now (https://github.com/KSP-CKAN/CKAN-meta/pull/560) which will revert all mods back into the metadata index but are currently holding it back while trying to locate what caused this in the first place and making sure it doens't happen again.

The bot is doing funny things, we're still working on it.

PSA: Our indexing bot just turned murderous and exploded a major part of the metadata repository. We're working on a solution and no changes are lost at this time since github allows us to revert all the damage!

I never knew I wanted this until I saw this thread, now I can't wait! I've generally solved these things in the horrible way of packing very small craft into very large fairings on way to big rockets when I've wanted e.g. planes on Eve.

The warning about URL handlers is nothing to care about, it is for a not yet fully implemented functionallity. I've never seen an issue quite like this one I think so we'll have to start out with the basics. What is the output of 'mono --version' in a terminal? Does commandline work? Aka can you issue a command like 'ckan install ContractConfigurator' and it does what one would expect it too? In the gui can you use the up and down arrows in the modlist and click space to select/deselect mods and if so does it work better than using the mouse? I recommend you open a github issue about this and add the information request above aswell as your initial problems to it. - - - Updated - - - Please add to https://github.com/KSP-CKAN/CKAN-GUI/issues/87 so we can see what people want

In the terminal you can do 'ckan remove --re .' which will prompt you for an uninstall of all mods. Not implemented in the GUI yet though.

It was added like half an hour ago so I think you might want to refresh your client https://github.com/KSP-CKAN/CKAN-meta/commit/7f83a42962d8dadde19a1bb4f77ba2f91ac27061 Best place to check what mods are in the works for being added is https://github.com/KSP-CKAN/NetKAN/pulls and https://github.com/KSP-CKAN/CKAN-meta/pulls rather than asking the author multiple times.