Search the Community

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

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.

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.

Dear Squad, I am having some major problems with the 1.1 update. The rover wheel block check seems too strict for me, as it has stopped most of my rovers from working. This is the Ok2Rov, which would have worked in 1.0.5. I needed to clip the wheels in slightly to make the rover fit in a service bay. However, with the new 1.1 update, the check for whether or not the wheel is blocked makes designs like this solid as stone. Can you please remove this feature, or make it less strict? (For example, only count it as blocked if the wheel itself is clipped into another part, and not the wheel assembly.)

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

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.

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.

After updating to 1.1 and reloading my Save, all vessels I attempt to 'fly' suddenly are uncontrollable, show a message about SAS being disengaged, and all engines/motors display a plume of exhaust (but the craft isn't moving). Can't maneuver the ships at all. Also, all saved vessels I load in the VAB show the exhaust plumes from every engine/motor (while still in VAB!). The game is completely unplayable given this. I'm using very few mods and, in fact, none of them are 'part mods' nor any other graphic-changing mods (mainly contract-adding mods). I do have MechJeb installed but I doubt that's related, and of all the mods I do have (7 or 8) CKAN says they're all valid for KSP 1.1. Has anyone else experienced what I described? If so, what can I possibly do about it? Thanks!

I'm trying to do something about my frequent crashing in 1.1. Can't play for more than a couple of minutes without experiencing some kind of weird crash. (Yes, I tried forcing it in OpenGL - just gave me different crash messages instead). So I just want to ask the experienced mod community: which of these mods might be the most likely to cause crashes? My PC has 16 GB of RAM, 4 GB of VRAM and a Geforce 780. I can deck out a game like Skyrim with 6 gigabytes worth of graphical mods, so technically speaking it should be able to handle a lot of extra fluff. Here are the few mods I use in KSP:

Version: Linux 1.1.0 x64 Operating system: Mint 17.1 KDE Mods used: Kerbal Engineer Redux 1.1.0.2 SpaceY Heavy Lifters 1.12.1 ModuleManager 2.6.21 (included with SpaceY) I'm having a weird issue where my computer is unable to open any of my KSP installs, regardless of version, as it won't do anything when I click the executable. This I don't think is a KSP glitch, but I got here through a series of game crashes first. I was re-entering the atmosphere early on in my hard career mode, my vessel flipped over and burned up and I had to redesign a new one. I built essentially a stack of FL-T200s with a Swivel engine on it. That was too tall so I offset it into the pod a tiny bit until it was small enough for the tier 1 launchpad. Pressed launch with Jeb and two tourists inside and the game crashed. ...this is where I didn't make a copy KSP.log before starting it again. I did scroll through and saw a lot of stuff about wheel modules not working or something when the game was loading. Load to menu, open save, click on vessel sitting on launchpad, crash again. Open game again, it loads about 100 pixels tall and I can't click on anything. I tried to resize the window and it snapped to show just the window bar at the top and wouldn't budge again. Closed KSP. Open AGAIN, it instantly loads into the unusable window bar thing and won't work. Getting desperate, I removed all my mods and tried to launch on both x86 and x64, neither of them actually did anything when I clicked them, nor showed up as a process in system monitor. I rebooted my computer, redownloaded KSP, copied from my SSD to my HDD and still got nothing. This is probably an issue on mine rather than KSP's side but the game crash before this happened did make me suspicious. Last-minute update before posting: I did get KSP to open by running it as root from the command line, and it doesn't crash on loading the vessel. I blame the computer.

I first want to start out by saying that i love Kerbal Space Program so much, and with each new update i fell the game gets better and better in ways that amaze me every time I play, which is why i feel screwed over by this issue. I tried out KSP 1.1 after it came out, getting all excited because of the amazing results in performance that i saw in the twitch streams. Then i started getting into it, and when i checked the performance, it capped at 60-65 FPS in a stock game, just like 1.0.5 (i did a comparison to make sure). I assumed it was because i wasn't switched to 64-bit because it wasn't showing the (x64) in the version number on startup. I actually made another thread about how to switch to 64 bit on a Mac, and i was told it was a unified binary and to check my activity monitor. So i did, and it said i was on a 64 bit build so i figured my troubles were over. I tried moving along with the performance issue by installing two mods: scatterer and EVE with configs. when I tested, i was getting 20-30 FPS on a 15 part ship in orbit, and same for a plane in atmosphere as the link shows: Performance Pics This was not the great performance fixes we were promised, because i see little to no improvement to 1.0.5. Does anyone know how to fix this issue, or is anyone having the same issue? SPECS: iMac (Retina 5K, 27-inch, Mid 2015) Processor: 3.3 GHz Intel Core i5 Memory: 16 GB 1600 MHz DDR3 Storage: 1.11 TB Graphics: AMD Radeon R9 M290 2048 MB OS: latest version of OSX El Capitan

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.

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.

Issue: At startup, a window with just a black background, approx 1024x768, is shown for a couple of seconds, then the programme just shuts down. This issue is rather similar to this one, but at least in my case it does not affect the X session. Tried: 32 bit version, 64 bit version (by changing progr. properties in Steam client), both from Steam client and from terminal: same result. Executables in Steam KSP folder have x permission enabled. My system: *) KSP: 1.1.0 Steam version, fresh install, no mod, run under Linux (no previous version ever installed, just bought it!). *) HW: 4-core i5 3.33 GHz, 12GB memory, ATI HD 5770 1GB mem, 2 x 1280x1024 displays. hardinfo report can be found at here. *) SW: Linux Mint 17.3 (based on Ubuntu 14.04 LTS), latest available Catalyst driver. *) Player.log can be found here. No KSP.log generated (or I could not find it). I had great expectations from this programme and I am rather disappointed by this unfortunate start. I am a developer myself (of other kinds of sw) and I know too well bugs do happen; this seems a very basic issue, though. I also understand it might be rooted in Unity3D, rather than in KSP code: another example of how Unity3D multi-platform support sucks! Thanks for any help, M.

It's HERE!!! I started playing KSP over a year ago and have been through 3 fresh start Careers. With the release of 1.1 I want to start again with all the new bells and whistles. However, I want to embark on as unique an experience as possible with mods. With the exception of MechJeb and Engineer Redux I have not done much with part or career mods. I am looking for some ideas to what would give me a completely new gameplay. In the past I have maxed out the tech tree just after landing and returning from Duna and TBH that's where the gameplay tapers off for me; when I feel a lack of "progress" towards some research goal. I have my eye on KSP Interstellar but would like some feedback before jumping in; does it enhance the game? should I max out the stock career before adding it? I'd like to hear ideas from people before I embark on yet another awesome journey into space!

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...

This doesn't look right? 1.0.5 was fine but this is happening in 1.1 can someone explain how to fix this?

I can turn on/off the "traction control", I can turn on/off the suspension, BUT I CAN'T TURN OFF THE MOTOR???? (are they nuts?) When you have a joystick, throttle applies to wheels, those things take a lot of of power. Am I missing something??

So Im on mac and I've looked through the fourms to figure out how to enable 64 bit on the Mac. what everyone keeps saying is that it is 64 bit by default but when i go into the game the performance is not improved and it is just as slow as 1.0.5 32 bit. i checked the activity monitor like some people suggested and it is labled as a 64 bit program, but is does not act like a 64 bit install due to the many lag spikes. I dont think im enabled on 64 bit, what should i do? Thanks, Justspace103

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...

So I downloaded the full release of Kerbal Space Program 1.1 yesterday, and the terrain is glitchy. Its all black. It never did this in the pre-releases. I've taken all my mods out, I've downgraded to 1.0.5 then upgraded again, I've even reinstalled it and it's still there. Screenshot of Terrain

I made a video about everything in 1.1. You can watch it here! Give it a like if you liked it, and subscribe if you want more!

Hello, I am using Ubuntu 14.04, with an Intel Core 2 Quad CPU Q6600 (2.4 GHz x4), with 8Gb of RAM, and a GeForce 720 card. With a fairly heavily modded game in 1.0.5, I was able to get a steady framerate of about 30fps (on highest settings). Now with a stock game in 1.1, I am struggling to get above 20 with lowest settings, and it fluctuates wildly. Even the loading screen is choppy. Also, even on 64bit, the game is refusing to use any more than 4Gb of RAM. I thought that this upgrade to Unity 5 was supposed to increase the performance. Any help?

I've tried flying the Aeris 3A, and it takes off straight as an arrow. My planes, however, tend to veer left and right on takeoff. I've managed to take off straight on 0 friction control, where the wheels appear to have no friction, so my engines do not have a sideways thrust offset. I am using symmetry and have tried placing wheels on fuselage and on wings, rotating them to various camber or lack of camber. I even used the Hangar Grid mod to force align all of my wheels to perfection. Looking at my planes, they tend to be back heavy, but I've always built them like that in prior versions, and they do not drift. The actual aerodynamics of my planes are fine, but they just can't take off straight. Can anyone determine the reasoning? It's just frustrating that the stock planes function perfectly while mine do not anymore. Here is one of my craft that exhibit this tendency. https://dl.dropboxusercontent.com/u/18568121/Goose%20Long%20Range%20Crew%20Carrier.craft This is my modlist, the only physics altering mod is FAR and I've had drifting without it.