linuxgurugamer

Well, I beg to disagree. I pulled down the latest code for KEI from github. It was generating an exception, until I added the ex.experimentID != null && With this single change, the exceptions went away. The problem is that the experimentID is null, which is causing the exception. I'm puzzled as to why you are objecting to adding a simple check for a null value? The exception is happening in KEI, because of a part from L-Tech (the Skylab). I'm working on that side, but would like to respectfully request that you try this fix yourself, instead of blindly rejecting it. BTW, I just looked at the link you provided, and the code which was/is in KEI was NOT, repeat, NOT, checking for the ex.experimentID != null. It is checking to see if it is not an empty string, which is totally different from being null

New release: 1.1.6 Add support for Community Tech Tree -When Community Tech Tree is installed, the K2 Command Pod will be placed under the Simple Command Modules tech tree node. thanks @JonDahm

I just confirmed that [x]Science has a fix in place which checks for the experimentID being null. At this point, I'm not sure it's a bug in L-Tech

There is another mod I'm going to add as a recommended mod which would prevent that from happening: https://github.com/shadowmage45/KSPRescuePodFix

I found a small bug in KEI, related to the problem with L-Tech. It's a simple one-line fix. What's causing the nullrefs was a missing check for a null value at line 152. This is what it should be: if (ex.experimentID != null && ex.experimentID != "" && ex.experimentID != "SEP_SolarwindSpectrum" && ex.experimentID != "SEP_CCIDscan") I'll be doing a PR. This doesn't excuse a possible problem with L-Tech, but this is a bug in this mod, and took me about 15 minutes to find. I haven't seen the same issue with [x]Science, maybe it was fixed already there.

Ummm, I'm not sure what you are asking. Crew Transfer is blocked on purpose. It's not an internal space, it's external, therefore no crew transfer. This was a recent change.

I'm looking into this problem you had with L-tech. I installed L-Tech, KEI and [x]science, created a new save, did what this said to do, and am not getting any null refs at this time. Can you provide any more info? I'm testing on a 1.2.2 system, with the latest L-tech code Edit: Just got the null ref, so I can now debug

Ok, this is what you need to do: The Retractable Lifting Surface mod needs to be in it's own folder, with the .version file for it in the same place. I don't mind (actually encourage) you to include it, but you need to keep the folders the same The .version should be in the SHED directory You should make a release file. It's ok in this case if it's teh same as the source, but it needs to be added as the release file

@Kerbas_ad_astra Would it be ok to add this to CKAN?

Does it have a .version file? If not, that would be useful

@steedcrugeon I got a request to add this to CKAN, but need your permission first

That link also has the c# file The files I linked just now are what was on Kerbalstuff

https://github.com/BahamutoD/CritterCrawler And here are the files: https://www.dropbox.com/s/855v5kuw1g9po58/Bahamuto_Dynamics_Parts_pack-v1.2.0.zip?dl=1 https://www.dropbox.com/s/6ysk05j6kqtaprs/Bahamuto_Dynamics_Parts_pack_v1.1-v1.1.1a.zip?dl=1

I have all the old Kerbalstuff files, I'll get it for you

What @politas said. I had the problem. Specifically, the following is exactly what I did this morning. I would recommend backing up the KSP directory first: Start CKAN File->Export Installed Mods... (save to a known location) Uninstall ModuleManager (most likely will NOT uninstall the other mods at this time) Exit CKAN Start CKAN Refresh File->Install from .ckan... (select the file you saved earlier. Will most likely uninstall all the other mods which depend on MM now) File->Install from .ckan... (again, select the same file you saved earlier, will reinstall all missing mods)

Oh, so only for mods which are registered in CKAN.

And how is CKAN supposed to know how to update a mod which hasn't been registered in CKAN?

His points about the Castellated ports being more difficult makes a lot of sense

Ok, since I haven't heard about any other problems, I'll be releasing this later this evening as an official release

I'd really love that also. Are you willing to write the code? Seriously, I didn't write this, I'm only maintaining it. If someone would write the code, I'd gladly incorporate it

Sounds like you may not have ModuleManager installed. Please verify, then post a link to the log file

@politas I redid the netkan for HorizonAeronautics, https://github.com/KSP-CKAN/NetKAN/pull/5176 but the problem with the .version file is still there, although now it sees the .version file in another directory. Not sure to to ping on this, I just copied your comment from the previous message

That's kind of what I was expecting. I still have the directory backed up, so let me know if you'd like me to sent you anything from it (or the whole thing)

Very scary, but I didn't think about the Save As. When I did the install from .ckan, it first uninstalled everything that depended on MM, and only installed MM, so I had to do that a 2nd time. Might be an idea to put ths in the wiki? What I'm puzzled about is why it wasn't updating MM, even though it saw that there was a later version

@Delta_8930 Could you please fix the download file? It is causing problems