politas

Tried to quickly test this morning with a clean KSP + Kerbal Sports, but I didn't get a "start fishing" option on the coast, and I ran out of time.

Ah, one of its dependencies needed fixing. Should be good now.

Nothing needed for SurfaceExperimentPack, v1.4.1 is already marked for KSP 1.1.2. KerbalFlightData - https://github.com/KSP-CKAN/NetKAN/pull/4012 Thanks for letting us know!

Done. Thanks to @NathanKell's forward thinking, it was already updated.

Ah, output_log.txt is what Player.log is called in Windows. I had forgotten that. I'll run an experiment and get you my Player.log.

If you can tell me where I would find such a file on Linux (I know where KSP.log and Player.log are, but that one's new to me), I can try to create a new one, but I've restarted the game, so it's probably been overwritten.

Thanks for letting us know! https://github.com/KSP-CKAN/NetKAN/pull/4002

Just been using that build on KSP 1.1.2, and it causes a KSP crash when I climb back into my plane and recover the vessel. Went fishing twice, crashed KSP twice. Don't know if it would be ok if I took off instead of recovering.

DeadSkins should be added soon (and AviationLights is moving to the new unofficial maintainer's GitHub, so it will become 1.1.2 compatible, too.) If you have the time to make an account on GitHub and start submitting changes via Pull Requests, we'd love you to bits! You'll get plenty of assistance to get the code sorted out, so don't worry too much about getting everything perfect straight away.

You mean like the Forum Thread link in the Help - About? Yes, that mod author hasn't recovered a lot of mods that used to be on Kerbalstuff. Thanks for the headsup, though, I'll remove the broken link. We do have a mirror of that, so it's still available for KSP 1.0.5, but there's no sign of a new version, yet. The mod author's Forum name is @amankd, and his/her primary focus is on wheel mods, which are probably going to require a lot of work to fix with all the Unity5/KSP1.1 wheel collider changes. That one has author-hosted metadata. I'll submit a change for it. Thanks for the heads-up!

Hi Andem. You've posted this on Spacedock with a CC-BY-4.0 license, but the original license used by kyeon (which you are including in the download) was the slightly more restrictive CC-BY-NC-SA-4.0. Can you fix up the license on Spacedock? Legally, you can't drop those attributes.

CKAN does not use the SVE github for this very reason. There has never been a release of SVE on Github, only pre-releases. CKAN uses the Spacedock release, which has not been updated from its original 1.1 KSP version, which CKAN translates to 1.1.0. I'll open up the version compatibility for all 1.1 releases.

Hi Athlonic. I'm not sure why the bot hasn't picked up the changed metadata on Chatterer, but I've submitted a change that should get it appearing again. The easiest way to force CKAN to see a change in your metadata is to push a new release onto Spacedock. That will make CKAN update immediately, now that we have a push notification system from Spacedock thanks to @godarklight We aren't currently using the avc .version file on Chatterer, but I can fix that.

The module name listed in those exception reports is a red herring. There's something weird with your mod compatibilities. Try installing as few things at a time as possible, and check the dependencies in the relationships tab. We're not trying to penalise anyone, we're just trying to get it all to work, and Squad made it really hard with 1.1.1 and 1.1.2 coming out so quickly. Things will settle down in time, but as I've said, CKAN is not a tool capable of 0-Day perfection.What we need is clear and simple reports of mod compatibility, not people complaining over and over again that they can't override the compatibility mechanisms. We know you want to be able to override the compatibility mechanisms. We've got ideas for that in the pipeline, but they aren't going to happen in a few days.

If you want to install a whole bunch of "incompatible" mods, then follow NecroBones' advice three posts before yours, and change the version number in the Readme.txt file temporarily. Or you could, well, wait until the mod authors say they're ready, and not expect everyone to dance to your desired timelines for when community volunteers make free upgrades to software enhancing a game you get free upgrades for?

Nertea has set the Near Future mods as compatible only with 1.1.0 in their .version files, and CKAN is following that guideline.

If you mean CactEye-2 Orbital Telescope, the community fork is now available - 2.7.2 is the latest version. There are now two versions available for KSP 1.1, though Angel-125's fork is only up to 1.1.1

Should be available now.

KerBalloons v0.3.4 is now available.

Not sure which mod you're talking about. Can you provide a link to the forum thread / Spacedock / Github / Curse listing?

Yep. It is exactly the same for us too. CKAN sucks for the first couple of weeks after a new KSP release. Hasn't everyone figured that out, yet? But then, using a heavily modded KSP install without CKAN sucks after a new KSP release, too. That's the nature of mods on a changing runtime environment. And you want CKAN to magically sort this mess out for you? I'm astounded that you'd rather stuff up your KSP game with possibly-incompatible mods than just play stock for a couple of weeks to see what the new release is like. Here's an idea: rather than write your own CKAN-like utility, help us make CKAN better, by adding the features you want to it. Hell, fork it and make your own version of CKAN that works the way you want it to. CKAN is fully open source, you are most welcome to do so.

I took your post entirely seriously, went as far as creating a new branch on my local copy of the NetKAN metadata repository, opened the netkan file, and found no homepage entry there. I then looked at the spacedock page the netkan is pointing at, and saw that it was indeed created by stupid_chris. At that point, I was rather annoyed at stupid_chris' blaming us for a problem he created. I was also rather affronted at your tone, attacking us for something that had never been previously brought to our attention. Through all versions of KSP, CKAN is tracking over 1200 mods (admittedly, many of them are not active, but we need to keep aware that they may come back to life at any time). There are about three of us actively maintaining this information, and we try to be as responsive as we can in keeping metadata correct. I get that you were frustrated at a minor incorrect detail, but if you could dial back the accusative tone, you'd get politer responses.

Sorry, but the Spacedock entry was created by stupid_chris, and the Mod homepage: Forum Link on there is http://forum.kerbalspaceprogram.com/index.php?/topic/96464. No CKAN maintainer typed in that URL. We are simply grabbing the information stupid_chris makes available.

The KSPX homepage in CKAN is actually taken from the Spacedock page, so stupid_chris can fix it any time he chooses.