Bolche

While designing my awesome 100% recoverable shuttle, I ran into a problem while rotating the boosters' Mainsail engines to compensate for the unbalanced CoM. It is inspired in the design of the SpaceMaster, with two orange tanks attached to a Probe Core that is attached to the spaceplane I want to launch. You can see result in the picture below: To achieve the intended result, both engines should rotate toward the spaceplane, but one rotates "inwards" and the other, "outwards". I tried to change the symmetry mode to "Mirror" but when I attach the engine to the tanks, it automatically changes back to "Radial". I tried removing the tanks and changing their symmetry, but ended up either with one engine on the top of the rocket and the other at the bottom, or the parachutes and Vernor engines (that are attached to the side of the boosters) at different positions, one "inward" and the other "outwards". While designing this craft, I made the boosters at the VAB, the spaceplane at the SPH, and merged then at the VAB. Not sure if that affected something. The strangest thing is that at an old save I had the exact same design on an older KSP version and it worked all right! KSP 1.0 if I remember correctly. But this craft was made from scratch in this save and is slightly different. Running KSP 1.0.4, 64bits, Linux, with several mods

This buddy system looks like a great idea! Definitely will use it. I installed MKS/OKS to try to create life support resources, but it is very hard to make a closed system. Anyway, thanks for the answers. It looks like there is no easy way. They'll have to be (relatively) alone out there...

Arch Linux with KDE. It has problems, but is always on the cuting edge!

My space program is close to finish developing a lively economy in the Kerbin System with orbital and land bases, shipping resources and regular crew rotation (the Kerbin Workers Association demands paid vacations for every Kerbonaut every year, at least ), all done with my fleet of fully reusable Shuttles and SSTOs. It is past time to go interplanetary, but I admit that I'm a little afraid and not really sure how to make it viable. I have assembled expeditions to Duna and Eve but maintaining bases and shipping resources seems really difficult. Getting the right phase angles for efficient transfers can take years, the transfers themselves are really long (and it gets boring to wait when you can't time wrap because of other things going on the Kerbin System), life support (I'm using RoverDude's life support mod) becomes a greater concern. Not to mention rescue missions when things go wrong: on a past mission, after I accidentally blew up half my rocket, including all the life support, I was able to get a rescue ship in less than an hour (by wasting fuel and being super aggressive in the transfer/rendezvous). If something like that happened on Jool, I could kiss my brave kerbonauts good bye... So how do you guys do to have a working economy and crew rotation on a interplanetary scale? Do you just accept longer delays and compensate with large volumes? Do you waste extra Delta-V doing inefficient transfers? Is doing a bi-elliptic transfer, with a first stop on a low Kerbol orbit, a good compromise between time and Delta-V? Or the only solution relies on technology not yet discovered (i.e. should I use a FTL mod)? All help is appreciated!

On Linux, sometimes when I upgrade KSP to a new version, it's common that the zoom speed is super high. Going into settings, several things also have insane values. My tip is to delete (or rename) the file "settings.cfg" on the KSP folder. A sane default with sane zoom speed will be created.

You can use the monodevelop to develop in C# on Ubuntu. But if you want to only use the mods, you don't need to compile anything. I recommend using CKAN. It's just like apt-get.

Use Right Shift instead of Alt

I had my first crash yesterday (Linux x86_64, lots of mods). The game is really stable.

A day is the time the planet Kerbin takes to spin around it's axis, i.e., 6 hours independent of game settings.

After seeing so many complaints with 1.0.2 in the community, I almost didn't upgrade. Well, I'm glad I did. I think 1.0.2 is a HUGE improvement. Even if it's not exactly right and still needs tweeks, it's better. My reentrys on 1.0 used to suck: I didn't slow down at all. I used to get to 10,000 meters at over 1,000m/s. It was mandatory to deploy the uber chutes while there still was reentry heat going on. I just loaded my game on 1.0.2 and returned from the Mun. It was a really fun reentry: I spent half of my heat shield and I actually slowed down, deploying the chutes after all heat was gone. As far as I can tell from some other posts, the Mk1 Pod does not really need a Heat Shield anymore. But my lander with a basic science package definitely needed it. Just consider the Mk1 Pod has a built-in heat shield. As for the memory leak, that, I agree, is pretty bad.

If you got it from steam, them just log into steam and it will update Edit: Ninja'ed

I had a similar issue and, looking at dmesg I saw that the GPU (Radeon) was restarting every few seconds and freezing the scene. On my case, the problem was with the driver. Check you dmesg for error messages

There is a Changelog.txt file on the KSP directory if i'm not mistaken. This is probably what he refers to

No SquadCast Today? What should I do with my life?

From the log, it looks like you need to update your graphic driver. On Ubuntu there is a program to install new drivers (I believe it's called "Jockey". Just search for "drivers" on the main menu). Choose the "Nvidia proprietary driver". After install and reboot, it should run.

ROM? Most personal computers dont have a proper Read Only Memory (ROM) anymore. If you mean RAM, them the answer is NO.

You know those annoying messages you get on Windows "This program has stopped working" (or "This program has performed an illegal operation" on older Windows versions?) That we call a "Segfault". It's a problem with the program. It's not a Linux exclusive issue, as you are probably already familiar with the issue in Windows. But in Linux we can actually fix it with the code shown. Personally, in my computer I did not had to apply this. The vanilla version just worked. Try it first, before executing anything.

Never heard of glxosd. Can you send a link? You probabily would put a command between "taskset -c 2-3" and "./KSP.x86_64".

Wow! How could a vague tweet turn into something this ugly? Please, people, let's have some faith and wait until things are unveiled in Devnotes. As far as we are know it could be that enginers can calculate how Delta-V changes in-flight ("after this burn how much DV I have left?") But DV always shows in the VAB. I think that would be awesome and a reason to actually carry enginers.

Judging by the date it was posted on the forum, the first mod released was ugly red fuel tank (http://forum.kerbalspaceprogram.com/threads/454-Yxxxx-Industries) on 16th July 2011, but a thread that talks about changing liquid engines is older (http://forum.kerbalspaceprogram.com/threads/78-Fuel-Rocket-modification-freezing-stopping-the-game-at-Loading). There were some really awesome stuff from the beginning. You can view them on http://forum.kerbalspaceprogram.com/forums/35-Add-on-Releases?sort=threadstart&order=asc

An air tunnel-like thing would be an awesome way to give information about a craft in the new aero. Click a button and it shows the craft in a tunnel pitching, yawing and rolling. Them you can quickly see how the plane behaves.

I had this issue since .90 came out. Sometimes, usually in map mode, the game would freeze for a minute or so and them come back. I finally solved it and I'm here to help someone else that might be having this issue. It's systemd's fault (or the radeon driver not getting along with systemd or something like that) . Basically when the GPU does some activity (I suspect it's fence signaling, but can't say for sure), it causes journald to create a coredump and spend a long time dumping the process to the disk. You can solve it adding Storage=none to /etc/systemd/coredump.conf I'm on Archlinux x86_64 with intel/radeon open source drivers. I hope it helps someone. Details: https://bugs.archlinux.org/task/39806 https://wiki.archlinux.org/index.php/Systemd#Disabling_application_crash_dumps_journaling

The usual way to solve this is to install an older distro in a chroot, with deboostrap, or LXC and compile there. It's pretty lightweight. But I'm curious. What are you hoping to accomplish with this? If libmono was vanilla, I would like to use my system's too, but since it is not, whats the use of not using Unity's?

Ferram Aero Space Research (FAR) has been updated. v0.14.5 works with 0.90.

I can confirm that the database reload from the Debug Menu solved the issue for me.