sal_vager

You could try the demo, it's a little old but generally if it runs so will the full game. Something to watch out for though is your GPU will need to support shader model 3.0 or higher, and you will need at least 512bm of video RAM. KSP works well on the open source mesa driver, though a Unity bug may mean you have to start KSP with the -force-glcore command line switch to get the text on the correct layer (else you can't see them) KSP can crash, some people have it worse than others though, and the crashes are cross platform. Shadows can be poor, but changing the render quality in KSP can help with that. Hope this helps!

Both your issues might be caused by the lack of graphics memory your laptops, and I should have spotted that in your first post, sorry :/ From the Squad store. 256mb of video RAM is pretty low, I'm not sure if KSP will run with so little and it may just require a lot longer to load. Try lowering the texture quality in the Launcher.app, that might help.

Hi @Fastfishy2, you can upload the files to a site such as dropbox.com and post the share links here. The specifications that are most interesting to me are your graphics driver version and install date, though you can just check for and install the latest driver here (assuming you are using the latest version of Windows) and see if that helps. What you describe sounds like a vertical sync issue, you can try disabling V-sync on KSP, in the Nvidia control panel, or make sure your refresh rate in the Nvidia control panel is the same as your screen, it's usually 60hz. Though if there is a fault with the laptop it would be better to have it serviced under warranty.

Hi @shadragon, you don't have crew in the craft in your screenshot, if you've launched all your current Kerbals you will need to hire more from the astronaut complex. I see some text over the message app in the upper right, if you are using a 3rd party program to monitor frame rate such as PrecisionX 32 or Fraps try disabling it. I don't see any errors of note in the log, you may just have a bad Steam install, try verifying the cache in case any files need to be replaced. Hope this helps

Hi @Lorenzo & Filippo, can you please take a look here and provide more information from KSP, thank you.

Yeah it needs struts, but don't attach struts to the TR-38-D, that summons the Kraken. The autostruts planned for 1.2 should alleviate this as you won't need a strut on the TR-38-D, or to have them physicsless.

Hi @CorvusCorax, this is likely the known issue with the TR-38-D. It's rare on Linux, but happens on OSX all the time.

Hi @Fastfishy2, KSP should not be showing what you describe and does not for other players, so this is not a know issue, sorry. We will need more information from you to diagnose this, such as your output_log.txt, KSP.log, settings.cfg and your dxdiag hardware report, see here for info on these.

Hi @red_philosophy, are you using an Intel or AMD graphics card with open source drivers? Many fonts will not show due to a Unity bug, but if you start KSP from the command line with this: ./KSP.x86 -force-glcore It'll detect the right version of OpenGL and the saves should be visible. If this works for you consider making a shell script (an executable text file) to start KSP this way for you, like this: #! /bin/sh cd "~/path/to/Kerbal Space Program/" ./KSP.x86 -force-glcore Save it and make it executable in the Properties for the file, and it will start KSP when you double click it.

Hi @kjtyteadad, your graphics card driver is out of date. The last driver that AMD are offering for the old HD6000 series graphics cards can be found here.

Unfortunately "National Space Exploration" is all that would fit.

Name changed to NurgleBurger. PM me as you asked on Saturday and I won't change this unless you confirm you know your login will change. Name not changed as it's too long :/

Unfortunately, Unity3D doesn't have these colour filters built in, they are custom shaders that have to be either written by the devs or added from a 3rd party. KSP is about rockets and little green aliens, instagram style filters are novel but aren't really part of the scope for the game, sorry.

NO! It's me! Next up miiiight be @RoverDude...

Hi @toric5, you should have a logs folder in your Steam folder, but I don't know if any of the logs there will help. Can you post your output_log.txt please.

Hi @rocketman768, please try the unofficial patch here, thank you.

That's good news at least, though why it's such a mess in Unity/Gnome/etc doesn't make sense.

Running KSP in a virtual machine is not supported, and VirtualBox is not designed for this, for example it is limited to 256mb of video RAM. 3D gaming in VirtualBox can be done but you must install the VirtualBox 3D graphics driver (part of the VirtualBox Guest Additions) in safe mode. The error you see is because you do not have a suitable 3D driver installed. KSP will be extremely slow in VirtualBox, no matter what your specs are or what minimum specs KSP has, so if you really really have to use a virtual machine then you can try using VMware Player but again you must install the driver in safe mode, this is also not supported and may not work. But as KSP is available on Linux, Mac OSX and Windows there is no need to use a virtual machine.

Hello @Tirs This is a known issue, and seems to be a bug with Unity3D and some graphics drivers, specifically all Linux open source drivers. If you start KSP from the command line with "./KSP.x86_64 -force-glcore" it should work properly, and you can use a shell script to start KSP with this line for you. Hope this helps.

I don't think this is possible Curveball, sorry, there doesn't appear to be a means to disable sound like there is for graphics ( -nographics and -batchmode )

We get signal. Next is @CobaltWolf

Hi Gfurst, missing menu text can be worked around by running KSP in the same resolution as your desktop in fullscreen, or by starting KSP with -force-glcore But if you can't launch the game it's something else and we'll need your logs.

It does have to be an unmodded file, sorry about that.

Hi @pembroke. The crash is occurring immediately after this. And it looks like it is being caused by an improper screen resolution. I'm assuming you have a dual monitor setup which is unsupported, so can you please try KSP on one monitor, you may also need to delete the settings.cfg in the Kerbal Space program folder to reset KSP to 1280x720 resolution.

An empty saves dialogue could be drivers as well, as it's not just your graphics driver that updates, Windows does too and old drivers can need updating to work well in newer updates of Windows. The only things that stand out are memory and drivers here, it's not obvious why you're having trouble with your saves. I will mention though that KSP does crash, not all the time but it will happen. Edit: Looks like the i3-M370 uses bog standard Intel HD graphics, I think you'll have to contact HP regarding this.