Squelch

We are currently looking into this, and thank you for the detailed issue report on the bug tracker to you both @Nachbar and @JimmyR

A configuration entry is missing for the 5m fairing, and we'd like to offer an unofficial workaround in the meantime until the next patch. Close the game. Find the following file and open it in a text editor. "PATH\TO|\Kerbal Space Program\GameData\SquadExpansion\MakingHistory\Parts\Payload\fairingSize4.cfg" Add the following line between the closing curly brace and node_stack_interstage01a rescaleFactor = 1 The result should look like this ... MODEL { model = Squad/Parts/Aero/fairings/AutoTruss scale = 4,4,4 position = 0.0,0.22,0.0 } rescaleFactor = 1 node_stack_interstage01a = 0.0, 2.17, 0.0, 0.0, -1.0, 0.0, 2 node_stack_interstage01b = 0.0, 2.27, 0.0, 0.0, 1.0, 0.0, 2 ... Save the file and the fairing shell will no longer have the gaps when used. This is an unsupported workaround, and If you are not comfortable with editing files, then please wait until the next patch.

We have taken measures to avoid this in patch 1.4.2. The cause is still unknown, and existing accepted or generated contract offers made before the patch may still be affected. Please check the behaviour for new contracts in 1.4.2, and if it still happens, a savegame from just before it is seen would help immensely as well as the logfile for that game session.

For anyone still experiencing this problem sporadically with new virus definitions, please follow the steps recommended by Microsoft to clear cached copies of the virus definitions outlined in the marked answer. We have been monitoring this closely, and can confirm that no further detections have been made by us since performing those steps despite some later sporadic reports.

This thread was originally for MacOS, and has been confirmed fixed on that platform. We have now found a fix for Linux Ubuntu 16.04 but too late to fully test for side effects before the 1.4.2 patch was released. It does look good so far and will feature in the next patch release all going well. For now, it will have to be the workarounds with AA and sizing of the window or screen resolution I'm afraid. Please feel free to start a new thread for this problem on the Linux platform. [Edit to add] I have marked @henr1k's reply as the answer to this support question.

Hello all. We are aware of this problem and know that it affects some openGL systems. It is not apparent on all, and can also vary in severity with screen resolution or window size. We are working on identifying the cause and a possible solution. Your reports and feedback are already helping immensely. Player.log is always very useful in identifying what hardware combinations are most affected, so while they might be error free for this particular problem, the detected GPU capabilities are.

@JEB'S DESTINY I see from your log file that you are running the 32bit version of the game. Are you using a desktop shortcut to start KSP by any chance? What are your KSP graphics quality settings please? Could you try running the 64bit version to see if the situation improves? From the Steam Client, 64bit is now the default.

Hello all. Windows 10 Defender was detecting Assembly-CSharp.dll as containing a virus. This has been found to be a false positive. The file was being detected as having a virus on the following previous definitions 1.263.580.0 1.263.582.0 1.263.580.0 release time corresponds with the first reported cases. Virus definition 1.263.585.0, just released, does not quarantine the file. Please be sure to update Defender's virus definitions. Source: https://www.microsoft.com/en-us/wdsi/definitions Results of the analysis: https://www.microsoft.com/en-us/wdsi/submission/bdea1058-efcc-4c43-8051-22cfe1139e81 Update: If Defender continues to flag the file as containing the Critet.BS trojan, the following advice comes from the Microsoft Defender team after the file was submitted again for review. Furthermore, you may find that a system restart is necessary to completely clear the problem

That's some great and detailed feedback. Thank you.

Hi there, From your description, you are trying to set the semi major axis using the slider only. The button that displays the value may also be used to enter values directly. I have noted this for feedback and improvements.

Thank you for the insightful report. We are currently investigating this on both platforms. We can confirm that this does not occur in a sandbox game or a randomly selected asteroid, and that it does appear to be restricted to contracts only which is an important detail.

Hello Z.R, Welcome to the forums. Your problem is mysterious. May I ask what your system language settings are please? [Edit] The problem appears to be the keyboard layout. Could you confirm your system input language, and the layout you have chosen in KSP? You may like to try this. Go to the main settings screen. Select layouts and change the keyboard layout to something different. You will be warned that this will change your settings. Then select your preferred layout again, and see if graphics settings are now working correctly.

This change was an unfortunate necessity, and has caused some asteroids to change shape when they have been saved in a previous version, and now loaded in 1.3.1. I have updated the issue with a workaround of undocking the asteroid in 1.3.0, saving, and then updating to 1.3.1 where the asteroid can be captured again.

Hi @orbit.impossible Please could you provide more information? I have attempted to replicate your problem on a clean installation of 1.3.0 and the save loader is working properly. Please could you let us know the distribution that you use and upload your logs together with one of the persistent.sfs files from a problem save found in the installation folder /saves/? Information on where to find these files and tips on how to attach them can be found here:

Hi @biasuz KSP for Windows and MacOS are functionally equivalent. However, due to platform differences there may be some variation in the experience, and as has already been pointed out 10.13 High Sierra with APFS seems to be causing some flicker at present. We are already looking into this. As a workaround, installing bootcamp and running the Windows version should be ok if that was your original enquiry?

This problem has been fixed and is currently available on the Patch Pre Release for testing. https://forum.kerbalspaceprogram.com/index.php?/forum/77-ksp-pre-release/

Hello @EljOt You have supplied only a fragment of the DXdiag report, but I'm afraid to say that your PC may be too far below the minimum specification to run KSP. Please refer to the reporting guide and self help threads for further information

Thanks for the update, and I'm pleased you have it working properly again. FYI the command line for borderless window should be "D:\Games\Steam\steamapps\common\Kerbal Space Program\KSP_x64.exe" -popupwindow

This is the unmodded section of the support forum. Does KSP load correctly without mods installed? As @Jas0n has pointed out, you also appear to be running the 32bit version, so using realism overhaul will exceed the memory that made available. I also note that you are running an older version of the game. It is recommended to update it.

[KSP Version]: 1.1.3.1289 (WindowsPlayer) (x64) ============================== Hi @boolybooly The second log indicates that you may have an incorrect and old version of x64. It should read 1.3.0.1804 (WindowsPlayer x64) en-us I would recommend that you use Steam's verify game files feature to make sure that you have all of the correct and current files for KSP. Open the Steam Client Go to your library Right click on KSP Select properties from the menu Select "Local Files" tab Select "Verify Integrity of Game files" May I ask what method you use to launch KSP - Steam client, a shortcut, or directly from the game installation? To bypass anything else that could be influencing the start up, try launching KSP_x64 directly from the installation folder.

The symptoms described would indicate that you have both the older parts, and the new versions installed side by side. Many of the parts have been updated significantly since 0.23 which was still very much in early development at that time. As @sumghai suggests, it would be prudent to make a fresh installation with the current release which is 1.3.0 and has many more features and improvements for you to enjoy. It would be difficult, and probably counterproductive to try and instruct a selective deletion of the deprecated files. The store does have a forgotten password function that should help you gain access again to download the latest release as already suggested.

[LOG 23:12:43.331] ******* Log Initiated for Kerbal Space Program - 1.3.0.1804 ... [LOG 23:13:07.011] [HighLogic]: =========================== Scene Change : From LOADING to MAINMENU ===================== That is well within the expected load time for the game. [KSP Version]: 1.1.3.1289 (WindowsPlayer) (x64) ============================== This file is not correct both in the file date that you state, or the contents. The correct path for the output_log.txt file is: "....\SteamLibrary\steamapps\common\Kerbal Space Program\KSP_x64_Data\output_log.txt" Depending on where you have let Steam install its library and executing the 64bit version. Can you say where exactly the slow load times occur? From your KSP.log it looks like you enjoyed a period of half an hour gamepaly with all scene transitions executing in a typically expected time frame.

@boolybooly Could you please upload your KSP.log and output_log.txt files somewhere and link them here? There could be a number of causes for the slow loading. It's not common, but we are aware that it happens for some players. Your log should help in building up a picture of the specifics in this case. Thanks. Details where to find the files and some suggested places to upload found here:

The default throttle setting is user definable in settings. This simply makes this zero by default. T-Z-Space will continue to work as ever. You are correct. Glitches be gone!

Ground scatter only comes into effect after the game is restarted. ie Ground scatter is not turned on by default - say after a new installation or settings reset - Enabling scatter will not make trees and rocks appear instantly. Restart KSP and it should work.