bawr

I've just started playing KSP again, so... I'll check, and update if needed.

Because Dwarf Fortress doesn't let me build rockets. Yet.

Certainly. Just watch the new thread I linked earlier, and give it a day or two.

Okay, now that this is done, any other tweaks I can offer? Aside for the landing gear thing, already working on that.

This mod moves to the pack thread: http://forum.kerbalspaceprogram.com/threads/80951-KSPStockTweaks-things-that-(supposedly)-should-have-been-stock

And so we come to version 1.2: http://forum.kerbalspaceprogram.com/threads/80951-KSPStockTweaks-things-that-(supposedly)-should-have-been-stock

By popular demand, in public domain. Download link: KSPStockTweaks v1.2 Included tweaks: FlightDefFreeCam - sets the free camera as the default; FlightDefPrecision - sets precise / caps lock controls as the default; MapShowNavBall - shows navball on the map by default; JoystickPrecision - makes precision toggle apply to control axes; When precision controls are enabled with [Caps Lock], joystick axes are scaled down by a half. Which means that you get double the precision, with half the control range. For example, even when you tilt your joystick all the way up, pitch only goes to half the meter.

I agree in principle, although I intend to provide them as standalone versions for people to mix and match simply, and because the tiny versions serve as a useful, if short, code examples for starting modders (like myself). As Don Knuth said, premature optimization is the root of all evil. More seriously though, the default page size is like 4kB almost everywhere, so... even if I make a thousand of those, that's still under 4MB of "wasted" memory. And if you take a look, both of my current mods are exactly 4kB in size.

The plugin is great, but I have two minor issues with RC2. 1. I tried to merge NASA parts with the Squad parts and failed miserably, alt-click on NASA and then alt-click on Squad does nothing. 2. NLua references another version of KopiLua than the one provided in the package, not sure if it's an actual issue or not, but it makes compiling impossible if KopiLua is added as a reference, even though it doesn't need to be.

There's another lovely idea - specifying the limit by TWR, not by thrust percentage. I'll see what I can do.

Not difficult at all - monitor this thread, I'll make a single page for all such small tweaks and link it here.

I'm not sure how I could do that, but if you could point me in the right direction, I'd be happy to catch a precision toggle event instead.

Spot on. I've been having the same impression and I created this as a quick fix before I figure out a proper way of doing things. I've been thinking about that and I don't see a clean way of handling the issue... yet. One idea is to roll my own "select axis / button" window, which would be a pain, but should be doable. Only I really don't want to do much, if any, GUI stuff. Another idea is to use stock KSP controls, dynamically unbind them (yeah, fun all around, but at least I get the KSP binding GUI), and basically roll my own replacement for control axes. Under that scheme you'd bind your staging axes as usual, except in the actual game we'd use "throttle (incremental)" axis and *secondary* throttle up / down keys to control precision/scaling of the control axes instead. I'm not sure what you mean here - would you like to use the same scheme as for the control axes? Limiting the max value, but increasing the precision? That's what I'd like ideally, but it won't happen soon. Version 2.0, ideally.

That's on my list, too. I was hoping not to do any GUI for now, since this is my second KSP plugin, the other one to show navball on the map also has like 25 lines total... but I see I just have to learn faster.

Actually, I'm looking into that as well, for the same reason. I'll post here if I figure something out.