AlexanderB

My bad, I cut my post a little short. I meant to say, depending on entry angle, speed and craft drag, its easily possible to stay above safe parachute speed all the way down to sea level. I try to build my entry-vehicles so they slow down to safe speeds at around 5k altitude, and set my parachutes to open at 0.34 (about 5k on kerbin), so even if I accidentally triger my parachutes in space, I should land safely. Should... However, some mountains are taller than that. :X

Depending on entry angle, mountains will certainly kill you, as its easily possible to go beyond parachute speeds, unless you fit airbrakes or drogues or some other way to slow down more.

yes, as in, it isn't solved? Because it isn't, turning on the drills and forgetting the ISRU completely drained an asteroid for me.

A certain 'D. Kerman' that got his name censored from the name generator.

That might work, I don't know. True, usually the command pod blew up too, but it was possible if you smacked it into the ground just right, not hard enough to break it, but hard enough to kill one or more of the kerbals inside.

Just looked it up, the code is still in the game, but there is no real easy way to trigger it, you have to somehow kill the crew without breaking the command pod first.

In the really old versions of KSP it was possible to K.I.A. your Kerbals without actually destroying the pod itself. They took that out of the game though, I think.

Running any kind of video capture software? the F1 and F2 keys aren't 'shared' in some way, like FN keys or something?

Yeah, that one.

If you really want more FPS, you can do some things though. -Tweak the water (and possibly surface) level of detail, if you're really scraping the bottom of the barrel gpu-wise this could certainly help in some situations. -Tweak the minimum physics timestep, if the CPU/parts count is holding you back, this might help. (basically, it slows down game-time (orange or red counter) instead of/before bogging down the FPS into single digits if there is too much stuff going on for the CPU to keep up.) -Overclock your CPU if you have the know-how to do it. Other than that, I think most mods have been named, here is my list: -KER, I need my dV readout to build stuff. The info windows while in flight are also quite useful. -Kerbal Alarm Clock, set notifications for planned maneuver nodes and other events, so you can timewarp without forgetting that other craft that needed attention. Also includes interplanetary transfer window help, real useful stuff. -change the CONIC_PATCH_LIMIT in the settings.cfg to something more than 3 (I have 6) so you can plan ahead of SOI changes better. -Planetshine, makes it a lot easier to see what you're doing in the shade/at night if you can turn the vacuum brightness up a little. Haven't installed, but certainly considering: -KAS, pick and place (small) parts outside of the VAB, place fuel lines between nearby vessels, etc.. Neat stuff, adds a whole lot of EVA dynamics (repairing stuff by bringing up actual spare parts and putting them on in EVA, running a fuel line instead of docking, etc..) -KIS, would go together with KAS, or so I heard. Haven't looked into it. -KOS, I'm also a programmer, so automating certain things is certainly something I could/would do, and it certainly adds options beyond my wildest imagination. It does bug me that it seems to use different syntax than what I'm used to, but I'm still willing to give it a try some time. -Mod to allow time travel to control both/all parts of a multi ship mission 'simultaneously'. I forgot what it was called though, but if you want to drop your space rocket from a plane, and then land the plane safely too, that would be the best mod to have I think. As you can see, I don't really bother with parts' mods, I already have plenty of work getting of use most/all the stock parts, let alone if there is a bunch extra. I did add parts in the past, but a lot (mk2 spaceplane parts, resource mining, fairings) is now in stock KSP. Oh, and a lot of mods start with the word Kerbal and have a 3 letter acronym, so that might be confusing sometimes.

Heh, so sarcastic.

Its really easy to completely run out of ablator that way, the trick might be to not go too high, and re-try a bunch of times until you have as little as possible left over on landing.

-(Accidental) modification of the key mapping, probably the most likely option. I'd check that out first. -Running some other software in the background that captures those keys. (unlikely, but possible) -???

Not even sure thats real 3d, does enabling Aero work? I just had a look at it, It should be possible to get some form of 3D acceleration in Virtualbox, under settings, display tab, tick the "enable 3d accerlation" box, max out the graphics memory slider to 128 MB, and then maybe, maybe it'll run KSP. But I highly doubt it.

Pretty sure virtualbox doesn't pass though 3d video in any way shape or form, it emulates a 2d-only card with 16 mb video ram.