Search the Community

I am trying to update my 1.0.4 to 1.1.3, on a Mac, and it is not going well. When I unzip the 1.1.3 archive into my applications folder, it creates a KSP osx_2 folder inserted of updating the KSP osx folder with it's Saves and mods history. If I unzip it into the KSP osx folder, it creates another KSP osx folder nested within it. I'm afraid that if I start individually replacing folders and files, I'll mess it up badly. I guess what I am looking for is a patcher, not a new install, but I didn't see a patcher available, except for Windows. What is the upgrade procedure?

Hello, I've got an annoying problem: I built a big ship in ksp 1.1.3, but bizzarre wheels and wings and incompatibilities of mods made me return to 1.1. Problem: I don't know how to convert my craft to ksp 1.1 because I've installed same mods, they work, and when I put the 1.1.3 .craft file into 1.1 ships/sph folder, it says me that the craft is incompatible with this version of ksp. halp plz I tried all day to fix that, but didn't succeeded

I've been experiencing some problem with the landing legs, not landing gear sorry. The problem is, when i turn the landing leg it goes inward and turns slightly and i just can't seem to get it to go outward into the landing position i guess. Although i have installed mods which include... TAC Life Support, Tweakscale (just installed today) and... actually that's pretty much it.

For the past month or so, I've been doing crazy thermal extremis testing in 1.1! I built a little testbed of a z200, two little solar panels, an OKTO core, a nuclear engine, and an NCS adapter with only 8 units LF in it, then attached various cooling structures to it, saved those as new craft, and launched them to orbit on a modified aero-equis to test how well they can radiate the heat produced. Methodology was to turn on infinite fuel, burn to an internal temp 1100 in the probe core, record burn time by comparing MET to MET at start of burn, then cut throttle to see if it can coast cool before the core hits 1200 and explodes. Most burns were angled to escape Kerbin retrograde, so as to delay NaN-spam from hitting a solar escape. A few actually reversed solar orbit and hit escape anyway, and were turned around to re-capture and restore performance. Tested where a pair each of Structural Wing Type Ds, wing strakes, gigantor solar arrays, Large, Small, and Edge static radiator panels, a pair of Small thermal control systems, and single front-mounted Medium and Large thermal control systems. On to the results! Keep in mind these are tests of a tiny, mostly-engine ship with a tank perpetually almost out of fuel, and thus a terrible heat sink. As such, the given times are to be regarded as impossibly extreme lower bounds. Also, to explain the odd numbers to any flux-accountants, the active radiators would steal internal flux from the engine. It was indeed producing 7471.27kW for all tests, though. Has anyone done similar tests using drills/refineries as heat sources?

The first video in my KSP 1.1 Career Series. In this part, we launch our first rocket and get to orbit.

In 64-bit KSP 1.1, with only one mod (the docking alignment indicator) - launching a fairly large rocket (174 tons in 6 stages): If I save and then attempt to load the vehicle, it shows up on the vehicle list as "116 parts in 13 stages", but there are only six stages on the sidebar. I click "launch". I go to the pad. If I don't do anything for a few seconds, the spacecraft settles in. It appears to be intact, but the first three stages disappear from the stage sequence on the left. If I activate the staging sequence, I get the fourth stage. If I hit the "stage" button before the rocket "settles in", stage one fires as it should, but controls then appear to be locked. I have checked visually - in both of these scenarios, the rocket appears to be intact, just the controls are misbehaving. If I leave the pad after the rocket settles in, then come back, the top half of the rocket falls to the pad immediately upon my return and lights everything on fire. I do not see the bottom half. The spacecraft in question has three probe bodies and no crew. I have tried quitting and reloading, shuffling the stage sequence, and similar with no apparent effect. Has anyone seen similar behavior? Any idea how it might be fixed?

I've placed my first space station in orbit on my new 1.1 career. I have a science lab crunching away at some data and I noticed that apparently in 1.1 once you put an experiment in the lab you don't get it back to be recovered or transmitted. My question is, once the lab finishes processing the data from these experiments, should I transmit it or recover the lab? What made me doubtful about this is the following note in the changelog: "Labs with science can now be recovered for science." So will i get the typical penalty if I transmit the generated science instead of recovering it, or does this just refer to recovering experiments that weren't processed? Thanks in advance.

Hi, the last few weeks have been a rough time for all modders. There were, or still are a lot of things to update and fix for the big 1.1 update of KSP (and the subsequent patches). Naturally, also the number of bug reports for the mods increased. This is totally okay, there are always new bugs introduces by such a big update. But lately, an increasing number of reported bugs are only caused by the fact, that there are still mods installed, that do not support 1.1. or are not cleanly installed/updated (as in remove the whole mod folder before installing the new one). These bug reports cause a huge overhead for us and are frustrating because they are completely avoidable. We invest valuable time to find out what is wrong with our mods, only to find out that the mod user didn't even invest any time to make sure the mods are properly installed (at least it feels like this). So before you report a bug, please Make sure that ALL the mods you use are compatible with the version of KSP you use. Remove the old folder(s) of a mod before you install a new version. If you use CKAN, install the mod manually into a clean (CKAN free) version of KSP to verify that the bug is caused by the mod and not CKAN. This will save a lot of time for both ends. We modders do not have to crawl through many log files and the user can use the mods without problems (and do not have to wait for the modder to tell them what is wrong)

THIS THREAD HAS MOVED! CLICK HERE: Kerbiting System This planet pack, which is in very early alpha phase, is a planet pack that rearranges all the planets in the stock Kerbol System. In later versions more planets and moon will be added, the star will change, and a lot more will come! This is what I let you guys decide. I like to make a planet pack which makes people as happy as possible. For that to happen I need your advice on what to do/add/edit. For now this is all you will get. I'm working hard on it and next version will come out soon! Very important to know is that this is my first work. So if any bugs are encountered, report them immediately! Let me know what you think and give me some advice on what to do next! I'll make a poll to know what you guys want to see first/next. Changelog: Alpha v0.2: Added correct science values for all the planets Alpha v0.1: All stock planets rearranged Given some different properties/orbit settings for some of the planets That's all for now. Images: POLL: Strawpoll Installation instructions: Just place the "Kopernicus" folder inside the "GameData" folder. DOWNLOAD: Kerbiting System Download DEPENDENCY: Kopernicus ModuleManager Thanks for downloading and have fun with my work! Big credits to the developers of Kopernicus and ModuleManager of course!

Hi, this is just a quick post. When I updated to 1.1 I got this horrible terrain glitch, and every texture is gone, unless i zoom out very far away. My game was modded, but I uninstalled all of them, reinstalled the game around three times and still get this. I updated my AMD drivers, but it didn't work. Anyways, I just hope someone can help me. http://imgur.com/Dnset0d http://imgur.com/5u5wbnE

I had a slight issue whilst building a small shuttle. I was trying to place a launch clamp on my craft, and my cursor slid onto the T-1 Toroidal Aerospike "Dart" Liquid Fuel Engine i had on the bottom of my craft. i thought this would be no big deal, until the game froze and wouldn't let me open the Task Manager. I was unable to switch to any other windows, so i had no choice but to forcefully shut down my computer. This was a bit of an issue for me, however I hope it will not happen again, and will be fixed. Directions to recreate: 0. Ensure all programs are not running, or have had their data saved. 1. Launch KSP Ver. 1.1.0.1230 2. Go to the VAB and place a Fuel Tank and T-1 Toroidal Aerospike "Dart" Liquid Fuel Engine (tm) on it. 3. Obtain a TT18-A Launch Stability Enhancer and hover over the T-1 Toroidal Aerospike "Dart" Liquid Fuel Engine. 4. For me, this froze my game, and forced my to shut down my computer. As the computer was force shut, no error log was produced, so I cannot include it here. DxDiag "important bits" Processor: Intel(R) Core(TM) i5 CPU M 450 @ 2.40GHz (4 CPUs), ~2.4GHz Available OS Memory: 3884MB RAM Windows 10 Home 64-bit (10.0, Build 10586) (10586.th2_release.160126-1819) DirectX Version: 10 I hope you can recreate this, and tell me what went wrong.

Love the new cleaner map view where you don't see the orbits of ships until you zoom into the planet. Then they fade up nicely. But the fade up takes way too long. I zoom into a moon and think "Where are all the ships ... oh there they are." is there a text file I can edit to make that faster?

Hello everyone! I love Kerbal Space Program but there's something missing in my opinion. I've always wanted add-ons that added rockets and space missions from the real world. Unfortunately, I couldn't find these anywhere. So, I decided to take it upon myself to make these add-ons starting with the Soyuz add-on!!! I just started making this add-on, so there's barely any work done, but it's coming. After this I'm definitely not going to stop making add-ons. There's still a lot of stuff to be made, like the Space Shuttle missions and the ISS Modules. Not only that, but I'm also enjoying the development of this add-on a lot! Here are a couple of screenshot of the only part that can actually be used already: The main tank! Thank you for reading! Hopefully you guys are as excited as I am! The_Boss-Ted

KSP 1.1 added a nifty new feature where orbital trajectory lines are faded to indicate the direction your craft is traveling along them. This gave rise to some heated debate as to which way the line should diminish, so Squad obliged us with the ability control it ourselves: Now that we've had some time to play with it, I'm curious which choice is winning out with fans of the game.

So I've been running the hack basically as soon as I installed my first mod. It ran beautifully, and It never crashed on me. Now, trying the official 64bit version of KSP, the game crashes every few hours or so. So what do you think? Oh, and I IMPLORE YOU to not merge this into the 1.1 discussion thread, because it's an undecipherable mess after all the threads were merged.

I am using KSP 1.1 64bit on Windows 64bit. At the bottom of the post I'll provide a link to my output log and a spoiler of the mods I am using. I wish I was able to fix this or figure out the issue myself, but I haven't found any similar problems online with solutions, nor am I smart enough to figure out what is wrong. It doesn't help that I have a hard time understanding the output log and don't know most of what it says. I don't know what else I can do to assist the people willing to assist me other than describe the problem Title says it all; While in the VAB, I periodically have the inability to click on parts. It happens fairly often, enough that the game is basically unplayable and I am going back to my 1.0.5 install until I can get help with this. Right click always works, as does shift click it seems. But when it happens, I will but unable to click on parts so that I can move them or delete them. This is not the case if I want to add new parts from the left hand part where all the new parts are. But when trying to interact with already placed parts, I periodically am unable to click on them. It is very frustrating, and I simply don't have a clue as to what could be wrong. I have looked at the exceptions thrown in the output log but they mean nothing to me, I don't understand this language at all. Also, before anyone asks why I have three mods that are for 1.0.5 and suggesting they are likely the cause of this problem... I have already removed the mods in hopes they would fix the problem, but they didn't. I have 1.0.5 versions of KSP Better Fairings, Stockalike Station Parts Expansion, and Near Future Spacecraft because they have not been upgraded to 1.1 yet and because I have 2-3 parts in 2 vessels already launched and in space. They won't load if I don't have the mods installed, and seeing how it didn't fix this issue, I reinstalled them after making sure they weren't the cause of this VAB editor problem. EDIT: Something kind of important I forgot to mention. This inability to click parts usually lasts for a good 30-60 seconds before it works again. This is the periodic event that I constantly experience, and is the reason why it's so frustrating. I'd be very appreciative of any help received, thanks. https://www.dropbox.com/s/84f6voyhs0kss6q/output_log.txt?dl=0 PS: I know my laptop sucks and can barely run KSP; Intel integrated graphics, 1GB VRAM, and 4GB RAM are not exactly my cup of tea, but I can't do anything about it. Fortunately I will be spending ~$2000 on a new gaming rig in ~3 weeks.

Pretty much what the title says. It's broadcasting its findings via @MuffinWatcher to #KSPModUpdated. The bot checks for updates every 15 minutes. It uses CKAN internally so it'll only see updates for CKAN-enabled mods.

Allrighty. It's been a while, now, hasn't it? I'm thinking of doing a new project. I hear 1.1 has dropped, and that there's optimizations in there that'll let me up my part count some. Maybe I can finally breach the 100k part barrier. Who knows. I'm probably going to put together a new Arkingthaad tower lander. The biggest one yet. So my question to you all, is, what should I do with it? What should I put on it? Is there any thing anyone wants to see, specifically? I've been out of the loop for quite a while, now, so some blundering is to be expected. Give me your thoughts, please!

I just realized that 1.1 was available in the options for steam, so I downloaded it. I also tried to have CKAN update all my previous mods, but it refused to do so because cryoengines is incompatible so every time I tried to update mods that were vaguely related it threw up an error and wouldn't let me. I deleted CKAN, my mods, and re-downloaded CKAN and compatible mods through it, as well as a couple that it didn't have or claimed where incompatible when they weren't (no fault of its own there really). Only reason I'm saying all that is because it could possibly be somewhat related. Maybe. In any event, the problem I'm having is that what appears to be an IVA interior is placing itself onto my command pod at launch, and is even visible in the VAB (below the actual vessel- at launch, the command pod is fine for a second or two, after which the IVA part clips into place). I even checked the SPH; same thing. Images will be near the bottom. Quick descriptions: 1: Showing the IVA part at the bottom of the VAB. 2: Showing that the command module still shows up fine in the VAB. 3: Just after the launchpad loads, command module in place. 4: A few seconds later, the IVA thing clips in. Some things that may be important: I'm running the 64-bit version, I have it set to borderless fullscreen because that's how I like it usually. I'm probably just going to uninstall KSP entirely and reinstall it, see if that fixes it, but I still figured I may as well put this up beforehand just in case.

On a dual-core i7, 8MB RAM, switchable graphics with Intel HD 520 and AMD R7 360, a clean install of KSP 1.1 stutters, where 1.05 is easily playable. On both 32- and 64-bit builds of KSP 1.1, + Loading Systems takes 230 seconds (50s with 1.05) + Main Menu stutters about 1/2 second just before the sprites come into view + Transition screens, black with 'Loading..' in the corner, take 20 seconds (5s with 1.05) + In the scenario "EVA over Kerbin" panning to show the planet stutters for about 5 seconds; panning in camera-view in often stutters about 1 second + Transition from map-view to camera-view takes 1-10 seconds (less than 1s with 1.05) + Esc menu -> Settings -> Accept, with no changes to any settings, pauses for 30 seconds before the Esc menu is responsive + Main Menu -> Quit takes 20 seconds before the KSP window closes This felt like garbage-collection, or file-system timeouts. Things I tried with no noticeable help: reducing graphics quality to minimum, setting the graphics to use AMD only, ensuring the same file-permissions on 1.05 and 1.10 install directories, turning off the send-progress-to-Squad option, pausing Windows Defender, setting the KSP option to use LEGACY_SHADER_TERRAIN, ... Any suggestions? Logs and DxDiag are here.

The challange is: Go to Duna,The mun,Minmus,Eve,and Moho and go back to kerbin and land safely Mods Allowed: KW Rocketry AIES Aerospace and, mechjeb(only to make maneuver nodes).

I'm having a problem where the steerable landing gear on my planes overstresses at the slightest touch, preventing me from launching planes. This happens in both x32 and x64, in Windows. I couldn't accelerate planes at all on the lvl 1 runway, as it was so bumpy that it immediately exploded. Even on the lvl 2 runway as soon as a plane reaches about 100 m/s it overstresses and explodes. Latest attempt the landing gear overstressed as soon as the plane was placed on the runway, before I even started the engines. Any clues what I might be doing wrong, or if anyone else experienced that? Planes are very simple, 30 parts only.

The title says it all. It's a jet capable of taking off and landing vertically or conventionally. It has a Narrow-band scanner in the nose cone! It's decently maneuverable, but you can always boost it by turning on the VTOL engines. It also has two drogue chutes and flaps to slow it down during landing. DOWNLOAD Basic information Name: KAI/KD CF-1 Total mass: 10.0t Height: 4,2m Width: 8,9m Length: 11,0m Part count: 73 No. of engines: 7 (1x Whiplash + 6x Juno) Resources: Liquid Fuel: 360 Electric Charge: 50,22 (Mono Propellant & Oxidizer tanks empty to save weight) Action Groups Images Front view in the hangar. (The narrow-band scanner is slightly visible) The VTOL engines are fitted in a 3-3 configuration on the underside of the aircraft.

I actually have a long list of real suggestions for this game, but all of them take a back seat to this. I was deliberately waiting for the RELEASE of 1.1 because I wanted it to be right. WHY ON EARTH DID YOU ROLL THIS OUT? I'm a software developer myself, so I understand. You needed to call something 1.0 and get out of the prerelease section on Steam. I got that. But we're passed that now. And there is NO reason to release this stuff until its SOLID. You have *users* out there now (not beta testers) and you're ... (self-censorship) ... aggravating us. Just stop. Go attend a 12-step program for people that can't stop releasing buggy apps. Let the next two (or 4) builds be nothing but bug fixes. PLEASE.

Hello guys, I have updated to 1.1 the day it came out and waited for the mod devs to update their mods for 1.1 full release then I went to play in career mode. I was playing fine for the past 2 days but this morning, it said my career file was incompatible with this version of KSP... what do I do? I don't want to restart another one so is there any way I can fix this? I have a few mods installed and all of them except for kerbal engineer are up to date. Actually, Kerbal engineer is bugged because I downloaded the 1.1 update for it 3 times and installed it and when I launch the game it still says that I need to use 1.0.5 with this mode because I have an older version. Can I don anything to fix this? And will my career file be re-enabled in the game afterwards? If you need to tinker with it just tell me ad I'll attach it here. Thanks in advance, Cheers I have to mention that only my career file got "corrupted" and not my sandbox file which is really liquiding me off. It may be due to the 20 or so vessels in flight in career whereas I have none in-flight in Sandbox but still, this is making me lose the motivation to play KSP now...