sal_vager

Hmm, digging deeper, ".local/share/Steam/ubuntu12_64/gameoverlayrenderer.so" is a Steam file for the Steam overlay, and it's not a KSP or a Unity3D file at all, as KSP files are in ".local/share/Steam/SteamApps/common/Kerbal Space Program/" I suggest you start the KSP.x86 directly from the Kerbal Space Program folder, this will bypass Steam, the Steam overlay and gameoverlayrender.so completely. If the game works you can easily make a script to start it, or a symlink to the KSP folder, as for why Steam is causing trouble however, that's be a matter for Steam support

Heh, Macs using a lot of Ram is common, apparently this is normal and "unused ram is wasted" Several Mac users I know are finding 4 to 6 gigs of their Ram are in use even immediately after boot and with no programs open, and on an 8gig system that isn't leaving KSP with as much, especially if you have Safari or other programs running. Yes KSP and the Unity3D game engine will load assets and keep them in memory, these are freed on scene change but the PQS terrain system is known to allocate a larger cache than there is memory available, but rather than being a "memory leak" this is a bounds checking issue. There's no fix for this at this time, the only workarounds are to reduce memory usage overall with texture management addons, the 1.0 release should improve the situation though if Squad take note of community feedback. Also, KSP on OSX has some issues with graphics which may explain the grey grid xerogravity reports, these are usually caused by anti-aliasing and the PPFX edge detection graphics feature, neither of which are working properly in Unity on OSX and are disabled by default on OSX for this reason.

Please see the support stickies, we'll need to see your logs

Well something is definitely wrong, you should not have this in the log: This suggests it may be a permissions issue, but could also be an overzealous anti-virus or some kind of security software that is preventing KSP from accessing the files it needs. You may need to try a clean boot to eliminate other programs from interfering.

Hi xerogravity It has been noticed that Macs use a lot of RAM even when idle, so there is not much RAM for KSP, this causes KSP assets to be cached and they may not be retrieved properly. Anything you can do to reduce your RAM use may help, such as shutting down unused applications, also please see the stickies and provide your logs.

Please see the support stickies Delrey, we can't help without your logs

Please see the stickies Varkolyn, we'll need your logs

Please see the stickied support threads Geoffry, we need more info from you

Hi 6677, officially KSP (and the Unity3D engine) support Ubuntu, so that's probably why the folder has that name. The black screen is a big clue here, it's having trouble with your graphics chip and driver, unfortunately you don't have much option with Intel but to use the Mesa driver. There's a few known fixes for Intels on Linux, though one has stopped being viable recently as the Intel string in the binary seems to be missing, none of them address this issue though. You could check all the libs you need are installed with "ldd KSP.x86" and see if the x86_64 binary will start for you.

Sorry crashy, openGL is not supported on Windows, only DirectX9. It's probably just a corrupt font, you can download replacement Arial fonts here

Hi crashy We may not be able to help, openGL mode isn't anything to do with Squad, -force-opengl is a Unity3D built-in command line argument and if it works, great, if it doesn't you need to ask on the Unity3D forums. All we can really suggest is that you ensure your drivers are up to date which you say they are already, or to try -force-d3d11, but expect graphical issues with any of these forced modes. The only mode that works properly is the default d3d9*. *Except on Linux and OS X, where openGL is the default.

Squad will look at Unity5 after 1.0, right now they cannot support a 64bit release using Unity4x and cannot fix issues that are caused by the Unity4x 64 bit builds. There really is nothing more that can be said, continually asking for it won't make it happen any faster either. Thread closed.

Don't forget the rules Ethanadams

Gentlemen, this thread is starting to go off-topic, and I'll thank you all to avoid derailing it any further.

Yeah guys, don't be harsh about this, how about you explain nicely why this wouldn't work?

Welcome to the community Trent Do try to stick to English though guys, forum rules an stuff.

No probs, have fun

Yeah I tried that, all the parts were still there

Well it's the Mk3 cockpit now, and it's working Linky *Kerbpaint not guaranteed to be working

Zekes, where's the root part?

The fairing on the 909 looks awfully short, I think AlexinTokyo is correct, and our thrust is being blocked by the fairing. It might be possible to edit the part out of the save file but I'd send a rescue craft instead, rescuing is a major past time of kerbals. Edit: If you upload your save file we could try fixing it for you, make a quicksave (F5) and put it on dropbox.

Hmm I can't see your staging, is the decoupler not decoupling?

Can you please upload the craft Zekes, one of us may be able to fix it

Hi lordmasta, you're playing the 64bit version, and career is broken. You'll have to play career using the normal KSP.exe, and only use KSP_64.exe for sandbox.

That's no way to help someone vlxr... rhidle, no it is not normal, but we're just volunteer here rather than paid Squad staff so we can't access accounts or really do much to help you, though it'd be helpful to know where you bought KSP and what you've tried so far. If you bought KSP on Steam you'll need to contact Steam support, same if you bought KSP from anywhere else that offers Steam keys but if you bought KSP via the Squad store then emailing Squad is the right thing to do. But please bare in mind that Squad do not work on the weekends so there would be no one to answer your email, you should hear from someone later today or tomorrow however. Also, you may have access to the game and just not know how to get it yet, Squads store instructions can be found here. Hope this helps!