Prezombie

The problem is, the 15 day "grace period" for EC is massive compared to how much EC you can reasonably fit onto an early ship (at most a few hours). If you don't forcefully disable batteries, any manned mission more ambitious than suborbital becomes unreasonably difficult due to EC drain making reaction wheels and radiators unusable until you manage to research solar panels. And it's thematically weird that you can't lock away supplies from them, but you can lock away EC from them. An easy fix would be to have kerbals start to drain that much after a few days in space. (First few days, being in space is awesome. After that they start to get bored and start watching reruns of Everybody Loves Kerman). This way, early Munar/Minmus missions don't have the huge "I have no power for reaction wheels" problem.

I think the default EC consumption needs to be dialed way down. Currently it's at 0.01/sec, which is nothing once you have solar panels, but can be crippling in the early game between part limits and batteries having small capacities. With the default rates, you're effectively limited to short orbital flights until you've unlocked solar panels, Alternatively, how about making it easier to frontload the grace time of having no EC? In effect, give each kerbal a personal resource container filled with a few days worth of noms and EC which they consume first before going after the ship supplies, so early missions aren't left with no power for the reaction wheel.

Really? A video which just reads out points from a week old post is now Daily Kerbal worthy? Is this really the best KSP video from this week you could find?

The only other mod affecting timewarp is BetterTimeWarp. I haven't actually changed any of the settings in that mod, just installed it for the lossless physics warp. Edit: huh. The default setting for BTW uses the orbital warp increments rather than the KSC increments when looking at the KSC. I guess that's resolved.

Ah, no. I was using Astronomer's pack, but I removed it when I was trying to bring up my framerate. Which of course was the problem all along, because this mod just puts other cloud makers onto OPM, not its own. *headdesk* In my derpy defense, CKAN doesn't actually say it depends on having a cloud maker already installed.

When you open it in the hanger and pick a dictionary, it shows a few random names. clicking one changes the name right away. The prefixes are common acronyms used by military/exploratory ships by different countries.

Been made already, RemoteTech - Probe control enabler. in CKAN or https://github.com/Felger/FelgerFixes/releases

After updating this morning to 1.8.1, I got a bunch of MM errors. I dug this out of the output log. It repeats 39 times. [ModuleManager] Applying node OPMClouds/ModDeleter/@CLOUD_LAYER_PACK:HAS[#CloudsPack [*],#OPMClouds [*]] to OPMClouds/Auroras/OPM-AVG-Auroras/CLOUD_LAYER_PACK (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) [ModuleManager] Error - Cannot parse variable search when editing key CloudsPack = #$@CLOUD_LAYER_PACK[MainCloudsPack]/CloudsPack$

With Ven's and RealChute, the mk16 parachute has no staging icon, and always tries to deploy on launch. oddly, this is only an issue with the mk16 parachute, all the other stock chutes and the ones added by RC work just fine. Removing the top and bottom of the maintenance bays is just ugly, and makes it impossible to properly store items inside protected from the heat.

Did you double check your action group setup? Have you added any other mods lately? Does the action group run if you uninstall RT?

Nice little mod, but for some reason if you visit the VAB multiple times, this plugin adds an extra icon in the toolbar, once for each time you've visited. This sounds like a bad idea.

the KCT settings shows max time warp of 10k x. I can change it as normal, but 10k is the max. And it's not a nearby deadline issue, it caps out at 10k even when the next build is a month away. While you're at it, a button in the build-simulate-cancel menu to automatically warp through the building and rollout time, jumping right to the pad, would be a wonderful anti-grind measure for when the player doesn't have any need to do any parallel missions. It's also kind of odd how VAB to launchpad has a rollout time, but SPH to runway doesn't have a taxiing out time.

I love this mod. I'd love to see an option to automatically add generation marks to the end, and increment with each launch, so you can save the ship with the name xyz, but then launches as the xyz mark 1, or the xyz mk IV, etc. A small field to put in a string to append to the end of the ship upon launch would be great, along with simple variables for arabic or roman numeral counting or spelled numbers.

https://github.com/KSP-CKAN/CKAN/wiki/Adding-a-mod-to-the-CKAN Since you removed the mods from KerbalStuff, you need to manually submit a push request using the Github guide.

One tweak that I've wanted for a while since I tried then dropped BTSM is the lower bound on the flyinglow situation. It's absurd to get extra science by simply bouncing the rover into the air a tiny bit. Just a hundred meters above the surface should be enough. To force the use of something that actually flies without significantly shrinking the flyinglow situation's volume. If it's possible, it would be even better to make the science for flyinglow require the kerbal/vehicle to be airborne for at least ten seconds. Gathering in the air on the way down would always be valid, and it would make the rover designs ever so much more interesting.