linuxgurugamer

You can try using Janitor's Closet, and block some mods in the VAB, or you can try using Filter Extensions

New release, 0.0.1.10 Fixed the settings not being passed to the flight scene from the editor Please report any issues. Due to the need to pass values from the Editor to the Flight scene, and the fact that there isn't any easy way to do this, the code is somewhat convoluted, and bugs can creep in unexpectedly.

Minor necro here: @Snark, would you like me to update CKAN for this? Right now it stops at 1.4.4 Also, a question about it's position in the tech tree. Since this is changing and reducing the stats, would it make sense to move it up one level in the tech tree?

New release, 0.1.6.11 Added a debugMode setting Changed most Log.info to Log.Debug to reduce log spam

That may be, but it's using standard KSP logic. If you are too far away from a docking port, you won't be able to target it.

I'm adding a debugMode, and most of those log lines will be dependent on the debugMode, so if debugMode is off, they won't write to the file. Should reduce the log spam by a significant amount

I have observed an issue where settings made in the Editor are not carrying over to the launch. Looks like one of the changes I made to fix a previous bug is causing this problem

Absolutely nothing, I didn't see it. Sorry. Not a big deal. You provided all necessary information to replicate it and I was able to fix it.

That is due to be changed in the next release.

That's what the OP says too

Last week I finished construction of my Space Camp space station. Designed to keep 12 Kerbals happy for 40 days, it includes a centrifuge and Emergency Escape Pods for all, as well as 15 tons of supplies.

No reason why it shouldn't. It works with whatever is the current target, doesn't matter what the target is.

First, a complete log file is needed. Second, do you have the dependencies installed? I just installed it on a fresh 1.4.5 install using CKAN, it works fine.

New release, 0.0.1.9 Fixed nullref which was causing an empty popup when toolbar buttons were disabled and the window was opened using the PAW menu Fixed resetting to default values for the following: ignoreAoAAboveAltitudeKm disableAtAltitudeKm Fixed default values not being set properly upon first run in Flight mode Fixed default values not being set properly upon first run in Editor mode Moved ResetToDefault() method into the AbortValues class to simplify code a bit

Found and fixed this. Would have been easier if you had provided a log file Took a while to realize that the AoA you were referring to was the disable at altitude. These are confirmed and fixed,will release later today

Congrats on the release

New release, 1.3.7.3 Fixed loading window positions

:-( And of course, right after I release, I found another bug. Probably best to wait a day for me to fix this. It seems to fail when a new vessel is launched.

That's not a fighter jet. It's a patch with a fighter jet on it

Thank you

It doesn't start watching the time until the vessel is launched.

If you edit the save file directly, maximums don't apply.

Ten thousand penguins, each in their own spaceplane? Mun, here I come

Is it safe to install this in a 1.4.3 game? I looked at the .version file, and it seems ok, just trying to confirm before I totally bork my install. Thanks

No, you can't, it's a limitation of the Settings methods. What you would have to do is to edit the save file and make those changes directly.