sal_vager

Yeah I agree, maybe instead of the current method it should have had a maintenance cost for better recovery vehicles, cranes and trucks etc, so you get more funds back for distant recovery. But unless you are using the recovery service to recoup funds, the maintenance cost outweighs it over time, this would reward environmentally conscious players who recover as much as possible

This is actually deliberate, the transponder strategy is intended to increase recovery bonuses when far from the KSC, but the penalty is that recovery near the KSC is reduced.

Okay, the logs may show what's going on here, next time it happens don't close KSP, just get the player.log and post it to dropbox or pasetbin, the issue should show up at the very end of the file.

There is a misconception amongst players that their early access purchase meant that they were alpha or beta testers for Squad, when early access was only that, access to the game as it developed. However, Squad has listened to the players since the start, both when the game and fanbase was small and it was easier to deal with issues raised by players, and later even after it became abundantly clear that too many voices made public bugs difficult to manage. Squad is still listening to the players now, but the balance of the game is ultimately their choice, rather than the players, and as has been said Squad cannot please everyone.

They only start disabled if you mod your game, they are enabled but not active until you get hot enough, and the F10 toggle is not persistent at all.

To add to this...

Squad are aware there is an issue KOCOUR, but I can only answer this on the day it's fixed.

Persistent saves have not changed and KSP should update the persistent.sfs periodically, also on exit to the space centre. Please upload your game logs and settings.cfg Maelstrom Vortex, see the support stickies for details on finding these and how to post them.

Hi Mystic, there seems to be an issue with OS X graphics drivers and the Unity3D engines built-in anti-aliasing, try turning it off in the KSP settings and see if this solves the problem. If this doesn't help then please provide your game logs and pics of the issue, see the support stickies for more information.

Hi jorrdann, the altitude and distance records are automatically awarded when you pass the required threshhold, are you accepting any of the four starter contracts? They must be accepted by clicking on them and clicking accept, then completed to unlock further contracts. Also please see the support stickies and provide your game logs.

Hi lewisd, your craft file failed to attach, please use a file sharing service such as dropbox.

Excellent news Prof_Strangelove, I don't use Gnome panel here so would never have spotted this one, I'll add your findings to the opening post so it can help others.

This may be an artefact of the new name generator, as Kerbal professions are defined by their name string.

Hey, I heard my name? Is Vanamonde around?

Hi guys and girls I think Raincrafter is around here somewhere.

Firefox doesn't write to the KSP logs though, you have a 1.0.0 settings.cfg yet your logs say you are playing .90, that will cause things to break.

Sample of KSP's impression of "a field in Cornwall using a tart's fishnet stockings as a blindfold." please (pic of the issue)

Well, right at the top e have this: (process:13590): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed And further down this: FMOD failed to get number of drivers ... File not found. So it looks like you're missing some libraries that KSP needs, open a terminal and run the ldd commands from the previous link, they will say if a library is missing or an incorrect version. Edit: kiwiak you're using a 1.0.0 settings.cfg on 0.90, delete your settings.cfg and try again.

Nouveau will be off when using the proprietary driver, I really don't recommend removing it, and yeah you can get the proprietary driver in a few different ways. Driver Manager may just not be detecting it, it should be listed in Synaptic though, and you can try running glxgears in a terminal to see if it's working. Can you post pics of this issue please, someone might recognise it. Also your logs please after the glitch occurs.

You can find the info here

Is there any way to force it to detect?

The contract should be pretty explicit, but you shouldn't get that contract if the correct wheels are not available. And yeah airplane gear isn't suitable sorry.

That's just it though, it wasn't It's easy for experienced players to press Z or X though.

Not as far as I recall kiwiak, can you provide your settings.cfg, hardinfo output (or equivalent) KSP.log, player.log and current desktop volume settings please.

Okay well KSP isn't designed with being left on for days at a time in mind, it's not a use case that's ever been tested. Anyway we can't really tell much from what you've provided, so please see the support stickies and put your game logs and system info on dropbox. Testing this is not something I can really do here sorry, and I hesitate to ask anyone else to leave either their computer or KSP running for so long. It's a bit odd that you don't have the alsa daemon running yet use alsa for sound though, also have you noticed this with any other games? FTL will crackle on my machine after a few hours play, even if I restart it, the only way I can fix that is to kill pulse audio.