cantab

If you always keep any joysticks and controllers - and some gaming mice may count as such - plugged in then you should be fine. Otherwise you can fix it by editing the settings.cfg. Or more simply the F1 screenshot key works on the settings page so you can just screenshot your settings for reference.

It resets trim for me. I do recall one mod making X stop timewarp, might have been alarm clock or KER, but that didn't stop trim behaving. SAS doesn't have to be off to reset trim, but it does have to be off to SEE your trim setting. If SAS is on you'll instead see what its inputs are. Mechjeb may also be making control inputs from any of its myriad tools, so do check that.

If trial and error isn't an option, a trajectory prediction mod isn't an option, and a spaceplane isn't an option then the only other thing I can think of is a "stop and drop" landing as described by mhoram, where you kill your orbital speed and descend vertically. At Duna the delta-V cost should be manageable. At Laythe, Kerbin, or Eve it will be excessively high.

Sent my missions off to Jool and Titanus. Do you think I have enough landers? Also, stupid overheat bug. The trouble part is the chutes on the atmo landers, inside the fairings. Hopefully updating FAR will fix it.

Yeah, I got the flying while landed bug. I made a quicksave, edited the craft to be considered landed, and loaded it. But that might not help if you want to EVA a Kerbal around.

I think that's just being overpedantic. My understanding is that real rockets have their own control and guidance systems anyway, it's a bit of a KSP oddity being able to let one box of electronics control the whole mission. In fact KSP's 2.5m "reaction wheel" is clearly based on the Saturn V Instrument Unit that sat just above the third stage fuel tanks.

CaptainMoustache, since you mention RSS and RP-0, did you let CKAN install FAR? If so then either ask in the "FAR via CKAN" thread, or make a fresh install with only Procedural Wings and FAR both installed manually and see if the problem still occurs. Just to throw out an idea, could this be something that could be handed off to parts mod developers? Perhaps have FAR support an option in part configs that specifies how to handle voxelizing that part?

If you want an awesome alternative, stop the rescue ship in a hover near Jeb's position then switch to Jeb and have him jetpack to the rescue ship and board.

The concern is about RAID 0, which not only multiplies your risk of drive failure but can make data recovery in the event of a failure much more difficult.

Much as some might like to deny it, you're still playing KSP. The "proper place" is the same as always - General KSP Discussion for general chat, Gameplay Questions and Tutorials for help, Support (modded installs) for bugs, and so on. You might adopt an unofficial [Realism Overhaul] tag or similar if you like.

I sent a probe to Pergas and got a normal atmosphere curve, but that was a few versions ago for both K+ and Kopernicus. I know one of the Kopernicus releases did change the syntax for some of the "curve" things. For me Kopernicus 0.3.1, New Horizons 1.6.4, and Kerbol Plus 2.3.8 all loaded up together, though some of the K+ bodies were obviously bugged. I haven't checked extensively for things like terrain or atmosphere bugs.

Yeah, the empty nodes get filled by mod parts.

Download and unzip a clean copy of the game. A corrupted file is the most likely cause.

Your script doesn't work because even though the file manager just says "Home", the real path should be "/home/(your username)/.steam/steam/steamapps/common/Kerbal Space Program" At a guess, try changing your anti-aliasing settings - if it's on turn it off, if it's off turn it on.

I'm the other way, I generally do like having my rudder and my wheel steering on the same control, so that I don't need to switch controls or worry about which to use during takeoff and landing rolls.

I've yet to deliberately sacrifice a Kerbal but I've had my share of "the mission must go on" moments. In particular my grand Duna and Ike mission (with an asteroid in tow, no less) back in 0.23.5 had many mishaps, with both the Duna lander and the Ike lander crashing into Duna as well as a fatal accident on landing one of the crew return capsules at Kerbin. Playing without quickloads any Kerbal death is a blow, but I just had to pick myself up and carry on.

Lately I've just been letting the boosters scrape the paintwork if they have to. I tend to have quite a low TWR after booster separation so relative speeds are low, and if I need to I can reduce throttle until they're safely behind me.

Most amusing, probably when the rocket goes nowhere due to either insufficient thrust or a silly launch clamp in the top stage. Or the old parachute and engine in same stage on early career mode launches.

How's this for a simple and practical definition: The payload is the bit you can easily swap out. In the case of a rocket launcher that's simple. In the case of a spaceplane or shuttle the contents of the cargo bay are payload and the crew are payload; I'd list the real Shuttle as having a payload of 24.4 tonnes plus seven crewmembers. The orbiter or spaceplane itself though are not payload because you can't easily replace them with something else, at least not without it being reasonably considered a whole new launch system. And yes, a destination needs to be specified. The "default" is Low Kerbin Orbit though.

So for my first interplanetary trip in New Horizons I'm off to Jool! An unmanned mission with an orbiter that will drop ten separate landers. One each for Jool, Dres, Duna, Ike, and Nolas. Three for Leouch, an atmo lander for the canyon and both an atmo and vacuum ones for the highlands. And one each for Vix and Valit from Kerbol Plus. Launch: https://flic.kr/p/xLQSr7 And course set I entered a Kerbin orbit roughly in the plane of the ecliptic hoping that would help, not sure how useful it has been though, my transfer orbit has a strong inclination compared to Jool but I'll look at whether I can make a correction in Kerbin or Sonnah's SOI. No lander pics yet, because of the screenshot-spoiling overheat bug.

Launched the Coleridge 1, my grand autonomous expedition to the New Horizons Joolian system, with ten separate probe landers. Unfortunately I got hit by the crazy overheat bug, so no screenshots of the ship until I tediously go through the save and make the temperatures not infinite.

I think that's overpessimistic. Most components don't move on that quickly. The AMD FX range aren't expected to be replaced until spring next year and nVidia seem happy to let the 750 Ti and 950 coexist at different price points.

Heh, when I have that problem I just take my "Thrust SuperScienceCar" out and drive it up to one of the KSC buildings. Four Mat bays, four Goo, the science the Kerbal can get, plus whatever other instruments I have.