Claw

Please see here on how to upload log files: http://forum.kerbalspaceprogram.com/threads/92230-Stock-Support-Bug-Reporting-Guide Also, ensure you are NOT installing to the desktop. That tends to cause problems. You're better off in a place like C:\Games\KSP Welcome to the forums! Cheers, ~Claw

Same, so if you can get it narrowed down to a few mods that enable this to be repeatable that would be awesome. I've been tracking this bug for a very long time. There aren't any smoking guns on this one. It might be that he has something in the logs that can narrow this down, but at the moment I'm excited that he's able to semi-reliably repeat this. Cheers, ~Claw

Please have a look here: http://forum.kerbalspaceprogram.com/threads/92230-Stock-Support-Bug-Reporting-Guide A picture of what you're seeing is worth a thousand words, and helps us keep from guessing. Might be useful to upload an output_log.txt also. At face value, it sounds like your game resolution is set too high. Welcome to the forums! Cheers, ~Claw

It looks like you're getting that because the separator is actually attached to the engine and not the fuel tank. It's one of the more peculiar things about the fuel system. Decouplers actually do have crossfeed capability. However, they have special logic that if they are connected directly to a fuel tank, they don't feed. You'll likely have to right-click and disable fuel flow until you've established it in orbit. Yeah, I know. It's a silly thing but it's just how it was meched a long time ago. Cheers, ~Claw

Press MOD+F12 (Alt in windows) to bring up the debug menu. In the cheats tab there's an infinite fuel checkbox.

If you can manage to upload a save file, I can try to take a look and see if there's an easy fix (assuming it's all stock). Welcome to the Forums! Cheers, ~Claw

Hmm. I have no guess on this one off hand. Mind having a look through this thread and posting some logs? http://forum.kerbalspaceprogram.com/threads/92230-Stock-Support-Bug-Reporting-Guide Thanks, ~Claw

This is usually caused by having the game's resolution set too low. For some reason it causes that really wide button to completely disappear. See if you can bump up your resolution a notch and give that a try. and Welcome to the Forums! Cheers, ~Claw

Does this stay persistent? I mean, after it's bent can you exit KSP and come back later, and it's still like this? This was happening on some clawed vessels early on. I was able to load someone else's persistence and warp the claw ship to pieces (in the same way as you describe with your other ships). Thanks, ~Claw

No, this isn't intentional. It's not intended to bleed the ship dry of resources by being "untrained." Thanks for the feedback. There's been a standing SAS problem with lightweight ships being over controlled by excess torque. Maybe try using smaller torque (which I know is not possible with just a Mk1 pod) and turning off the RCS to see if that helps. You could also right-click disable the pod torque. Cheers, ~Claw

Oh yeah, sorry. You are indeed correct to generally say "making corrections sooner is better than later." If you switch to a westerly direction during the initial stages of launch, you spend much less dV than trying to change your orbit direction later. In that case, you're spending 174 m/s * 2. Whereas if you did it in orbit, you need a lot more (as illustrated in my earlier post). But that's not to say that being closer to the planet is the reason. It's because your velocity in relation to orbit is already very low. Course corrections are another case too (such as on the way to Mun). Making them early rather saves you dV because small angles far away make big changes later on. Whereas once you get closer, you need to add more dV to get the same distance offset (or inclination change). I'm trying to be short, so hopefully that's still clear. Cheers, ~Claw

Hmm. Nothing intentionally changed that I know of. Do you have a save file from before the crash that you can upload? Thanks, ~Claw

It's stored in the persistence file. So I think the only way in game to get it refilled is to hire them all. If you're not opposed to save file edits, you can try deleting the applicants from your roster and loading your game back up. Be sure to keep a backup copy, and edit with a plain text editor (such as notepad). Cheers, ~Claw

The blue ball will also drop sometimes even if you have wings. That's because the VAB assumes the wind blows down the length of the rocket (from the top down). Since the wings don't generate lift until they have some angle of attach, the lift bubble will sometimes end up at the floor. Cheers, ~Claw

Yeah, sorry. I didn't mean to sound dismissive. Just trying to make sure this doesn't get written off as an add-on problem. Of the testing I've done, I nearly certain it isn't clipping related. It doesn't act like other clipping bugs. I'm pretty sure it's not SAS pulling the ship apart either, based on how the ship looks when it's coming undone. Your pictures are exactly the same as the bug on stock installs. One thing that would also help out when you're posting pictures is to specify which is the root part, and which is the second part that you placed. I'm also thinking there might be some correlation between where the ship comes apart, and where the first two parts are. Seems fairly common that it'll bend at the joint off the second part. And often when it comes apart, the second part gets ripped out completely.

Huh. Well this sounds like a bug of some sort, but we definitely need more details about what you're doing. If you could have a look at this thread, it would help if you could provide some extra info. Cheers, ~Claw

That was going to be my suggestion. The easiest fix is to turn down your Texture Quality to Half, depending on your setup. Cheers, ~Claw

I'm going to lock this one out, since your more recent thread seems to have the answer you seek. http://forum.kerbalspaceprogram.com/threads/103433-What-causes-the-launch-pad-to-blow-up Cheers, ~Claw

Well, I can't swear this is your problem, but your log is throwing this error on all your launches: So my recommendation would be to forcibly update your Direct X. Perhaps it didn't install correctly with the autodetect option. Give that a try and see. I think it might be this one. Double check though: http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=35 Cheers, ~Claw

That's your best bet. Depending on what version you are upgrading from, you might be getting multiple copies of parts. It's easiest to wipe it clean and try downloading/installing again. Cheers, ~Claw

AA with the updated Unity seems to be causing all kinds of problems. Some users are reporting a lot of graphics problems with AA on. Unfortunately this one is sounding like a Unity problem, which is pretty hard for us to fix.

This sounds like the old "SAS overcontrol" problem. A picture and craft file would help confirm that.

zipster911, Please review this thread: http://forum.kerbalspaceprogram.com/threads/92230-Stock-Support-Bug-Reporting-Guide We will need some more details in order to try and figure out what your problem might be. Cheers, ~Claw

Interesting. I've not heard of the fact that KSP would letterbox. I'm guessing this has something to do with the Unity update. Is there any reason you can't set the KSP resolution to 1366 x 768? That would make sense if you're wanting to run full screen anyway. Also, I now see your other post:http://forum.kerbalspaceprogram.com/threads/103359-UI-Fails-in-OpenGL-Mode I'm not sure if these are related, but which is your most recent problem? Cheers, ~Claw

No reason to be sorry. Hopefully that'll solve your problem. Hmm. It used to register as landed on initial launch (to the pad or runway). Unless they changed it for 0.90.