sal_vager

If you could upload the KSP.log and the output_log.txt from the KSP_Data folder when this happens that could be very useful. You can find more info on these files here.

Hi @Seturian, this was already fixed, please provide your logs and save file so we can examine your issue. And please use a host that does not use adult adverts, thank you.

The issue is caused by Apples GateKeeper which is stricter in Sierra than in earlier versions of OSX, in the future it is likely that all software that wants to run on Apple operating systems will need to be signed, not just KSP. Assuming Squad doesn't run into issues with Apple with getting KSP signed that would probably be the best and only long term fix, there's no real way to work around this on a developers side, on the users side there are two known workarounds, running the binary directly or copy to a user folder and back, but these do not work in all cases. Code signing for OSX is definitely something that Squad and all other developers who target Apple systems will have to investigate, we'll have to keep an eye on the devnotes to see if or when this happens. Edit: One issue I expect to see would be the need to be signed again for every update no matter how small.

From the Firespitter thread So if these are Firespitter parts they cannot be reused without prior permission and attribution must be given.

Please only report the bug if you can reproduce it in a stock install with stock saves, thank you. If you can only reproduce this with mods please try to find which mod is causing it and contact the modder.

Let's not have arguing in this forum, thank you, this forum exists to provide players with technical support, not as a soapbox to complain about issues, so it has been closed to prevent derailing. If you can provide a simple reproduction of this issue please make a bug report on the tracker.

Yes this is due to the newer OS X @MissMolly, there are tighter restrictions on running unsigned software. You could try running the binary file directly, as ZachisCheese does here.

As you have another size3largetank I think it's time you reinstalled KSP fresh, then copied your saves over to the new install, as the size3largetank folder should not be present and there's no telling what other extra files you might have.

Good to hear!

Sent you a PM.

Nope, one account per person, get ready for a mergin!

Okay I'll change it Edit: It's already taken! Can you think of another?

Hi MissMolly, this may be the known issue with Mac's, please try moving the contents of the KSP app to another folder, then move them back, that should fix it. Also moving to tech support. Thank spacekumquat for this.

Not too long ago we had another report of this, turned out the engines on one side were blocked.

This looks familiar. If I remember right this is caused by a mod changing the path to another techtree.cfg, make sure the career node in your save points to the Squad tech tree, like this. The two nodes above are not stock nodes and do not exist in that file, so you may also have to look for those nodes in your persistent.sfs and delete them, back up the file first though. Mods leave traces behind in many places, and can screw up a stock game even after they are removed, so it's important to keep stock and modded saves separate.

It should compress pretty well, it's just text, maybe try zipping it up.

Not him, me. Next might be @Climberfx

Anything in your logs? Also, if you rename the physics.cfg KSP will make a new one with default values, so unless a mod is changing them it might stop whatever this is.

Hi @BOX, we're going to need more info on this one, KSP should not even be able to crash your mashing like this. Please see this thread. We'll need the logs from after this occurs, your dxdiag (assuming Windows) and the craft that causes the issue.

Hi @MrAAA264, I think you need to contact [email protected] directly, as we can't deal with account issues via the forums, sorry about that.

Hi @cfbird, I am sorry you are having trouble with KSP, and I'd be glad to help you solve this issue, I'm sure this is something we can help with. First we have to find out what your issue is exactly, as saving and loading is working here for me and for many other players your issue is not known. To help you we will need to see the logs from your game and from your computer, you will have a KSP.log in the Kerbal Space Program folder, and an output_log.txt file in KSP_Data on Windows. On Linux you will have a Player.log in .config/unity3d/Squad/Kerbal Space Program/ For Windows we will also need your dxdiag hardware report, you can run dxdiag from the start menu, and on Linux you can use the hardinfo package to gather info on your system. Please put all these onto dropbox.com for us and we will try to find out what is causing your problem, if or when you lose saves again upload new logs so we can see if there is a change. Also, KSP automatically makes backups of your saves on Windows, Linux and OSX, so all is not lost, check for a backups folder inside the folder for your save. Thank you.

Hi @Konvict, likely you have this issue. Please disable the highlighter in flight from the settings screen.

Hi @Goldenseek, before deleting anything can you please try attaching the tank again, then find the output_log.txt in KSP_Data and paste the contents to pastebin.com for us, thanks.

@ComradeGreen, it's the Promethues VI Lander, if you remove that craft the rest will show in the list as normal.

Hi @Pajn, please see here as we can't help you without more information.