sal_vager

Hi @brownsavo, is this in Windows?

It sounds like you need to reinstall your graphics driver then reboot, your dxdiag hardware report will tell you exactly what driver you have, if you run dxdiag from the start menu you can save the report, post it to pastebin.com then link it here for us to take a look.

Is anyone else seeing this? I just tested it here and my existing saves and new saves are showing the correct hiring fee. Tested on Linux 1259 (1.1.3) matthew49, we need more info from you on this issue, just saying it happened is not enough.

Thinking about it, though we can have (and have had) too many pinned threads, threads like this do need to be easily accessible to new members.

This thread was moved here from KSP Discussion, but unless someone can reproduce this we'll just be chasing shadows. I'm going to close this thread, as while it's not impossible for this issue to exist I don't want people wasting time without logs, saves and reproduction steps.

Here's some information on 32bit hardware. For our purposes, 32bit KSP can use only about 3.5 gigabytes of memory, and this can be even lower on some 32bit operating systems. KSP 64bit can access much more memory, up to 16 GB has been reported on Linux. As for your issue it may help to know why the 64bit Windows version of KSP has a different KSP_Data, when Squad exports KSP from the Unity3D game engine on Windows they have to do it twice, once for 32bit, and again for 64bit. On Linux they only need to do this once, and Unity makes both a 32bit and a 64bit binary. Also on Apple OS X they only need to export once, and the OS X binary is universal, it will automatically run in 64bit if it can. So for Linux and OS X the KSP_Data is exactly the same, but on Windows one version will have the 64bit tag, the other will not.

Monitor the heat to start with, you can look up your CPU online to find its operating temperatures, as long as it stays within those it should be fine and heat can be ruled out.

I'd check that the fans are turning fast enough, there's one in the power supply as well but it's inaccessible (anti tamper stickers) and would not be safe to mess with due to the risk of electric shock from the capacitors, even when disconnected. Though even if the fans are okay the CPU can still overheat if the cooler has a poor contact, that can happen with old PC's if the thermal paste has dried up. Checking the temperatures in software would reveal if it's the CPU overheating even after a clean.

Hi @KSP Rules, this appears to be a problem in Windows itself, as searching for the problem signature is showing many different reports of this issue, none mention KSP. If you are overclocking your PC try resetting the bios to its defaults, and ensure that plenty of air is entering and leaving your PC's case, you can also check your CPU temperature in the bios and with monitoring software. Most likely your CPU fan is dusty and needs a clean.

You're unable to bind the thumb sticks or triggers to the pitch, roll or yaw axis @RetroJay? Afaik that should work, the d-pad as well, should be bindable to an axis. Unfortunately it seems that we can't use analogue input for the key bindings, but anyone here can tell you that KSP is long overdue a replacement to Unity's basic input system.

Try keeping the window in focus while KSP loads, this suggests you are alt+tabbing away from KSP. Also please ensure your graphics drivers are up to date, you may need to reinstall them if Windows is misreporting the driver version.

Forward slashes are acceptable in Windows filepaths, they are used for cross-platform compatibility as backslashes are Windows only. Can you test KSP with the -force-glcore or -force-d3d11 command line arguments? If they work it could reveal an issue with your DirectX install. Another to test is -force-gfx-direct to force single threaded rendering.

If you started KSP using the KSP.x86_64 binary in the games folder or via Steam using %command%_64 it is the 64bit version of KSP. The lack of x64 on the main menu on the Linux version doesn't mean anything, and cannot be cited as proof that the game is running in 32bit. If you're so concerned then load up KSP with mods and watch as the memory used goes over 3.5 gigabytes, which won't occur with a 32bit application. It's 64bit

Not a bad idea, though the format of the page is poor since we lost the goto tags :/

Hi, please take a look at the 1.1.3 release notes If the editor is using a lot of CPU for you try disabling the space center crew.

Hi @tsaven, can you try disabling Nvidia 3D Vision please, I have heard of it causing instability with KSP.

How many buttons does your stick have? There's a hard limit in the Unity engine of 20 buttons that can't be bypassed, but in practice it can be lower from stick to stick. Some sticks just don't work, I don't know why, of my controllers I have one that just doesn't work which is a shame as it's a set of CH pedals, and they'd be great in KSP. Basically, the stick needs to work with Microsofts Xinput on Windows, if it doesn't, well you can guess. On OSX and Linux Unity uses rawinput, and there's no way to choose. Supposedly as long as Unity detects the stick it should work, the sticks name is used by Squad to remember axis/button bindings per controller. Also note that hat switches are usually axis, not buttons, so don't forget to calibrate the hat as well, and use it as an axis, not a button.

Hi, if you are using a shortcut to KSP your Physics.cfg and Partdatabase files may not be loaded, please try the KSP.exe directly. If you unzipped KSP to Program Files it may be unable to write those files, please unzip KSP to C:\Games instead and run it from there. If these don't work you may have a corrupt Physics.cfg or PartDatabase.cfg, deleting these will cause KSP to make new ones, this should solve your issue.

Hi Wilson wilson, have you tried -force-glcore yet? -force-gfx-direct is the old Unity4 command, it still exists but has been superseded. -force-glcore will force the Unity5 engine to redetect the versions of OpenGL on your system, and by appending a number you can force a specific version, -force-glcore33 will force OpenGL 3.3 for example. Also, if you're using the fglrx driver from the repository please note that it is rather old, and you would be better off with the driver from the AMD website.

Heat will still conduct into cargobays from outside, they will only protect from atmospheric convection and from radiation, so some heating is expected even inside a bay or a fairing.

This is news to me, unless your PC is slow. If your bind axis dialogue is not appearing then something is broken, possibly it is being dismissed immediately so you can't see it, and to diagnose this any further we will need your logs and system information, please see this thread for details.

It does not, the KSP_Data on Linux is good for both 32bit and 64bit, only some Steam plugins for mono change so only those are in the KSP_x64_Data folder, so KSP will first look in KSP_x64_Data, load those files, then load the remaining assets from KSP_Data. You will have two binary files for the 32bit and 64bit versions of KSP. KSP.x86, this is 32bit. KSP.x86_64, this is 64bit. Steam is 32bit and will start KSP.x86 unless you tell it to start KSP.x86_64 using %command%_64 By putting the Windows KSP_Data into your Linux KSP_x64_Data KSP will load that instead, and could cause bugs if any of the data is different. These are the files you should have with a new install from Steam.

Okay PM me when you're online, this will change your login.

Movido

So this is intermittent? I have not seen it yet. Guys if you could open a bug report on the tracker and add your saves, logs and settings.cfg it'll help a lot.