sal_vager

Hi BlahBlah84, try reducing the texture quality in Settings, also please post a dxdiag log.

Sorry to tell you this Branjoman but Yukon0009 is right, your throttle limiter limits the thrust from your engine, setting it to zero effectively prevents the engine from working. Right click your Skippers in the VAB and slide the limiter back to 100, save your craft and launch, that will fix it.

It's probably a controller so if you have a joystick or gamepad plugged in try removing it, if that is not the case and you are using addons try removing them and see if the problem goes away.

Hi limeindy, your logs show that KSP could not access any memory. Please try setting all your graphics options to their minimum and reverting to launch again, if it works you may want to try the active texture management addon.

You can do this via the terminal, it's easiest to just open a terminal in the KSP folder and paste that line into it. Or you can make a script containing this. #!/bin/bash cd "/path/to/your/Kerbal Space Program/" LC_ALL=C ./KSP.x86_64 And make it executable. It'll start KSP and force it to use the posix standard for language, some system languages swap the , and . causing all kinds of issues.

It sounds like a bad download to be honest, I'd try a new one.

Hi Nikola, you are going to have to edit your Windows registry to fix this, you need to find "HKEY_CURRENT_USER/Software/Squad/Kerbal Space Program" Change Screenmanager Resolution Width and ScreenManager Resolution Height to decimal, and put in the width and height you need, I suggest just resetting them to 1024 by 768. If your taskbar is in the way, you'll need to hide it. Don't forget to check that your desktop resolution is at its highest setting, and back up the registry first.

I'll try to think of something, it may be that the original fonts that Windows needs to repair your font cache are themselves corrupted, but they aren't easily available. You can still get the old Microsoft core fonts here though, losing fonts happens to Windows and OSX from time to time, and I find the best fix is to replace them completely.

Okay, KSP does use your system fonts for some things, specifically Arial and Arial Bold, and if these are corrupt KSP won't load them. This page has some info on restoring fonts on Windows 7. Let us know if it works.

Yeah it should say something like "Oryip@computer:~/Path/To/Kerbal$" in your terminal, if you opened the terminal from the menu it'll say "Oryip@computer:~$" Use the cd command to change directory.

Unfortunately that error is "normal" and not part of the issue, and the log is not showing any problems, do you have text missing anywhere else and is this a clean install or a previously modded game?

Did you miss the space? Copy the following line and paste it into your terminal. LC_ALL=C ./KSP.x86

Please try starting KSP from the terminal with "LC_ALL=C ./KSP.x86" Make sure you are in the KSP directory, it's easiest to open the terminal within the KSP game folder.

We're watching, and Xyplos is correct, the thread has been splitting into two for the last few pages but is still largely on-topic, so please put aside your differences and keep to the topic of the thread, thank you.

Okay well you had them working, and the lines do work for other people, so we need to find why they do not work for you, can you post your catalyst settings please. Please delete your settings.cfg and try starting KSP with "LC_ALL=C ./KSP.x86_64"

Have you changed any settings, in KSP or Catalyst, since you got the lines working again?

I'm glad it's fixed Have fun in space!

This would be good, and even better if decoupled stages kept the name, also I've popped this over to Suggestions.

That changes a few things, though it's still worth testing the open driver by uninstalling the proprietary driver and rbooting, and also trying the updated AMD driver which is up to 15.7 now and is available as a .deb, so can easily be installed using Ubuntu software centre or my preference, GDebi, which can be found in the repos. Also, if you have changed any of the default Catalyst settings such as anti-aliasing or forcing mipmaps, try disabling them.

Well this is interesting, you have virtualbox modules loaded, I never managed to get KSP to run in a VM but Linuxgurugamer got it working in VMwarefusion. So I'm wondering if this might be a graphics driver error, and it can't handle the transition from the close-up orbit lines to the ones it uses further out, different shader maybe. Can you try the open source driver with the VM? See if the lines work, though KSP may be too slow to play that way, if that does work there may be a newer (or older) version of the current driver you can try. Failing that, you might want to give VMware fusion a go as it'll use different drivers to communicate with the host graphics card, or try a dual boot instead.

Any further pseudo-scientific, anti-scientific, creationist or conspiracy theory off-topic posts will be removed and the poster will be warned/infracted, if you want to discuss such things take it to PM or another forum, thank you.

Hi Rocketmaster, please upload the logs anyway just in case, and please provide your system specification, a hardinfo report should be enough.

Great, glad it's sorted, and now I know another way Windows KSP can go wrong

Could be the driver yes, your dxdiag log might tell us more, and you can try forcing Dx9 with the "-force-d3d9" command line argument, the easiest way to use this on Windows is to make a shortcut to KSP and add that line to the properties, target box I think. I suspect your driver has some global options, and is set to use Dx11 system wide.

Well that is interesting, as that's the only time I've seen this, can you put the contents of your KSP.log on hastebin please.