cantab

If the arrest warrant was to be issued by either the astronaut's country or the spacecraft's, I think it simply wouldn't be issued. The high-level government would lean on the police to quietly postpone it to avoid bad publicity and affecting the astronaut performance.

This is not my Tylo lander (dur). This is not my Tylo lander's transfer stage. This is one quarter of my Tylo lander's transfer stage. In orbit by cantab314, on Flickr (Not launched full, I used most of its fuel along with a couple of SSME clusters to make orbit.) EDIT: And here's a teaser of the lander itself, which self-launched to Kerbin orbit: https://flic.kr/p/pm3gYP

Lodestar, yeah, I've had that issue in the past too. Rather annoying and I don't know a user fix (as opposed to something the modmakers could have to do).

It makes part placement consistent. With the debug menu option on a part will either place in any orientation or not place at all, the latter in cases where the part being attached or being attached to does not support radial attachment. With the debug menu off, whether the part can or can't be placed seems utterly arbitrary, as I think everyone here has experienced.As Harvester has said, .90 will remove this arbitrary behaviour.

Pretty much.Anyway there's a few things that can affect KSP performance. Lack of GPU power. This will lead to poor framerates on the menu screen and when flying low part count ships. KSP's not super-demanding in this respect but it is a 3D game. Solution is to reduce graphical detail and/or resolution, or get a better graphics card. Poor graphics drivers. Same symptoms, solution is to get better drivers. "Water lag", which I think is a particular case of lack of GPU power. This will lead to poor performance when looking at Kerbin but good performance when looking at the sky. Solution is to create a custom terrain detail preset in settings.cfg and reduce the detail values for the oceans. Physics lag. This will lead to slowdown with high part-count ships. Framerate will actually be OK until the part count gets extreme but the timer will be yellow and the "Physics Time Ratio" in the debug stats will be less than 1x. Solution is to get a faster processor or use lower part-count ships. If you're video editing, there is one more option: fix the slowdown in editing. Depending on the exact issue this might work more or less well; a recording affected by physics lag can be simply sped up but one affected by lacking graphical power not so much.

How do you know? Not all viruses make themselves obvious, some expertly hide themselves from future scans, and novel malware might even go unnoticed by a bootable antivirus CD.

Granted. But EA get the idea and are first to market, and they give it their usual touch. I wish I had a better chair.

Agreed. I admit I've not checked the updated parts yet. Ring wings are a thing (though real ones tend to be squashed, not circular), so I can imagine a streamlined warp drive that's also a wing.

Granted. It makes Top Gear's effort look professional. I wish Top Gear's shuttle had worked.

To everyone else, I'll say only that sedativechunk's experience is not the norm. He may have had hardware compatibility issues - less of an issue than it used to be but it does still arise sometimes. He may have followed bad advice or used old techniques on the setup - a potential issue with any OS or software. As for WhiteOwl's experience, sound is one thing that's a massive mess in Linux unfortunately. Try not to end up messing with it. I've been using various Linux distributions as my primary OS for a decade now and have got on well with it. Valve trust it enough to use as their planned Steam Machine's OS. It's not without issues, but no software is. Oh, and OSX is in my limited experience an annoying and hard-to-use interface. It may share design concepts with Unix but Apple's philosophies are the antithesis of those of most Linux distros.

I would merge this thread into the megathread. Anyway, as mentioned depends on which i7. But even for the latest-generation "Haswell" processors, 3.2 GHz is on the slow side. You can expect over 4 GHz with an overclockable one. Elthy's outline is reasonable. I'd add though not to go dirt-cheap on the motherboard. There's no need for overpriced "gaming" stuff, but get one that's got decent reviews in particular good overclocking, and also look for four RAM slots (unless you want a compact computer). I'd also get a quality 400-500 W power supply to better support a future graphics card upgrade and just generally give more headroom.

I've got on quite well with Panda. Does its job and largely stays out of the way. However it did have a bug with mapped network drives. If you use a fileserver or NAS it might not be a good option.

Granted, but it's got Luftwaffe markings for some reason, and you can't repaint it. I wish for you to guess.

By most reports .25 ended up being a step backwards in terms of Windows 64-bit stability. The bigger problem now is that several modmakers, fed up of bug reports they believe are down to the stock game, have made their mods refuse to run on Windows 64-bit KSP. On the Linux side of things, 32- and 64- bit KSP are both equally stable and both fully supported by nearly all mods.

I found some similar things on Duna the other day. I was driving at night and it was quite visible, a glowing patch on the ground maybe 2.5m across, brighter in the middle. Oddly it was not visible when the active vessel was an EVAing Kerbal. Showed up in the same place if either my rover (lights on or off) or flagpole was active. Screenies to come.

Granted. All explosions become impossible. While you're driving across Death Valley in a petrol-powered vehicle. I wish to skip an hour right now.

An air launch would serve to "start" a ramjet. But then you can just do that from the runway with JATO boosters.

Granted. It overheats and breaks. I wish that Voyager 1 would have unlimited electrical power and not overheat.

Granted. I'm not one of them. Why have you got an East Korean flag as your avatar? I wish furmark didn't stutter. It's just annoying.

To be honest gsarducci, since the stock game worked fine you probably have a mod issue. Try one mod at a time, each on an otherwise stock install, to isolate the problem. Then if that doesn't find any problems, to diagnose a general memory usage issue I'd throw a bunch of pure parts mods - ie ones with no plugin component - on. If that turns up no fault it's probably an interaction between mods, harder to pin down but keep a one step at a time approach to the mods. Also, make sure you don't muck up any of the mod installations! I guess you could do worse than to run prime95 for a bit, check that your overclock is truly stable. You probably did it when you set up your OC, but you never know if things might have changed. It's a long shot this being an influence. You also could disable the integrated graphics. I think Linux does sometimes dislike having multiple graphics drivers active.

The big one I think is the jet engine. It needs to operate at something above Mach 5 to make enough of a dent in delta-V requirements that rockets can propel the plane to orbit, that's tough. It needs to also operate from a standstill and that's really tough. The Reaction Engines SABRE (that inspired KSP's RAPIER) is one of the few realistic efforts at this, but it's some way off ever propelling a vehicle. The SABRE, incidentally, requires a cryogenic fuel; it's used to chill the incoming air before being burnt. A kerosene-burning SABRE would be impossible. Even liquid methane wouldn't be able to offer the same performance in the precooler.

I'm not sure. I've been trying to use DuckDuckGo because of concerns about Google, but I still use Google a lot. DDG often isn't all that good. I also use Wikipedia a lot, it's my go-to general reference source, and I wouldn't be surprised if it's actually my most used search engine.

I would not recommend that. You can and frequently will typo your password.

One more suggestion to make things more tolerable. Instead of sending up modules and just adding them on in sequence, build up two halves (in different orbital locations) then join them. That way in all but your final assembly step you have to deal with less than half the part count. Won't do anything, because when you launch a ship the .craft is basically copied to the persistent.sfs. I don't believe editing the persistent.sfs in flight will have any effect either, since that's only loaded when you load your save.

If you aren't averse to mods, TAC Fuel Balancer will let you dump the excess oxidizer once you're in orbit.