steve_v

While not really into drones myself, I know several people who very much are. I can anticipate the reaction... it's a toy. Or a fancy selfie (filthy habit, that) camera at best. Not to say I wouldn't take one if it fell on me, but I'd pull it to bits before I actually used it for intended purposes. Drones that do something useful or are even just fun to fly I can dig, but this appears to be for people who want fancy pictures / videos of themselves with no photography or piloting skills required. This product gets a solid "Meh" from me, unless of course it proves to be highly moddable. - - - Updated - - - Oh, and if I see one of these "flying cameras" anywhere near me I am liable to deploy "countermeasures".

Performance, or the lack thereof. And bugs.

Depends... I have GNU/Linux installs at <500MB, and one at <1.44MB . For a 'general purpose' desktop you're probably going to want at least 6GB for the OS, + enough for whatever you intend to install later. FWIW, my current Debian desktop has a 16GB root partition and the the remainder of the 250GB SSD is /home. Partitioning options are somewhat more flexible in *nix, you can always rearrange later or mount extra drives into the filesystem.

StageRecovery should be stock, IMO. Feels nicely balanced to me, and saves a lot of boring debris recovery.

I find that VMs provide very, very close to native performance for anything that's not graphically intensive*. Boot times are actually somewhat better in a VM.As for VM software, my vote goes to VirtualBox. It does almost everything VMWare does and it's free. There are many advantages to using a VM, some that come to mind: Differencing disk / state snapshots. Ability to run several VMs at once (RAM permitting). Shared clipboard and drag/drop with the host. Ability to 'hotplug' devices in software. Ability to create virtual hardware configurations you don't physically have (multiple NICs, disk drives etc.). Good isolation for testing of potentially dodgy software. Relatively safe way to run outdated/unsupported/insecure operating systems. VirtualBox has "seamless" mode, presenting guest windows with the host window manager - run apps from the vm as if native. I'm sure there are more. *Assuming you have VT-X/AMD-V, which pretty much all modern CPUs do. OpenGL performance is ok, but not game-worthy unless passing through to a real GPU. - - - Updated - - - GRUB2 isn't all that bad, the configuration complexity is mostly due to distro automation. You can still create a "simple" all-in-one-file grub.cfg that's no more confusing than LILO is.

Well, since it appears to be TweakableEverything that's choking, you could try removing that or asking in the thread for the mod.

If the physics works, it works. Implementation might be a little problematic though, and the politics downright unpleasant I too like the concept of the '500ton SSTO', but the idea of detonating hundreds of nuclear weapons inside the atmosphere might meet a little resistance. - - - Updated - - - I guess my vote goes to medusa, if only because space is a somewhat safer environment for playing with nukes, as far as long term consequences go.

Personally, I'd beg to differ. But as you provide no reasoning whatsoever, I guess you're entitled to your opinion.

Yeah, a log file from a crashed session would help.But I'm pretty confident as to what you will find... OOM, due to a memory leak. It is, however, unlikely that the root cause will appear in said log, just the symptom - an Out Of Memory crash. I'm seeing the same ~100MB increase in memory usage with each revert, but without the crash (x64 on Debian Jessie). There's nothing suspicious whatsoever in my logs. Also, if this is what I think it is, it has been reported many times before.

Well, if you want to look at it that way adding a fan to the heatsink is also "active" In this case however, I think "active cooling" means reducing the temperature of the "cold side" of the interface to below ambient - with something like a thermoelectric (peltier), phase-change (refrigeration) or evaporative (liquid nitrogen etc.) system. Once the thermal resistance of the heat spreader / TIM becomes the bottleneck, it's the only way to improve heat transfer further.

You already are, OpenGL is the only option on Mac/Linux.

This sounds exceedingly promising

My point exactly.

There, fixed Actually, Linux has the only stable/supported 64bit player at the moment, though the demand is strong for this on Windows so we may well see it with 1.1.

Ditto on GNU/Linux, so I don't know what's up here either.

Err, me? I don't really like needlessly killing crew on launch. Anyone else feel that instant revert seconds before exploding is just a wee bit too, ah, forgiving?

The true meaning of that acronym illustrates why this situation is so annoying - hands on the stick means hands off the keyboard and mouse, which implies everything shall be mapped to the controller. Without manual config edits if you please.

That's what Launch Escape Systems are for.

Picture playing with no reverts, no quicksaves - it is a valid difficulty setting.IMO, anything that causes me to lose hours of play under these circumstances qualifies. Examples: Docking ports not releasing. Claw related physics bugs. Random unexplained overheating. Engines that "cannot activate while stowed" (and aren't). Kerbals ejecting violently from hatches. Random orbit changes coming out of timewarp. Infinite ragdolling. Surface bases leaping into the sky and exploding on reload. Unintentional kraken drives and phantom torque from clipped parts. Even the occasional NAN kraken for no reason whatsoever. The list goes on. Any one of these is aggravating enough that I don't want to play any more, and therefore game-breaking. Some can even permanently corrupt saves or craft in play - the claw/frozen orbit bug being the most obvious example. If you want more, go have a look through the support subforum sometime. Please, it's finished when this stuff stops happening, and I don't have to save-scum every time I do anything.

That people (who may have spent "tons of hours") are here complaining is simply an indication that they care. If it wasn't a worthwhile game I would have quit in disgust long ago. But beta testing is (apparently, says squad) over now, time for some polish and bugfixes. I have yet to finish the tech tree, ever. Because bugs. I am also counting all those "do over" missions, because bugs. That accounts for much time.

While I have indeed spent many hours playing the game, I have spent almost as many debugging the damn thing or attempting to recover craft taken by game-breaking bugs. Yes, it's a good game. But it should be better, and it won't be "finished" until 100% of my time "playing" it is actually spent... playing.While I expect this sort of thing from "early access" or beta software, it's inexcusable in a released product.

Now that you mention it, where's the poll option for "taken by the kraken, in his many forms"? If it weren't for quickload / revert I'd have lost far more kerbals to bugs than any pilot or design errors on my part. On the "collided with <something not there>" bug, I certainly have encountered this, repeatedly.

I have fairly recently revived an old DOS machine, and a collection of 50+ games, circa 1995. Bugs encountered = 0 Patches applied = 0 Crashes = 0 Release quality = stamped on CDROM, or packaged on floppy disks. Fixes practically un-deployable, and yet everything works. Have expectations of software quality really fallen so far? Were this an open-source project, I'd be happy to contribute to development and hunt bugs. But it's not, it's a released commercial product. The content that constitutes a "finished" game is negotiable, bugs and crashes are not. They are simply indicative of a shoddy, unfinished product. That the community has, so far, put so much time and effort into fixing squads game for them is commendable. But it's not our job. KSP will, IM(NS)HO, be finished when one can play through the whole game without encountering bugs, crashes or unintended behaviour. Thus it has always been, for any software project. If it doesn't work properly, it's not done. I stand by my <= 70%, until such time as I can play the game without having to go bug hunting.

In days gone by I'd agree, but grub has grown on me somehow. I'll never forget those 'LIL.... Oh drat, the bootloader's borked' moments.

Feature-wise, It could be called complete at any time. It stands as a good game even without the upcoming content. But there are still far too many bugs and performance problems to give it more than 70%, IMO. TBH, I'd be quite happy with it if the core game was stabilised and the rest left to mods. But with the bugs, poor performance, and physics engine glitches it still feels very alpha.