sal_vager

Please see Kasuha's thread on fuel lines

The problem here is anti-aliasing, Unity's built-in anti-aliasing was found to cause severe instability on AMD drivers around the time of the Linux version release and had to be disabled. The latest versions of Unity have now broken the built-in anti-aliasing for Nvidia drivers, and it's never worked with Intel and the Mesa driver. We can use the graphics drivers own software to force per-program anti-aliasing or force it system wide however.

The correct version number will be in the buildId.txt, this was found to be an easier way of updating the build Id instead of changing the number in-game or rewriting the readme every time. As you can no doubt imagine, if we're on 464 now and 0.23 was build 395, there are a lot of builds between updates

There were fixes, they came out quite soon after the release, the current version is build id 464

Yeah the flag issue is a pain but it's not a major hassle, and build 464 is the current release, running the patcher won't get you any further at this time, sorry.

Make sure your patcher is up to date, or just forget it and get the full copy from the store, the patcher should work but so many things go wrong.

Please refrain from turning this into a political discussion and resorting to personal attacks, thank you.

Well you could try the new claw part, the guy here did pretty well with it

Gentlemen this is one of those discussions that has no answer and no end, and is about as far from KSP and rocketry as one can get, it would not even be a topic suited for the Space Lounge. The discussion above has touched on Religion, Politics, and various fallacies such as appeals to tradition and just plain old gut feelings. This will be closed to prevent it going off the rails as threads like this so often do, and to protect us, whether we are fond of meat or prefer to avoid it, from undue and unwanted argument as to why we are wrong in our own personal choice of what we eat. Good food should be enjoyed by all, it should never be a cause for division.

I'm sorry Brucey but much of this is either planned, or has been suggested so many times we've put it on a list of frequent suggestions, to try to prevent its reoccurence. Also such threads do frequently become argumentative because of the above, I thank you for your time making this, but I am going to have to close it to prevent the usual responses these posts draw. Oh and Javster, it's just a word, calm down buddy.

Unfortunately not me Humptydump, I remember there was a serious issue with AMD drivers ages ago and AA had to be forceably disabled, while Nvidia AA died with a recent Unity update (4.1 I think) You can force it via the driver itself, and set up a profile for KSP in your graphics cards own software but it won't work out of the box as far as I know.

mrabinovich, I bet it's that decoupler bug we're seeing in other threads in the Support section, it can be fixed by setting the physics significance of the new decoupler to zero, you'll need to edit the part.cfg

Because this! Every month a random number of particularly good threads from the community are given the spotlight of stickyness, who knows Camaron, one day it might be you

Dimetime35c, you may be interested in this from the FAQ:

Need to add a comms tower or a fuel store? RAMMING SPEED!

This probably should be in Development discussion to be honest as it's an unfinished/unpolished feature rather than a fault in the code I'll pop this over there.

This thread is turning bad, we can't all be deviantArt quality Czosnex, let's keep things civil in here or I'll have to start clearing out the trash.

I don't have a demo Mun craft handy, but this will get to Duna and back on demo parts, so the Mun will be a snap (the craft may have a fuel line issue, watch your fuel balance!)

Hi and welcome to the community Gonçalo You might like this site, as it lets you see where satellites are on your PC. I find that the ISS can be quite hard to spot in a city, it's better if you can find somewhere away from the city lights.

Lets not have any rules broken here okay guys?

Nice find jdiaz, thanks for posting this

Gentlemen, please relax and politely point out flaws, and link to refutations, don't get too worked up over things

You don't really need that installer file, it's just for patching the binary and a few other things, you can just unzip KSP to somewhere in your home folder, right click the KSP.x86 and make it executable in its properties tab, then use it to start the game. If you want to patch the 64b binary just make a copy of the file first, open a terminal in the same folder as the KSP.x86_64 and copy/paste the lines from the memory/segfault fix. You can manually add a menu entry for KSP easily enough using the normal menu editor, and just find a little pic of a Kerbal for it

It's not a bad question, but the answer is "maybe". The trouble is that the graphics drivers in VM's are pants, VirtualBox for example supports up to Dx7 I think, and while they say they can access the Gfx hardware directly in practice it doesn't work very well. Graphics features will often fail to work resulting in some ugly issues or prevent the whole game from working at all, when I tried to get KSP working in a Windows guest before we got a Linux version it just crashed at startup. Everything else should be fine, but graphics drivers let the whole thing down.

If you are running something that needs admin privileges then yes it will ask, but KSP does not need them nor does the launcher, the installer should only need it for setting the binaries as executable.