Papa_Joe

Just an update. I've not forgotten this mod. I have one editor issue to work out, and a release will be forthcoming. Showing and hiding the COM ball is wonky at the moment. should be an easy fix.

I am in fact in the code for CLS now. late changes to KSP 1.2 (like the very last PR build), broke CLS bad. So, I'm trying to refactor the "magic" that was used for so long that no longer works. Maybe a MM config will do it, but not sure. CodePoet was working with Prefabs in the editor and in flight. he was actually modifying these things every fixed update. All this to support hatches. Stay tooned. I had some RL things interfering with my mod work, but I am working it actively now.

I am in fact in the code for CLS now. late changes to KSP1.2 (like the very last PR build), broke CLS bad. So, I'm trying to refactor the "magic" that was used for so long that no longer works. Maybe a MM config will do it, but not sure. CodePoet was working with Prefabs in the editor and in flight. he was actually modifying these things every fixed update. All this to support hatches.

New release. Version 5.1.3.1 - Release 15 Nov 2016 - KSP 1.2.1 Compatibility Edition - Fixed: Create Kerbal fails. - Fixed: Rename Kerbal changes do not show up after change. - Fixed: Removed Mod Button from Settings Window. Was there in error. Enjoy.

Hey everyone. Thanks for the feedback. Here is where i'm at. 1. Mod button. This is a bug. I have now removed it. This functionality is available in stock now. I will include this fix in the next point release. 2. Kerbal renaming and creation. I'm working on getting the changes properly registered with the game. This was part of the late changes to 1.2 Also will be in the next point release. 3. Kerbal Respawn. Looking at this now. I think it is also related to the roster registration process now needed. Also will be in the next point release. Working on them now folks. Keep the feedback coming!

You should not even have a mods tab anymore... I know I don't have one on my build... I will investigate... I removed the mod tab as it is redundant with KSP's built in assembly viewer So where is this Mods option you speak of?

Thanks for the feedback and the log... I will take a look and get it corrected. Thanks! Good to see you back as well!

New release: Version 5.1.3.0 - Release 14 Nov 2016 - KSP 1.2.1 Compatibility Edition - New: Refactored mod for KSP 1.2.x Compatibility - New: Added support for new events in Crew Transfer, allowing improved performance and customization of Full Part messages during Stock Crew Transfers. - New: Corrected supported versions in the Developer Notes and Installation Notes. (Git Issue #30) - New: Added support for switching "Allowing Unrestricted Crew Transfers" in CLS so that SM and CLS do not compete for control over Stock Transfers. - New: Added a setting in the Settings window to enable/disable overriding CLS CrewTransfer setting. - Removed: Mods Tab in Control Window. Installed mods is now availabe from the KSP Debug window (Alt F12) - Fixed: SM windows were not always closing on scene changes. - Fixed: Resource Dumps from the Manifest window would cause any previously clicked dump to initiate when another was clicked. Science is not well tested. Let me know if there are issues. CLS and PWB Fuel Balancer follow soon.

Hey all, I've been slammed by RL. I am back. Sorry for the delay. I will have a release out tonight. I've tested and looks good. So expect in the next couple of hours.

I ran into this while working with SM and CLS. This used to be a field and is now a property. therefore a recompile is needed for what ever mod is using this object.

Do i use MJ? Yes. End of discussion.

Lol. "Is it Soup yet?" There is a reason I called my Git Repository Papa Joe's Soup.... I'm working thru it folks. I'll have a release soon. along with CLS, PWB fuel Balancer, and the BDA suite of mods... Sigh, a modder's work is NEVER done...

Please refer to the post JUST before yours. That is all.

Hi! Welcome to the Forums! As with all modded install issues, a little (or a lot) information goes a long way. Please refer to this post: It will provide you (and us) the information needed to properly troubleshoot your issue... If you read it (completely) and follow the steps, you may even solve your issue yourself!

Normally I don't like to "dive" into controversies about these things, but given that I've expressed an opinion, and, given that you have explained that you do not understand what I mean, and that I'm simply" resorting to cliches" as it were, I feel that it would be reasonable to explain. This may be TLDR to you, but I don't like to be misunderstood, and it is incumbent on the speaker (me) to make sure the receiver (you) understands. First, no one here is in the position of "defending" squad's poorly implemented console releases. I'm not here to dissuade you from your "righteous indignation" or your general feelings about squad or the ports to console. I'm merely explaining that it is very obvious from the posts that squad has made that they "blew it", they know it and they are working to make it right. I do not claim to have any inside knowledge of where they are in that process, nor do I claim to be a console user. Second. I'm a software engineer by trade, and have a quite few years of development experience under my belt. I don't claim to be a "leader in my field", but I know how to get the job done, and done well. I have watched squad since when they were a "garage" operation to the company they have become. I've seen many ups and downs. I've seen good and bad. I could have chosen to "complain" about the bad things, but I held my tongue. The reason? It adds no value to the conversation, and does not solve the problems that Squad faced. Instead, I did what little I could to "teach" the community about software development and to understand the process a little better. Third. I build Mods. I've been doing it since 2013 (0.22), and will likely continue to do so for the "foreseeable" future. during that time I've seen some really stupid things done in code, and I've seen some brilliant things. It is what it is. I have to work around those "stupid things" to get my mods to work, and usually I can find a way. This is how I am part of the solution with KSP. Fourth, with regards to consoles. they are broke bad. This is fact, and no one is arguing this. Even Squad. Squad knows, and is working on a fix for these issues. I do know this from what little interaction I had with other modders, who were also once devs. Unfortunately, as has been explained before, there is a very rigid process that must be followed for EACH Console vendor (Certification), and it is VERY expensive (more than what you paid for the console version of the game, IF you did). Because it is so expensive, a game vendor does NOT go to get a patch out for every little fix created piecemeal. You do it when you are reasonably sure that the code is ready. NOT before. SInce KSP 1.2 PC version is now released, I'm certain that process is now ongoing in earnest. No one wants consoles to succeed more than Squad. You can be sure of that. Finally, we come to how you can add value to the conversation and be part of the solution. I don't know if you have taken these steps, so please forgive me if I've stated things here that you have already done. 1. You can submit bug reports, following the procedures laid out by Squad on the issues you have found within the console release of the game. Be detailed, and provide saves, logs (are they available on the consoles?), steps to reproduce, and as much information on the circumstances of the issue as you possibly can. 2. You can share your experiences with other players, eliciting information on the circumstances of the bugs in order to aid the developers in locating and resolving the bugs. 3. You can monitor the bug tracking system, to ensure that all known bugs have been identified and are being worked. if they are not, you can inquire on their status in the bug tracker. 4. You start a thread that explores ways to "work around" existing bugs, in an effort to make the games more playable in their current state. I do not know how much value this could add, as I don't play the consoles, but it may. 5. If the above are not your cup of tea, you can ask for your money back. I don't know that process, but that is by far the loudest statement of your displeasure you can make. Put your money where your mouth is. If you stayed with me so far, I hope this helps to understand. I have learned by experience that, in general, being angry and complaining about a problem does not solve it, and usually causes others to stop listening. As a result, it contributes to making the problems actually take longer to solve, as time and effort is wasted on the noise. By all means, make your opinion known. This is important. but I feel there is no added value in repeating that opinion numerous times. In closing, I've read that there are those that would like to start "movements" to make the world know how bad the consoles are. That is of course your right. But, consider this: If you do, you contribute to the destruction of Squad. Is that how you wish to add value?

I would tend to agree. In my simple view, a person has a choice: either to be "part of the problem", or "part of the solution" I choose the latter.

First, welcome to the forums! Second, there is a sticky that describes how to get support in the forum where you created this thread. Third, in that sticky it describes placing mods in the game data folder. NOT the gamedata/squad folder. Squad treats it stuff just like a mod, so they have a folder of their own. Read that sticky post an all your answers lie there!

First, MM 2.7.1 is for KSP 1.2 You will want to go to a version earlier than 2.7.0.

With that said, build 1574 dropped late last night. Check out the change log here:

I have not tested this, but I have a theory. You can specify colors using <color> in the string you pass to the field. It may be possible to use <font> as well... give it a try...

" Fact: Enthusiasts do not tend to leave the development of something they are enthusiastic about mere weeks after joining it. " This would be opinion. While the likelihood is good that it could be fact, it is not in fact, fact.

Thank you kind sir. Now to get CLS working.

Time will tell...

Obviously, this was NOT a very good lie....

This ^^^^ Is what I'm referring to in my response. Sorry for the double post.. I expected them to merge