Papa_Joe

I've had no word from the Original Author. Since the license allows it, I've completed the rewrite and have a build to test. I'll let everyone know soon. If needed I'll release with a new thread for the spacedock specific plugin.

Thanks. I updated the version and the server copy correctly but forgot the link on the distribution copy.....

Certainly Possible. I'll check it out. Thanks!

Ok, new release. release v1.2.0.2 * New: Added Changes to configurations based on conversations in forums and a Pull Requests by Technologicat, khr15714n & Kerbas-ad-astra. * Fixed: Correct build deploy automation to project (missing icons for blizzy). * Fixed: CLS tweakables incorrectly visible when custom passability is disabled. On SpaceDock and Github Looking forward to KSP 1.1. Soon now...

I've sent a PM to the author. I'm waiting on a response. If none, I'll create a replacement plugin for SpaceDock

yes. allow unrestricted is the setting I'm referring to crudely.

Indeed the mk 1 pod is impassable... there is a heatshield on the back... cant walk thru that... However, if you realy want this, then I'm guessing that if you enable Custom CLS configs, you can modify the design in the editor and enable passability for the pod. Check it out. this is explained in the wiki as well. Check out my sig. Additionally, in the CLS options menu, you can turn off cls and that will allow the stock transfer to work.

Still here and active. been playing since .7, before there was a sun. Been modding since .18

Anyone know if the author has been active? I could take this over and get it working again with SpaceDock...

That was an addition offered in a PR from jd284. I agree!

Thanks Technologicat for all your efforts here! I've merged this into the CLS Repository. I'm now going thru a couple of other pull requests from Kerbas_ad_astra & mwerle (back in 2015). No date yet, but soon.

This feature was requested way back around the beginning of this mod. At that time, PWB fuel balancer and TAC fuel balancer handled this (and still do). Given that the focus of my mod really centered around treating crew, science, and resources as "cargo", I named it Ship Manifest. Active fuel balancing is really a flight control feature to minimize imbalance, and to reduce fuel consumption. These features really do not align themselves with the "theme" of this mod. Having said that, I've recently added ship's control dasboards for accessories such as hatches, lights, solar panels, etc. So I'm not opposed to such a feature, but I'll have to consider the implications of it, (career mode, realism mode, whether to have it active by default "out of the box", etc.) Codepoet (author of Connected Living Space or CLS) wrote PWB fuel balancer; you may wish to look at that. I'm not sure if it is still working or not, but you can find it here: http://forum.kerbalspaceprogram.com/threads/42624

You can also take a look at a few mods that implement reflection apis such as DeepFreeze, ShipManifest, These should give you examples of how to do it.

Awesome! I'll be sure to correct that with the next release. Thanks!

Hey all, Back in action. SM had been released and nominally debugged, Roster Manager has been updated. Now to address CLS... I have some existing bugs to fix. I will be posting them in the Git Repository Issues area. If you have bugs that are not in the list, please add an issue for it. This way, I will stay on top of them and they won't get forgottten. I'll begin going over the various conversations governing the configuration files, and get a quick release out to resolve any glaring bugs. JPLRepo and I also found some bugs when testing between DeepFreeze and ShipManifest. The big one is a cls bug in a failed crew swap that causes dup or missing kerbals. This may be the one that has been haunting SM and CLS for months... I'll also lookover the proposed changes to the configs and build that PR being discussed. Thanks for all the feedback!

Sorry for the delay on this. I've finally found a bit of time to get this released. JPLRepo has added a nice feature with Notes in the records tab. you have 2k to express yourself on each kerbal. Persists with the game save. New Release: Version 0.2.1.0 15 Mar 2016 - Fix issue with Loading/Saving causing errors at space centre. - Fix issue when Kerbals are sacked. - Changed DeepFreeze Integration to use new DeepFreeze wrapper API (no more hard dependency on specific versions). - Added Notes function. There is now one Notes area for each kerbal (2k characters max) to record whatever notes you wish, accessed by selecting a kerbal in RM and selecting the Records tab.

With the release of 5.0.1.0, I'd like get a better handle on what remains to be resolved. If you have been experiencing a bug, and you have posted it to this thread, but it has not yet been fixed, please create an issue in Github (link is in my OP). This will ensure it does not get lost in the ongoing conversation and ensures that I will address it. I will be going thru the thread and extracting the issues I see. Please check to see If I or someone else has created an issue before opening a new one. Thanks! Update: I've added several issues to the Github repository. I hope I've captured all of them. Please let me know if I've missed anything. Link: https://github.com/PapaJoesSoup/ShipManifest/issues thanks!

Released Version 5.0.1.0 - Release 14 Mar, 2016 - Bug fixes and APIs - New: Removed DFInterface.dll. Added Reflection based Wrapper class source code for integration with DeepFreeze. - New: Removed SMInterface.dll. Replaced by SMWrapper, which is also a reflection based wrapper for developer use with SM. - Fixed: Crew movement issues with DeepFreeze. - Fixed: Roster Window does not display correctly with DeepFreeze installed. - Fixed: EVA kerbals causing a null ref bug and duplicating kerbals. This fix requires the latest version of Deepfreeze (V0.20.4.0) if you use it with SM. DeepFreeze will be released within the hour.

New release coming within the hour. Due to the nature of the update, JPLRepo and I are coordinating releases to ensure maximum compatibility during this update. DeepFreeze has been updated as well. We have completely revised the way we communicate with eachother. hopefully this will improve things going forward. For those that care, we are now using similar reflection classes as in ToolBar and many other mods. Change Log for impending Release: Version 5.0.1.0 - Release 14 Mar, 2016 - Bug fixes and APIs - New: Removed DFInterface.dll. Added Reflection based Wrapper class source code for integration with DeepFreeze. - New: Removed SMInterface.dll. Replaced by SMWrapper, which is also a reflection based wrapper for developer use with SM. - Fixed: Crew movement issues with DeepFreeze. - Fixed: Roster Window does not display correctly with DeepFreeze installed. - Note: The latest version of DeepFreeze (DF) is required if you use it with SM. - Note: EVA kerbals causing a null ref bug and duplicating kerbals. This fix also requires the latest version of Deepfreeze (V0.20.4.0)

thanks. that helps

This is the original post That I"m referring to above....

I'm looking at this now, and I'd like to ask: Do the kerbal inventories move when a kerbal is transferred and not swapped? Meaning. only when they swap is the issue coming up, or are no inventories moving? thanks!

In SM, I had not programmed the the Tourist profession. I've since added it it. Let me know if this resolves your issue or if you are still experiencing it. After the major refactor of ver 5, I'm not sure what bugs will still be there or what new bugs I may have introduced with version 5. As I'm getting closer to release of 5.0.1.0, I'm going thru the forum thread to make sure I've not missed anything. If I have not addressed your concerns please speak up again. Thanks!

We have a fix We have a fix. I'm packaging it now. One of the changes is the removal of the SMInterface.dll file. DeepFreeze will soon be released with a new wrapper class to access features of SM. This corrects the error, as we have removed the need to keep track of the namespace, I'm also looking over other bugs recently posted to be sure I've addressed those as well.

JPLRepo and I are investigating. I believe we have found the culprit. It appears I renamed a class namespace without updating the Interface. Working out a solution now.