sal_vager

The entire UI including the HUD is being replaced for 1.1, there's no information on specifics such as this, so please wait until the release. Until then you can try updating your graphics drivers, reducing your mouse polling rate and reducing your part count.

Hold your horses Tex, it's probably a typo, possibly of 0.18.0 Forget my head next, can't even remember which version was first on Steam.

Hi Rocketthrust, as you have KSP on Steam, use Steam to update it for you. The Update tab has an option to keep the game up-to-date. And the Betas tab lets you choose the current release (1.0.4) or the last stable release (0.90.0). If you still cannot update KSP you will need to contact Steam support.

The ckan.exe should stay in the KSP folder, and you can start ckan with mono from that folder by first opening a terminal there or changing directory to that folder, then running ckan with: mono ckan.exe Don't put ckan.exe in /usr anything, it doesn't belong there. If you want a shortcut to ckan, make a file containing this: Make it executable (right click, properties, permissions) then double click it.

Hi hargin, I had to remove the fonts as they are still copyrighted despite their ubiquity, if Wikipedia has also removed their links then we are reduced to the mscorefonts installer or the winetricks EU-fonts pack. If you have text already you do not need to install the fonts. If you are using the settings.cfg from before you used LC_ALL=C it may be corrupt, so delete it as this forces KSP to make a new one. As you are using French you likely are using an Azerty keyboard layout, this is known to cause problems with KSP but there is no fix that I know of, and the only workaround is to change the layout to Qwerty. Other than that, the alphanumeric keys should be working fine in the settings screen, and are assigned by default to action groups 1 to 10, you can test these in a sandbox game if you have not yet unlocked action groups in career.

The rovers are fine

Glad it worked, and thanks

Okay, your log contains this. And your save file contains this. So either install module manager or edit the save to this. Then it'll be fine

This is one of the problems, old unsupported versions floating around that may not even work with the current release. Or no licenses which is why it's very important to have a license in the download, though that can be removed, thankfully the KSP communities are good at spotting rebranded mods. Not to mention advertising revenue from others work, or potentially gaining access to your KSP forum or store account if there is a sign-in and you use the same username and password. Plus I hope anyone who does use some of these sites has an up to date anti-virus, I'm sure Curse has protections in place as a standard duty of care for their users, and Kerbalstuff has a reputation to uphold so I expect protections are in place there as well.

Pinecone, please see this thread. We will need your output_log and your save file. We will also need to know if you made any changes to KSP since it was last working.

Hi Pinecone, did you have module manager installed?

Please upload the persistent.sfs beelzerob, you can put it on dropbox.

Well that's interesting, but may not be much help as Unity uses a custom build of the Mono runtime, according to this page it's quite old and 'only slightly modified'. I don't recall anyone successfully replacing Unity's Mono with the standard one, if you have Mono installed you should have '/usr/lib/libmonoboehm-2.0.so.1.0.0' which all the various libmono symlinks link to, but I just tried putting a symlink to it in my KSP_Data/Mono/x86_64 folder and . Unity 5 doesn't use a newer version of Mono, and it looks like Unity will eventually stop using Mono, making this issue resolved by default. So the only option for now may be to upgrade to a 64bit version of Linux, you need to check if you have a 64bit CPU first, to quote cantab: 'uname -a' will print your system information, 'uname -p' will print the CPU type only, if it prints 'x86_64' you're able to use a 64bit OS, and both Linux x64 and KSP x64 are extremely stable. I don't know how easy you find reinstalling an OS to be, if you have everything in one partition you will need to back up your /home folder at the very least, if /home is on another partition it should be untouched (and it is good practice to keep /home and / separate, this can be done when setting up partitions during install). It's also possible to install the 64bit OS alongside the current OS if space permits, the existing partition would be automatically resized.

I have removed the poll for you.

There is the bug tracker , though I'm unsure if this is a problem that can be addressed if no means to reproduce it on others computers can be found, it doesn't help that the devs all use Windows and that the Linux Unity editor is still in beta. Is your CPU 32bit? the logs are no longer accessible so I can't check and I'm wondering if it's worth updating to a 64bit version of Linux if the PC can use it.

Only thing I can think of is that there's so much UI clutter that the mouse events aren't being registered, it's known that KSP has UI problems in Unity4x, and all the additional UI elements added by mods means there's more calls to update the UI. A badly made addon UI or modified action menu can also cause lag due to excessive redraws. If you take a look at the support stickes and provide the necessary logs then people may be able to see if something is going on, there may be a lot of logspam exacerbating the issue. It may also help to reduce your mouse polling rate or DPI, as that can also cause issues, check your mouse software and OS documentation for how to do that.

Hi Psycopyro, retreat several meters then try again, if a docking failed or the ports were undocked there is a minimum separation distance before they rearm. Also, there is no actual requirement to target docking ports or to control from specific ports. If it still doesn't work, open the debug log with Alt+F2 and check for error messages.

Yeah it's to do with how RoverDude programmed it, there's a bug issue open here on the tracker. Link to tracker issue 5209. From what I understand, ore is extracted in batches and processed behind the scenes, especially when using warp for any length of time, but this is not clear to the player. If you could add your info to the tracker issue it'd help with having this changed.

Unlike planetary resources, asteroids deplete over time.

This is controlled by the vBulletin double post options to prevent multi-post spamming, and is set to 30 minutes. So to avoid it, wait 30 minutes.

Very, nice But it's more a fanworks thing really, and is likely to rile the Kult of the Kraken. Moved!

It does look to be crashing because of running out of memory, if you lower the texture resolution it should help prevent this, there's also an addon called "active texture manager" that can reduce texture size and avoid the crash.

I can attest that per-application graphics settings at the driver level are perfectly fine on Linux, perhaps Linux and OpenGL are a little more stable than what some are used to with other platforms. As I recall from my Windows days, forcing any graphics driver options was hit or miss as to whether it would actually work with any given program, I have not run into this yet with Linux. It also offers more control than those exposed by the Unity engine, which is a nice bonus

Hi Zmell2, there's a solution for this issue in this thread

Well, you may have to stick to smaller craft, I can't see anything obvious in your log or dxdiag, and the process list is incomplete. If you're running anti-virus you could whitelist KSP, that will stop the AV from scanning it and slowing KSP down, also avoid any programs that monitor the games memory, there's a few free Steam programs that do this and they have been causing problems. Something else to try would be setting the process affinity, as KSP is made in the Unity3D engine, and as Unity cannot split the physics into individual threads, KSP doesn't really make full use of multiple cores and can work better if set to a single core. Windows has a tendency to dump everything on core 0 (the first core), so setting KSP to core 1 to 3 (I see you have 4) can help.