linuxgurugamer

No, I've suspended development as it wasn't going well

New release, 0.0.1.11: Removed all usage of the escape key

Is the OP up-to-date in the descriptions and bugs/issues?

New release, 1.1.6: Added a check to see if the vessel speed is >10 m/s, if so, no emissions. This includes being in Orbit Added an alwaysOn flag which can be toggled in the editor. If enabled, vapor will always be on at speeds <= 10 m/s New release addresses the problem. No way to have vapors in orbit at this time, so it's disabled for speeds >10m/s

A picture or a better description would be nice, I don't have time to test every single "try this" post in the forums.

Reentry effects is the mod

Far left field, I'm sorry to say. It's not a config change it's a code change. You could try recompiling for 1.2.2, unfortunately I don't have any time to do it right now. Sorry

FYI, in the next release of this, there will be a patch installable via PatchManager to install this patch.

I've put this into the Enhancement list for the next release, thank.

Oh, I didn't realize you had bloc numbers already. I would suggest that you use something like: <<launchNumber>> and <<blocNumber>> or [launchNumber] & [blocNumber] Internally you should use the format string, but maybe have an easy mode where there are a few standard format strings to select from.

Look at the settings page, you shouldn't need to change a config. Not that common, really depends on the settings.

Did you do that in a MM patch or a direct edit? If a MM patch, could you send it to me please?

Looks good

Thanks. I've updated CKAN, it should now allow both in a 1.2.2 install

Why not use a very simple template, something like this: anytexhere<<#>>anytexthere Where you would replace the <<#>> with the number. The first would be how many leading zeros to put there. So for example: STS-<<0>> Would generate names like: STS-1 STS-2 etc. and: STS-<<1>> would generate names like: STS-01 STS-02 etc You could get fancy and start having two numbers, the first number being the major number, and use the minor number for variants. But that may be getting too far beyond what you want to do, cause then you have to start figuring out how to determine variants.

Well, try reading my signature to start. Here, I'll help you: Read this BEFORE asking for support: http://forum.kerbalspaceprogram.com/index.php?/topic/83212-how-to-get-support-read-first/

Not caused by my actions, but I did the Retro Solar Orbit rescue challenge in 99 days, using life support. Rescue ship had about 60,000 m/sec dV , the first if the two launch vehicles weighed over 20,000 tons

Ill update the OP today

That would have affected many mods, not just this one. thanks

Ok, so here is your problem: This is from the file: title = #autoLOC_500445 //#autoLOC_500445 = RE-M3 "Mainsail" Liquid Fuel Engine manufacturer = #autoLOC_501637 //#autoLOC_501637 = Rockomax Conglomerate description = #autoLOC_500446 //#autoLOC_500446 = A monster of an engine for heavy lifting purposes, the Mainsail's power rivals that of entire small nations. Anything following the two slashes is a comment. So what is really there is: title = #autoLOC_500445 manufacturer = #autoLOC_501637 description = #autoLOC_500446 Those strange autoLOC tags are localization tags, and reference strings elsewhere What you want to do is this: title = My Title Here manufacturer = My Manufacturer description = This is my new description Why did you say this? This is someone trying to be creative, and is using this part to learn. Change the values as I described will not hurt the game at all

I'm on mobile right now, I'll take a look when I get home.

Probably localization at work

Well, there's a problem. KCT isn't listed on CKAN as being available for 1.3 I've contacted @magico13 about it

New release, 0.6.10: Added Kerbal Kooperative Union, thanks @mrcarrot Reduced height of buttons in gov sel window from 30 to 25