Claw

You can upload to a place like mediafire or pastebin. This happens on occasion, but it's been very difficult to replicate. So if you can get it to happen repeatedly, please provide more details. Cheers, -Claw

Your picture is actually correct. It's just a little confusing with a string of numbers like that, and you happened to chose 50% (so the numbers rewarded and converted are the same). The numbers before the parenthesis is what was actually added to your resources after strategies are applied. The number in parenthesis shows how much was converted because of strategies. What's really happened is that you were awarded 44k funds, 22k went into your funds and 22k was diverted to science (-22k). Same thing for rep, 270 awarded which gave you 135 rep and 135 converted to science (-135). The result was thet you received 779 converted science (in parenthesis) and the base contract actually rewarded zero science (no number before the parenthesis). Hope that makes sense, maybe try a throw away save game with different percentages (other than 50%) and it might make more sense. -Claw

Because there is a whole slew of issues, and I'm working on a new sticky to cover most/all of them. If there were too many stickies, you wouldn't see the rest of the posts!

Yep, this is indeed an old issue. You can get straight to the Cross Platform bugs thread in my sig. There is also a fix in there if you find yourself in a position where you must rescue a quicksave. It's not a permanent fix, but will rescue a mission in a pinch. The broken link is due to the support forums being reorganized not too long ago. Sorry about that. Also, in retrospect I think Sal was being funny about it being an easter egg. Cheers, -Claw

If you add them back in, make sure you change the name in the .cfg file. Not the name of the file, but the name inside it. KSP uses the name to identify parts in-game, and parts that were replaced have the same internal name. Cheers, -Claw

This is a common misconception that is not true. As Lethal Dose and SlimeCrusher (and others) said above, you can place the torque modules anywhere and the effect the torque has on the ship is the same (regardless of distance to the CoM). The difference will come in if you put a lot of torque out away from the CoM on wobbly parts. Then the ship may have a tendency to tear itself apart. Although this has more to do with wobbly parts than torque. Cheers, -Claw

The double parts is due to using the patcher. The part.cfg files were renamed so now they are duplicated. You'll need to delete the contents of your GameData directory and run the patcher again. For your other problem, you may need to double check the KSP resolution setting to see if it made a mistake in saving. You can also edit the settings.cfg file directly (with notepad) and set the resolution you want by looking for the RESOLUTION lines. -Claw

Try a higher number for the texture quality (like 3). Also, you can try to reduce the resolution and set it to window mode to get it started. These things can help reduce the memory load. In the settings.cfg, look for the RESOLUTION lines and the FULLSCREEN line. Put in a smaller resolution and set full screen to false. See if that helps, then you can tweak things around after that. Window mode seems to work better for me, and that was the case for another user suffering the same problem. Cheers, -Claw

Yeah, what Diomedea said. I run borderless window all the time now at max resolution. It looks just like full screen but doesn't cause as many problems when you ALT+TAB away. The only downside is that you can't minimize the window very easily, and it likes to pop back up. Cheers, -Claw

Nearly all of what you describe is a consequence of the new masking features for when you are using a KSP window. It is apparently difficult to grab all of the events that a mouse can generate with the way the windows have been implimented in KSP. With maybe the exception of not being able to close it, or the jittery time warp thing. Those are all good things to note though as the interface continues to improve. Thanks, -Claw

That's because you are overwriting the zip file. Also, use caution with splicing the files together. You may end up with corrupted files everywhere. I was also having problems with chrome downloading. Mine kept hanging at 100-110 MB. Chrome also lets you pause from that screen you are showing above. Perhaps try to pause it every 100 MB or so. Good luck, -Claw

That's an epic picture. When logs are this big, they are often full of the same error over and over. If what Padishar suggests is still not manageable, try to recreate the problem with just the bare minimum needed to make it happen, then exit the game. This will ensure the log isn't full of extra info. Then if you can zip it up it should be even smaller. You can also try opening the log file (which migght be a challenge given the size, and look for a spam of messages at the end. If there is a long list of the same error, you can delete all the extras. That can also trim down the size. Cheers, -Claw

I don't know if it's the problem, but yeah, try resetting the read-only attributes again. Make sure you apply it to all the sub-folders and files, not just the top one. If that's still not working, please check this thread on how to provide us some more information (such as log files) to help narrow down the problem. Cheers, ~Claw

Hi Jimbo78, It was a really good idea to copy 0.24 before update. Personally I always do the same thing. Can you please check this thread and provide a little more info. Passing us some log files and what version of KSP (OS) can help give us clues. My first thoughts are to double check your folder permissions (since you deleted everything) and make sure they aren't read only. Steam has some weird tendency with that. Off hand, I can't recall of someone having all the options grayed out before. Cheers, ~Claw

Yes, this is how it's always been mechanized. If you attach something other than a fuel tank to a radial decoupler, and that part allows crossfeed, then fuel will feed through the decoupler. Any part that isn't specifically labeled as "not crossfeed capable" allows crossfeed. The radial decouplers are a special case in that they don't allow crossfeed to connected fuel tanks. Strange, but that's how it is. Cheers, ~Claw

32 or 64 bit KSP? And I second the "try to redownload and/or reinstall." ~Claw

Hmm. Well without knowing specifics of your setup, I would have to ask you to check out this thread and give us a bit more details: http://forum.kerbalspaceprogram.com/threads/92230-Stock-Support-Bug-Reporting-Guide There could be several ways to fix this, but the bottom line is that 0.25 renamed many of the part files. So you probably used Steam or the patcher to get the update. In which case you'll have to (as a minimum) delete the contents of the GameData directory. Then reinstall or (if you are using steam) verify the game cache. This should fix the part problem. As for the save files, I would need more info (from the link above). And maybe even post a save file on mediafire or pastebin for us to download. Good luck, ~Claw

We don't usually delete answered threads, but I can lock it if you'd like. For instructions on how to mark it answered, you can check here in the sticky in the forum: http://forum.kerbalspaceprogram.com/threads/85063-How-to-change-Unanswered-to-Answered The short answer is, edit your original post and click "Go Advanced." Cheers, ~Claw

Well, we can make lots of guesses and stabs in the dark, but it would help greatly if you could provide a picture of said craft. Multidocking is an option, as is changing the configuration of your ship. Puller designs can be more rugged than pusher, but doesn't guarantee that it'll work. Sometimes just stiffening up the payload works. Or try switching where your controlling the ship from. It kind of depends on the ship. Cheers, ~Claw

Also, I think a common problem that's going around right now is being caused right when 32-bit Win KSP tries to load the main menu. If that's when your game is crashing, try the following: Edit your settings.cfg file and look for the line that says TEXTURE_QUALITY. Change it to TEXTURE_QUALITY = 1 (or even try 2 or 3). Restart KSP and see if that fixes it. Hopefully that does the trick. Cheers, ~Claw

Hey onlinegamesz, I can't tell from your description what the problem might be. When you can, please check out the link below. It will tell you what kind of information we need in order to try and help you better. Things like what operating system, screenshots, and where the log files are kept. http://forum.kerbalspaceprogram.com/threads/92230-Stock-Support-Bug-Reporting-Guide Cheers, ~Claw

Well, this is the wrong log file, BUT I have a suggestion. Open the settings.cfg file and find the line that says texture quality. Change it to read TEXTURE_QUALITY = 1 (or maybe even try 2 or 3). Then restart KSP. If that doesn't work, see this post on what kind of information we need to help better: http://forum.kerbalspaceprogram.com/threads/92230-Stock-Support-Bug-Reporting-Guide Cheers, ~Claw

That's why I mentioned both of these fixes. Some things work better than others, depending on your designs. This same thing is listed in the 0.24 Cross Platform bug thread also. Cheers ~Claw

I have noticed more lag in the VAB when the ground (where the kerbal ground crew and vehicles are running around) is visible. Try scrolling up and working higher in the VAB. This might at least narrow down what's causing the problem. ~Claw

Yeah, this seems to be going around. I think with the new parts, KSP is pushing memory limits. Edit your settings.cfg file and change the texture quality line to read TEXTURE_QUALITY = 1 (or even try 2 or 3). Then restart the game. Cheers, ~Claw