Claw

Boostme, Please see here. We need a bit more info for this one: http://forum.kerbalspaceprogram.com/threads/92230-Stock-Support-Bug-Reporting-Guide Thanks, ~Claw

This has happened in previous versions too I think. I think you can solve it by deleting the contents of your GameData directory and verifying the game cache. This will force it to download again. I can't remember for sure, but I think that you might have some corrupted files. Cheers, ~Claw

Hmm. Just to clarify a little. You only need to hold the ALT (or Mod) key when you're placing the part. You don't have to hold it while grabbing, which can cause the editor to copy if you're grabbing a part "in-scene." You'll also need to make sure you're viewing the connection node a bit from the side. Otherwise you might still have problems connecting because of how the editor works. Cheers, ~Claw

One other thing to try, since you aren't providing logs and it's hard to tell what's going on. Edit your settings.cfg file and change the texture quality line to read TEXTURE_QUALITY = 1 (or even 2 or 3). Beyond that, we really do need more information than "KSP is giving me a black screen." Log files, when it's freezing, what operating system, etc, etc. We aren't trying to be jerks, but there's a LOT more info that keeps us from randomly guessing and telling you the wrong things. Cheers, ~Claw

I think with all the new parts, KSP might be pushing memory limits. Try editing your settings.cfg file and set TEXTURE_QUALITY = 1 (or even 2 or 3). Then reload the game and see if it starts up. I was running into the same problem. KSP was asking for a lot of memory right when it tries to load the main menu (grabbing lots of texture space). I'm not sure if this is a KSP bug or a problem with the memory management underneath. Cheers, ~Claw

What I would recommend is deleting the contents of your GameData directory (make sure not to touch your save games, or maybe even make a copy of them). I would also move or delete your settings.cfg file. Then make steam verify the game cache. After it downloads the new files, start the game. If it starts up, then go in and reconfigure your settings. If it crashes out, go into the new settings.cfg that it created and do like Padishar said and set TEXTURE_QUALITY = 1 (or maybe even 2 or 3, higher number is lower quality). You are probably running out of memory at the last second when KSP is trying to load everything up (including textures) for the menu screen. This was happening to me as well, and changing texture quality fixed it up. I think it's nearing max memory with all the new parts and maximum textures. After it starts, you can move the texture setting back if you want, and I think it'll take it then. I'm not sure if this is a bug with KSP's loading mechanics, or just how the memory management is handled underneath KSP. Cheers, ~Claw

That's because if you only delete the Parts folder, there may still be other bits lying around. You need to delete more than just that, so completely deleting KSP will work. Or you can just delete the contents of the GameData folder. Cheers, ~Claw

Hmm. Do you mind posting a save file? I thought it was supposed to carry over, but perhaps the new bits aren't being added correctly for some reason. ~Claw

All of what Taki said. In addition, the damage is supposedly based on energy. So it's supposed to be a combination of mass and velocity. ~Claw

I'm certain what you are referring to is a result of Maxmaps posting a tweet that the new cargo bay would be able to house parts inside and would shield the drag (stock parts with stock aerodynamics). As worir4 said, Max later followed it up with another tweet saying that it's not going to be in 0.25. So we have to wait until at least 0.26 (or maybe later) before we see this. Cheers, ~Claw

This isn't an intended feature, but rather a bug that was introduced when fixing a stack decoupler bug. Unfortunately the workaround for now is to use separatrons to aid in getting the boosters away. You can also try editing the decoupler's .cfg file and increasing the decoupling force. That seems to be helpful for some people's designs. Cheers, ~Claw

If it is a DEP issue, you'll need to Copy (not move or rename) the whole folder to a new folder. Windows knows if you're trying to trick it with a move/rename and might still be interfering. I'm not saying that is the cause, but if you had it installed to one of these places you have to go out of your way to get it away from Windows DEP. ~Claw

We need more info, such as if you use steam or not. Please see here to provide some additional information: http://forum.kerbalspaceprogram.com/threads/92230-Stock-Support-Bug-Reporting-Guide In general though, unless you copied over your 0.24.2 install somewhere, you won't be able to "revert to 0.24.2". ~Claw

Pawelk198604, Please provide some pictures. Typically this problem is caused either by an inverted decoupler, or one that has been attached too far up the connection node, where it's attached the correct direction, but the bottom node of the decoupler gets connected instead of the top. It can still look normal in the second case, so perhaps check that connection. Otherwise we will need some pictures or a .craft file. Cheers, ~Claw

Yes, the vehicles must be landed on Kerbin in order to recover. There are two new things in the update that go along with recover. One is as Taki mentioned. You can recover vessels from the KSC screen (by clicking on the little flags). The other is one of the strategies, where you can increase the percentage value of things recovered at a distance from KSC. Cheers ~Claw

Hmm. I don't remember off hand if the G-Force Experience software has selectable AA options. If you haven't try to turn OFF the AA in KSP. Sometimes the double AA accomplished by the game and by the video card interfere with each other. If it's already off in game, then try swapping the settings. Good luck, ~Claw

It is silly and completely valid. Unfortunately I don't know if it'll change since there isn't actually "water" where the pool is. At the moment, it is just a useless aesthetic. Cheers, ~Claw

Well, there's a whole list of bugs that need to be squashed. This one is actually the result of squashing a stack separator bug, so at the moment it's the lesser of two evils. Also, many of us who try to help on the forums aren't trying to deflect your reports by saying "use more separatrons." We are trying to provide work-arounds until such time as it's fixed. Cheers, ~Claw

Awesome! And thanks for the nice report. ~Claw

Yep, if you used the patcher see here: http://forum.kerbalspaceprogram.com/threads/95820-Double-parts-%28with-fix%29 Cheers, ~Claw

Yes, all of the files were renamed. Using the patcher causes the issue for this particular update because of the file reorganization. For any further discussions see here: http://forum.kerbalspaceprogram.com/threads/95820-Double-parts-%28with-fix%29 Cheers, ~Claw

Yep, for any further discussions see here: http://forum.kerbalspaceprogram.com/threads/95820-Double-parts-%28with-fix%29 Cheers, ~Claw

Thanks a bunch for using the bug report form! I will check this out when I get a chance. Cheers, ~Claw

It's also a tradeoff of making it easier to get the values to match up, without having to drag pixel by pixel to get different tanks (and maybe more importantly, things like parachutes) to be at the exact same values.

It's all good. I definitely agree that it can be annoying. The connection edges were intentionally sunk into the black edging a bit to make the wing parts flow together a bit more seamlessly. I'll double check the overlap on that part and see how much worse it is than the others. Cheers, ~Claw