sal_vager

This sounds like a calibration or deadzone issue, the stick may just be too sensitive. Try increasing the deadzones in the joystick software and ensure it is calibrated.

No unfortunately there is no workaround, things like this have to be handled by certain individuals at Squad directly. I ask that you all please be patient, this has been brought to Squads attention but will take time.

Heh, I'm glad it worked and I'm glad you can survive now Have fun playing!

Yeah I know, really the save and load buttons should be in the flight scene pause menu, not just at the KSC. I've asked for it on the tracker and can ask Ted to mention it to the devs, as these buttons and their code already exists I hope it'd not be too much work to add them to the in-flight menu. Here's my ugly awesome mock-up of what it might look like.

@Vaporized Steel, it's fine, though I don't know how to answer you yet, frame rate drops a lot die to physics and KSP either drops frames or slows down (it's called lagsbane), anything that frees up cpu should help, I'm using xfce and should really try iceWM or similar to see if that helps. @CJHusVar, glad I could help

Hi CJHusVar, when you start KSP it makes a KSP.log in the Kerbal Space Program folder, and a Player.log in the /home/usesrname/.config/unity3d/Squad/Kerbal Space Program folder. These can show what is causing the issue, so please put them on a file host such as dropbox.com and post the links here

No, actually 300.6 m/s at 3700m up sounds spot on for the craft you describe using a Hammer SRB in 1.0.5, build 1028. What doesn't sound right is the "20km", a fully fuelled Hammer will take that craft a lot higher. Also, "Reloaded override drag cube for zeroed cube root part mk1pod on vessel Untitled Space Craft" is intended, it's supposed to be there. 20km is still pretty KSP, the atmosphere is only 70km high and a Mk1 pod with a Mk16 parachute, a flea SRB and a few basic fins only reaches about 9.8km. From that height the falling Mk1 pod and chute reaches a velocity of about 222.5m/s at 3.5km before it begins to lose speed, so it's safe to do a vertical ascent like this. But the Hammer gets you to 89.6km, it not only has more fuel, it's more powerful. From this altitude the falling Mk1 pod and chute reaches 1007.7m/s at 21.7km. At about 10km you're still fast at 763m/s. 408m/s at 5km. 300m/s at about 3.8km. And under 250m/s at 1.5km, you can pull the chute but you better be quick. This happens because the pod is heavy, it has a lot of mass so gains a lot of inertia which it doesn't lose very rapidly because it's also small. At half fuel load, the Hammer takes a Mk1 pod to about 20km. The falling pod reaches 304.9m/s at 13km then begins to lose speed. It becomes safe to open the chutes at 5km, you're about 260m/s at this point. Unfortunately your Player.log is completely useless, as all it contains is nouveau spam: So I have to jump to conclusions here, either you left the fuel in or something else is happening, and the only thing I can think of is KSP can't locate the settings.cfg or Physics.cfg This can happen when you start KSP from the desktop instead of the Kerbal Space Program folder, so make sure your link is setting the games folder as the working directory. It might also happen if you have bad permissions, make sure KSP is in the user folder, not in root. Also, I'm editing your post, people respond better to politeness on this forum.

Well, I see this has just been turned into another Squad bashing thread, so I'm closing it. If you want the developers to be receptive to your ideas try to be more like @Kevin Kyle, his post was fine, it laid out the issue and made a sensible request. Some of the post after that...not so much. Default throttle was set to zero at community request, then reverted because new players couldn't launch their rockets, going back to 50% was seen as a great thing by the majority as it helped stem the "Help I can't launch" threads, but how quickly some forget. Full throttle would be nice, but it's no hardship to press Z, and there are addons to alter the default behaviour

Just going to throw this out there... The Shuttle may have exited the VAB east/west but it was on the pad north/south, and there were a number of reasons for the Shuttle to perform a roll.

I got socks and aftershave, I already have socks and I don't use aftershave

Hi @suicidejunkie, the mk1 pod is only 1.25 meters across so it doesn't have a lot of drag. You can get away with a vertical descent if you only used a flea booster, but a hammer will put you too high, you need a parabolic trajectory so you pass through more atmosphere and slow down. Like this. Also note that heat shields are heavy so you will take longer to lose the inertia, but you don't need heat shields until you're returning from geostationary orbit or the Mun.

If KSP loaded the last autosave, and had just autosaved at a point when it's too late to avoid catastrophe, what would to say then? Alt+F9 (rightshift on Linux, command key on Mac) opens the load menu allowing you to choose which to load, I suggest you try it, and alt+F5 to create named saves.

Can you please upload the savegame to a file site such as dropbox, also the output_log.txt from immediately after trying this contract, it is in the KSP_Data folder.

KSP moderators don't handle the error reports Well some of us help with players issues but that's about it, and we have to learn as we go. Probably the best thing to do would be to put them all on google drive or dropbox, then post the link here and other players can take a look, maybe even help figure it out, though it's usually just a memory crash from too many addons. Try a lower texture resolution, that can help a lot.

If you click the link it will take you to the Unity manual for the engines command line arguments, -force-opengl is a Unity command line argument, it is not made by Squad. For Nvidia drivers click this link. On that page you can put in what card you have and it will tell you what the latest driver is, or you can make it detect your card and driver. If your driver is old, you can download the newest one and run it to install it, then restart the computer after it finishes installing. It may not help but it's still a good idea to keep up to date. Also, you might want to try -force-d3d11 instead, it will help reduce ram use just like -force-opengl does, there will be graphics glitches though.

Sorry but there really isn't anything Squad can do about OpenGL, it's a Unity3D engine command and the Unity engine supports D3d9 on Windows, not OpenGL. It's there along with D3d11 if you want to take your chances but even Unity doesn't provide support for it, if it doesn't work try updating your drivers or a different resolution. Or just don't use it.

Yes, but is the savegame from 1.0.4, or was it started in 1.0.5

Hi vpeonix0407, is this in a save from 1.0.4 ?

Hi WY, please delete the settings.cfg file in the Kerbal Space Program folder then start KSP by using the KSP.exe file.

Hi @Kevingomez28, what other software are you running when you play KSP? KSP doesn't do this, so something else is making KSP do this.

No, one account per member, KMC2 will be removed.

Hi KMC2, many members had their passwords break, if you are not receiving the password reset email PM me and I'll try to sort it out I see you have reset your password and logged in as KMC, so KMC2 can be removed.

A shortcut on your desktop can be an issue yes, as KSP looks for some files relative to the KSP.x86(_64) such as the settings.cfg and the Physics.cfg, if it can't find them it runs with internal values and these were incorrect in 1.0.4 A shortcut needs to set the KSP folder as the working directory, doing this will vary between desktop environments so please see your desktops documentation for details. As for the segfaults it may be because KSP is in opt, it's not designed for this and could be failing due to a permissions problem. See if a copy in the home/user folder has the same issues.

Hi P-Maker, can you put the Player.log on pastebin for us, even if it looks useless it may still tell us something. Also, please tty KSP without any arguments, they simply are not required and are optional, though LC_ALL=C should no longer be required at all as KSP 1.0+ ignores the system locale on both x86 and x86_64 --force-opengl is also completely redundant and useless on Linux. But as KSP is causing the whole PC to freeze I'd be testing my RAM (memtest via a live cd) and checking my distro's own logs to find out what was going on. While KSP might crash or freeze itself, for your system to freeze suggests a deeper issue than anything KSP can cause.

The challenge guidelines are just guidelines, but they do exist for a reason. People want challenges that are interesting and fun, we see far too many where there is no real challenge and the poster has just posted something they think is cool without actually trying it. I recommend you think of how to flesh out this idea, as if it's too easy it isn't a challenge and it isn't fun.