cantab

This only really applies for a rocket designed to take advantage of using all its engines by using lighter lower-thrust engines.In fact, the following two scenarios have the same delta-V: First stage of two FL-T800 tanks and two LV-T45s. Second stage of one FL-T800 tank and one LV-T45. Asparagus staging with a core and two boosters, each one FL-T800 tank and one LV-T45.

Wrong scale. As mentioned, even Gilly is so massive that the stock parts in feasible quantities would have a negligible effect on its orbit.

Yeah, I think Starwhip's got that.

I wish people would stop making wishes.

Granted, because Napoleon conquered Russia and all Europe, the Cold War was between France and the USA, and now people make jokes about American soldiers surrendering while the French Navy has ten aircraft carriers. I wish that comet Siding Spring had hit Mars.

Granted. They are 0.625 m across and just will not work with Tweakscale or any other resizing methods. I wish Kerbals walked faster. I mean seriously, they go at like 0.1 mpg.

Out of sequence, but I feel obliged to corrupt it anyway: Granted, but the method doesn't work.As for Squad, granted. They have the power to make addictive science-based video games. I wish the person after next would wish for a biscuit.

Were you trying to launch your own VAB?

Controlling a 1.25 m stack, the applicable RGU. Controlling a 2.5 m or bigger stack, either an octo2 or a qbe mounted on a cubic octagonal strut, the big RGU is too heavy IMHO. The qbe masses the same as an RTG, which is the main reason I pick it. If I think it's gonna be whacked, the QBE, since it's sturdier. For a small probe, whatever I think looks good.

Watched Scott Manley's where he discusses FAR, then installed it and made a working plane in it . Though I admit I wimped out and turned off aerodynamic failures.Now to try some rockets.

Granted. They touch your hair with sledgehammers, rather too hard. I wish for snacks.

No Alt+F12 here Sun.

No pictures, but slamming into Kerbin's atmosphere sideways because the timewarp caught me out was a Bad Idea. Snapped the capsule section clean off the rest of the ship. In stock aero mind you.

The issue in interstellar was plant disease, or "blight". Which presumably cannot be effectively treated. The whole blight producing nitrogen thing seems really iffy though. I don't think they got a decent biologist to advise them like they got a decent physicist.

Near Future has some giant solar panels, and also a set of ~2.5m trusses. In stock, the Shuttle SRBs are the longest single part, so I used them as beams to build a big station while keeping the part count down.

Granted. But they were made by Dobby, and thus don't match. I wish I could make my mind up.

I don't really want to be doing aftermarket cooling on the graphics card. Sure, it's possible, but I doubt it's worth the effort and cost on a budget card.

On Ubuntu I would install the proprietary graphics drivers using a package manager. Or one could use the "Additional Drivers" utility or similar. I've not used Mint, but it's based on Ubuntu so I expect it works the same way. At most, you might have to add or enable a repository for the proprietary drivers. It sounds like you tried to do things an unnecessarily complicated way. Unfortunately instructions for doing things an unnecessarily complicated way aren't uncommon. As for the dependency issue you encountered before on Manjaro, system libraries come in both 32-bit and 64-bit versions. My guess is that that you simply didn't have some of the 32-bit libraries installed. You'll probably find the same on Ubuntu - in general a 64-bit Linux distribution isn't going to pull in a load of legacy baggage needlessly, and the OS doesn't know you have KSP until you try to run it. How to install the 32-bit libraries varies, but on Ubuntu and I expect Mint they will have the same name but followed by :i386, you may need to search for them explicitly in a package manager or can install them from the command line with apt-get.

The short question: Which 750 Ti should I get if I want good value and quiet operation, and ideally to run two VGA monitors from it? The detail: Games of particular interest are KSP (dur) and the Total War series, but I want to be able to handle most games OK, which for me is a steady(ish) 30 fps at 1080p on non-cruddy detail settings. My current gpu struggles to do that on KSP and 2006's Medieval II: Total War. My main OS is Ubuntu 14.04, with Windows 8 for the Windows-only games. Unless a cheaper card can meet my wants, I'm planning on getting a 750 Ti. It's at the top end of what I'm willing to spend and won't draw too much power. AMD cards tend to underperform on Linux so I'm mainly looking at nVidia. "750 Ti" was the easy bit though. Which 750 Ti is where I'm really stumped. As said I want good value (dur) and quiet operation. I currently use a pair of VGA monitors and though it's not critical it would make life easier to keep using them. My current card is fanless and gets toasty so I don't think another fanless card is a good idea. Absolute fastest-possible-overclock isn't what I'm after though obviously extra speed is A Good Thing. Phenom II X3 710. 4 GB DDR2. Nvidia GT 610. 400W PSU with 1 PCI-E 6-pin connector. Space for a full-height two-slot PCI-E card, not measured clear length. Xubuntu 14.04 (main) and Windows 8.1.

Water, I should think.

A fairly normal planet, but Nightfall is set in a sextuple star system. The orbits are such that there is always at least one sun above the horizon, except when there's a once-in-a-millenium solar eclipse. The real world is scarcely less strange than fiction. Take Kepler-70b, thought to have been engulfed by its star during the red giant stage but survived to orbit its star once every six hours, so close that the planet's surface is hotter than our own Sun.

True, a ballistic rocket will generally be quicker than a plane for either a trip around Kerbin or getting to orbit. The difference, however, need not be all that much. Fast high-altitude jets can get you around Kerbin quite quickly enough. For making orbit, there's often a tradeoff between fuel and time, and there's not really much need to squeeze every last bit of speed out of the jets like some players like doing, you can just do enough that the rockets handle the orbital insertion. Runway to orbit in five or six minutes is reasonable.

The demo helps in a sense by having a much tighter set of parts. First real milestone is to get to space. Fly straight up and see how high you get. If you don't get above 70 km, make the rocket bigger and try again. Next is to get to orbit. For that he may need the pointer that he should pitch over. Once in orbit with some fuel remaining he can start getting to grips with the map view and manouvre nodes. Setting up a Mun flyby or impact is pretty simple.

Ah right. In my case I use the proprietary nVidia drivers, so I'm guessing I could get a PPA with more up-to-date versions of those if I wanted.

So, questions a-coming: Is there any important difference between the scripts given in the OP, and doing the variable settings in a one-liner as shown in The Linux Thread? What benefits will Xorg-edgers actually bring, and would you recommend it for my "main" Xubuntu 14.04 install that I do 95+% of my computing on? Regarding Steam using its own old versions of libraries, is there a way to launch games through Steam (for overlay, hours played, etc) but make them use the system libraries on a per-game basis? (Just in case any other games give errors with them.) Related to my report here, http://forum.kerbalspaceprogram.com/threads/99430-Running-KSP-0-25-with-glxosd-results-in-missing-characters-in-text , any other suggestions for FPS monitoring? Time Control is a pretty big mod for the job with its own risk of causing problems.