sal_vager

Lol yeah I derped, it's the craft launch dialogue, but please try removing "-force-opengl" or "-force-d3d11" if you're using them, and check your KSP.log, if it says it's using the openGL renderer on Windows then it's likely you need to check your graphics driver. If you've just updated it, don't forget to reboot.

This happens when you use openGL as well, it was "fixed" on Linux and OSX by editing the pixel offsets by hand, but as openGL and Dx11 modes are not supported on Windows it's unlikely this will be addressed, sorry. Also notice your mission control background is missing...

This really isn't suitable for these forums, sorry.

You should probably try reinstalling KSP.

Hi FoxHunt, this occurs when the affected save is missing files, usually the ships, VAB or SPH folders, please browse your KSP saves folder or your savegame, and if any of those folders are missing copy them over from another save. Alternatively your persistent.sfs could be corrupt, and you will need to replace it with a copy of your last quicksave.

Arthropode I think I know what is going on, depending on how you start KSP it is either able to find its config files because it is starting from the directory that contains them, or is unable and is looking for the files in the location where you started it, such as from a desktop link. Please ensure you cd to the KSP folder before starting the game, either from the command line, a desktop file, a script or even from primusrun, and not by using "./PathToKSP/KSp.x86" KSP like many other games will look local to where the binary was started, not where the binary actually is.

Please fix your permissions and clear the saved state for KSP, then try again.

This certainly is not correct. The first two lines tell me that you are starting KSP via the Steam client, this should be fine but the gameovrlayrenderer.so is a 32bit library, there is no 64bit version and you are using a 64bit OS, but as you can see it is being ignored, there is no fix for this by the way. The third line is very strange, I have not seen it before and it is likely another symptom of your issue, I suggest using a live cd to do a memory test of your machine, I also suggest you try running the KSP.x86 or KSP.c86_64 directly, and not via the Steam client. Steam starts KSP.x86 by default, but as you are using a 64bit OS you won't have any 32bit drivers, and may need to install the 32bit version of mesa with "sudo apt-get install libgl1-mesa-glx:i386", or edit the Steam options to start KSP.x86_64 by adding "LC_ALL=C %command%_64" to the launch options.

Well I'm sorry to disappoint you but things change, aero and heat were a very big change and KSP isn't a game about blowing up your own craft with your engine exhaust gases, so stuff like that isn't deliberately modeled. If you like, please see the support stickys, you will find a bug tracker link where you can report this issue.

Hi Oryip, will kSP work if you start the KSP.x86 or KSP.x86_64 in the game folder directly?

Thank you, there's no error during loading though, it looks like the last time you ran KSP you went from the main menu to settings and back but not into the game itself, there's no entry for changing to the KSC scene or the VAB. But there's a few things you can try, this is from the self help sticky. Please give those a go, then try looking in the VAB again, let me know what happens and upload the new player.log from that attempt.

The KSP.log will help, there's some stuff that isn't in there though so the player.log is better. That's all I know about finding the OSX log, hopefully it'll show an error message that'll give ideas on what's going on.

You can put the contents on hastebin, if it'll fit, or try dropbox.

Hi TrivialTurtle, do you see this with a new save? Please see the support stickies, and upload your player.log somewhere, we'll need to see it to have a clue about what's going on.

The blue line is showing anti-aliasing effects lance0625, when this is enabled via the graphics card driver you can get the effect you see there, try disabling AA for KSP and using the built-in anti-aliasing in the settings screen instead.

ZentroCatson, Squad will try, and we are all hoping Unity5 will be better for all platforms, not just OSX, I'm a little concerned that Linux may be adversely affected, but like you I have to wait and see. Maybe you can help though, we do need more OSX testers, drop Ted a PM explaining how you'd search and report bugs, and a little about yourself, he will keep you in mind.

Then it's doing damage, please keep going till it overheats or is damaged enough to explode, lots of things were changed for 1.0.x and parts blowing up too easily was one of them

Hi dimitriy, try opening the flight log (alt+F3) and look for damage being reported.

Moved, and please see here [LINK], we need information from you to diagnose the issue.

Moved to Gameplay Q's, though I think SpenSpaceCorp is correct, also floating point rounding errors will change your orbit slightly over time.

I am having no luck reproducing this, your files all seem fine, do you start KSP in the same way every time or does it vary?

Sorry Laythe Dweller, the space would not be visible so you'd effectively be impersonating an existing member, you'll have to think of something else.

Preferably somewhere with no annoying popups, ads, wait timers, demands that you login or need an account to download. We need an imgur for files...

This is due to the forum software we used to use, simple machines, vBulletin is not quite able to handle the different format.

Currently 88 additional members will benefit from this thread than would have done so in GD