politas

I would suggest moving your Flags folder to be under SELV directly, rather than under Aura.

The License you list is "CC BY-SA-NC". Assuming you haven't created a new license, could you perhaps use the more standard "CC-BY-NC-SA" nomenclature?

I haven't updated to the latest version yet, but I've been getting a few stages that the SR dialog tells me are recovered without any notifications popping up for the recovered funds. The last one was a stage I separated from in atmo, after aerobraking below 2000m/s. It had sufficient parachutes to land safely, but stayed in physics bubble until I landed the capsule, and then just disappeared.

Well, for example, there's this mod and Procedural Airships that do very similar things. Can you use both of them? Can you mix and match parts of one with the other or use the control system from one to control the parts of the other? Would installing them both cause one or the other (or both) to not work? Is it laziness? Perhaps. But we're talking about mods for a game. Something that I do to enjoy myself. Time spent reading every detail of a mod's forum posts or readme file is time I'm not enjoying the game (or the mod). Some mods forum threads run to many hundreds of pages. How much time should a player spend reading through them in order to find every report of an incompatibility with some other mod they want to use? If I tried to read every forum post for the mods I use, I wouldn't have any time left to actually play KSP. Most mod authors do actually want people to use their mod. That's generally why they share them. The purpose of CKAN is to make using mods simpler and less frustrating. Now, some mods are easy to install and have few interactions with other parts of the system. Some, like say Renaissance Compilation or Astronomer's Pack, make use of facilities and plugins provided by other mod authors. Installing such a collection of mods in the wrong order can leave you with an unusable game. I've got no problem with people who choose not to use CKAN. That's fine, you can chase up all the details on your own if you want to. But for me, mods were a nightmare until I found CKAN, and they've been great ever since. For me, CKAN makes a modded game something I enjoy, while without it, I was tearing my hair out in frustration and throwing away complete game installs. So, like I said: for me, CKAN is indispensable. Oh, and by the way, saying "this is not to be rude" and then calling someone lazy? Sorry, but that is rude.

Here's the failed Pull Request from the KerbalStuff Bot, by the way. It seems your opt-out choice was not respected by KerbalStuff. It failed the test-bot checks because the mod name is not the same as the directory that gets installed.

Well, for those of us that use a lot of mods (I have 57 listed in CKAN for my current 1.0.2, and I'm running a fairly light install for me), it makes the whole process of keeping mods up to date and avoiding incompatibilities a whole lot easier. For instance, Hooligan Labs Airships requires Toolbar. I've set it as a dependency in the .netkan file I created, so anyone using CKAN will get Toolbar automatically installed if they choose to install Hooligan Labs Airships. There really is more to it than just copying over a single folder. If you insist, I will remove the file I created, and continue not using Hooligan Labs Airships, but I do hope you change your mind about this. I'm sure I'm not the only person who uses CKAN as their main source of mod info.

Can I ask why? As a user of many mods, I find CKAN indispensable. I actually stopped using Hooligan Labs Airships due to it not being on CKAN. I thought you'd come around on this, as the author listed by CKAN is your username.

You put it on KerbalStuff, which auto-generates metadata files for CKAN. But the file it submitted was wrong. I've submitted a new NETKAN file now which I believe will work. Why do you think permission is required? The mod is an MIT licence, and CKAN is only a metadata repository. It helps people install your mod, it doesn't make any copies or forks.

Ooh, so happy to seeyou've updated HL Airships! I think the NETKAN file needs to be updated, maybe? CKAN is only showing version 3.0.0 as the latest.

Well, bugger. I was hoping this would be a solution to the AMD Linux PNG lockup issue.

Wait, wait, wait, I just opened the img2dds Python program, and there's an exclusion for 'BoulderCo/'? But that's the only folder I want to convert, so my computer doesn't crash on me if I install EVE!

Haven't had it happen in 1.0 yet, but I always found docking mode a pain in the past. I only ever got into it accidentally, and I have never figured out the keyboard control to return to staging mode. Also, the settings don't allow you to re/unmap the docking mode toggle key.

Any chance you could add this to CKAN?

Still quite useful in 1.0.2: EDIT: Note that this screenshot is using v0.20, as V0.21 hasn't shown up on CKAN yet. - - - Updated - - - One question, in KSP 1.0+, many deployable parts are unable to be un-deployed. Should these panels land in that group, or should they be foldable?

I hope you can get the info you need to update this for the new stock aero. Are you also looking at NuFAR development? That's sounding pretty good.

A toolbar button for configuration would be great. Also, the CKAN info is lacking a homepage URL (this thread would be ideal).

Yep. Just tried that, and confirmed that the problem is somewhere between AMD drivers and PNG library. Opening certain EVE and Astronomer's Pack texture PNGs in image viewers (Image Magic and EOG) also freezes my desktop. IT's not an EVE or KSP bug. From some bug reports I've found, it sounds like there are certain optimisation methods used for PNGs that trigger the bug. Perhaps there's a solution there in re-encoding PNGs. If devs would like to try different PNG settings, I'm happy to help, as I am reliably getting the UI freeze when opening certain texture files. Send me a PM and we can work something out.

Ok, well I just proved that it isn't a problem in KSP itself. I was looking through the texture files in Eye of Gnome (default Ubuntu image viewer) and it locked up again.

This appears to have worked. I have successfully started KSP 1.0 with EVE installed!EDIT: Or perhaps not. Just crashed again on restarting. Here's my log if anyone can make sense of it.

There is never anything useful in the logs, and I don't have ATM installed (Why bother?) I have found on the Linux thread a fairly sane explanation of problems with AMD drivers. I'm going to try that. I think last time I tried that it killed my multi-monitor setup, though.

Can anyone give me a simple direction for what I need to fix? I'm running x64 KSP on Ubuntu Linux 14.04, and every time I try installing EVE, it crashes and locks up my computer when it gets to loading /BoulderCo/Clouds/Textures/kerbin1. I have to reset my computer to do anything. Clearly, this isn't affecting everybody, since there are loads of people talking about in-game issues under Linux, which I never get the chance to experience. I've searched and searched through the forums, and keep getting sucked down various rabbit holes. Help? Please?

Ahhhh! I would never have guessed. But that's broken, now?

Not sure if it was caused by Editor Extensions, but a craft I was building suddenly lost the ability to have any parts added or removed. Restarting KSP without Editor Extensions freed it up. (But restarting might have done so without uninstalling EditorExtensions, I really couldn't say) Edit: Nope, it's locked up again without Editor Extensions installed. No idea what's happening. Klakh, Vertical alignment didn't work in 0.90 either, surely?

I Already have the IVA set of Jeb, Bob and Bill. Just ordered a Stargazing - Small to take to work and Werner von Kerman. Really looking forward to adding Valentina to my collection some day.

The term "solar system" (lower case) can indeed be used to describe other planetary systems. "solor system" is definitely a typo, though.