linuxgurugamer

New release, 2.0.5: Added toolbar button and window for controlling the Thrust Limiter New functionality Can change the following: All active engines All inactive engines All RCS and can also select specific engine types Remembers window position Added settings window

I still don't know why you are cc'ing me on these. None of these mods are mine, is there something specific that you want me for?

I'll look into this Sounds like a bug, will check it out I don't understand, please elaborate on this

new release, 1.3.7.2: Added the following to the per-vessel info: LaunchSequenceControl Initial throttle Final throttle Enable SAS at launch

New release, 1.3.7.1: Fixed bug where launch sequence item #10 was not being saved Fixed the enableSAS not being obeyed (was always being turned on) Renamed EngineControl to LaunchSequenceControl Made change so if LaunchSequenceControl is false, no stages will be activated and GravityTurn will not be called. Added the following to the per-vessel info: LaunchSequenceControl Initial throttle Final throttle Enable SAS at launch The per-vessel info additions were not released yet, sorry

It should

You need to use the latest Kopernicus for your version of KSP.

Thats the whole idea behind Vens. However, for some parts, he also changes some stats and diminsions. But it looks greak, I use it

Ill disagree, many times Ill see stuff in the output_log which isnt in the KSP.log

Would be nice to know what issues you are referring to.

Not an issue

Not causing an issue, but I thought I had taken care of that. I'll have to revisit it

can probably ignore it

Need a log file

Thanks for the update, glad you got it figured out

Your welcome

First, which mod are you talking about? This mod isn't mine, so I'm a bit puzzled as to why you are asking me about it. Second, if you ARE referring to this mod (Bluedog Design Bureau), then it IS compatible, but there haven't been any updates for a while, so the only listing for it in the CKAN meta data is for 1.4.3. However, it IS compatible with 1.4.2, so follow these steps to see it: In CKAN, go to the menu item: Settings->Compatible KSP Versions This will bring up a dialog where you can tell CKAN to show mods which are specifically compatible with other versions of KSP. In the center of the dialog, there is a place to enter new versions, it is labeled "Add version to list:" Enter 1.4.1 and click Add Enter 1.4.2 and click Add Enter 1.4.3 and click Add Now, in the list box, click the checkbox to the left of the versions you just entered and click Save Bluedog will now show up, along with some other mods which might have the same problem.

Welcome back. Please update the OP and the thread title to reflect the update. Feel free to call on me if you need help with an6 updates

New release, 1.3.7: Fixed hang after doing a launch with GT, on the next launch Swapped names of ToggleOff and ToggleOn methods to properly reflect the functionality Fixed saving of launch sequence Changed id from guid to vessel name for Sequences Now properly saves settings for each vessel, using the craftName before any modifications are made by other mods Added optional (but highly recommended) MM patch to support this. If MM not installed, then it uses the craftname on the pad

I need an icon which will fill the following requirements: Two sizes, 38x38 and 24x24, these are the sizes of the buttons on the stock and Blizzy toolbar Needs to convey the idea of a throttle, preferably a throttle limit Would be nice if it could indicate that it is a multiple (ie: the button works for multiple throttles) Also, this mod is under the GPL, so the icons need to be the same. Looking forward to all the great ideas I know are floating out there

The mass is 0.001 already

If that was so, then why do you have a bug fix coming up from my do you just released. The Mr. Clean mod, which you just released, and sounds interesting, seems to have some bugs. This is what I'm talking about. Not having looked at the code, it is possible that if some additional thought and development had been put into it those bugs would not have so another. Even if you had, then this simply goes to so that software development is not as simple as you made it out to be. This is not a personal attack, simply pointing out that software development is not as simple as it sounds like.

Agreed, but just spending a bit of time thinking the entire process through is usually a good idea. Just going ahead and implementing an idea usually isn't good. First, sometimes adding additional features, or just fleshing out existing ones may conflict with existing code. Second, those pesky edge cases are always a problem. Now, no one expects every edge case to be found beforehand, but, the more you can cover in advance with a bit of thinking, the better the user experience will be when using the mod

No, I don't see it in the .version files, at least none of the ones I'm aware of

Better "in yellow" than "yellow"