Claw

Try running KSP.exe directly. For some reason the launcher is very unpredictable, and seems to cause problems for some people. ~Claw

I assume you are using steam. In which case they are saved somewhere else. I would make a guess as to where (I think maybe somewhere in your documents folder?), but I'm not a steam user myself. So hopefully one will be along soon. Welcome to the forums! ~Claw

You can also try dropping down the Texture Quality (KSP settings in the main menu) by one notch. v0.25 uses more memory than in the past, and sometimes this causes a crash on scene change (when the game is grabbing lots of memory). Cheers, ~Claw

Hmm. Your question is a little confusing to me. Perhaps check here and see if there's more info you can provide (like a marked up screenshot?). http://forum.kerbalspaceprogram.com/threads/92230-Stock-Support-Bug-Reporting-Guide Cheers, Claw

The arrow is showing like that because you are building in the VAB. The VAB editor assumes that whatever craft you are building will travel UP (like a rocket). So the lift vector is going to be all messed up since all of your wings are perpendicular to "up." So not a bug, but how the VAB is mechanized (for rockets). And closed, at the OP's request. Cheers, ~Claw

I also had similar issues, and reducing the texture quality (in the main menu settings) by one notch fixed it. Just as Padishar is suggesting. Cheers, ~Claw

I don't think it'll cancel your strategy, but you won't be able to switch them without the building. ~Claw

This: http://wiki.kerbalspaceprogram.com/wiki/Plugins I'm suffering through the same thing as you right now. I'm running MicroSoft Visual Studio Express 2010 (which the wiki tells you how to set up for KSP purposes). It's free and I'm familiar with it, but the wiki link above has two other suggestions as well. Good luck, ~Claw

If you had mods, and didn't install updated versions, then your old save will not be compatible. Usually KSP flags the saves as such and deletes things it doesn't recognize. But maybe in the case of fine print and/or debrefund it didn't recognize what was wrong with the file. ~Claw

As KSP has evolved, it's using more and more memory. It may be that it has finally surpassed the amount of physical ram on your computer. What that means is that your operating system might be using virtual memory, swap things out of memory an onto the hard drive. This is a slow process and can cause problems. There are a couple things you can do to reduce KSP's memory footprint. The first thing to try would be reducing your texture quality in the settings option of the main menu. There are also mods that can help reduce the memory requirements... Of course this all assumes that memory is your problem... Or it could be your physics time steps have changed in 0.25 if you let it generate it's own settings.cfg. You might want to check that too. Like skeevy says, we need a bit more details about your setup. You can check this link and it'll tell you how to get the logs for your game: http://forum.kerbalspaceprogram.com/threads/92230-Stock-Support-Bug-Reporting-Guide Cheers, ~Claw

Indeed. I am working on a new thread, that encompasses the more recent additions to our bug family. This bug was already reported for 0.25, but I still appreciate reports. Especially when they follow the bug report guide. Thanks for the heads up! Cheers, ~Claw

Sorry to hear. I get that you are making a stock request, but perhaps I will move this over to the modded support forum where maybe people have other suggestions for you to help with the burden of fixing. Good luck, ~Claw

Heya Joshwoo69, It would help out if you can read the link below. It'll ask for information like reproduction steps and operating system. Also, if you can narrow down what's happening right before the first problem, and maybe point out what the first problem is. It's really hard to guess what you were doing when digging through a 7MB log file and we don't know what we're looking for. http://forum.kerbalspaceprogram.com/threads/92229-How-To-Get-Support-%28READ-FIRST%29 Cheers, ~Claw

No, the number in parenthesis is what's been converted. The above picture does have a bug, in that the base contract awards zero science and isn't showing the total science with the conversions. It should show like you said, with 700 (+700). (But that wasn't exactly what the OP was asking about.) If the parenthesis showed what you were getting, then the OP would receive -22k funds and -135 rep for contract completion (which wouldn't make sense at all). I agree that it's not very intuitive, but it is how it's set up. Yes, there's a display bug, but it's not what the OP was asking about. ~Claw

This log entry "UnauthorizedAccessException: Access to the path "C:\Program Files (x86)\Steam\SteamApps\common\Kerbal Space Program\KSP.log" is denied." and "UnauthorizedAccessException: Access to the path "C:\Program Files (x86)\Steam\SteamApps\common\Kerbal Space Program\settings.cfg" is denied." leads me to believe your folder permissions are set to read-only. You'll have to deselect that (and make sure to apply it to all sub folders). Also, I see you have several mods installed. You may want to try running KSP without the mods first, to see if the stock game is working correctly. Then add the mods back in. Also, make sure your mods are up to date. Cheers, ~Claw

If you want to fix any flights in progress, you should be able to do the following... 1) Make a copy of your save directory and keep it somewhere safe. 2) Open your persistence.sfs file with a plain text editor like notepad (do NOT use word or wordpad). 3) Search (Ctrl+F) for all entries of "sasModule" 4) Replace each entry with "advSasModule" 5) Save the persistence.sfs. 6) Load up your game in KSP. You can also try the same with the quicksave.sfs, then just load it with the standard F9. Good luck, ~Claw

The name of virtually every part.cfg file was changed to something more descriptive. I don't think many of the paths have changed (except for space plane parts), but almost all (if not all) of the file names are different now. Probably not what you wanted to hear, ~Claw

As a random thought, edit your settings.cfg and change the texture quality line to TEXTURE_QUALITY = 1 and start KSP. Other than that, please see the bug report sticky to provide some log files. Cheers, -Claw

It sounds like one of your saves is corrupt. You can confirm if one of the saves is a problem by moving the save games out of the SAVES directory and then try KSP again. It might also be that one mor more of the folders are set to read-only. Reset the attributes. How you do that will depend on your operating system. And lastly, if you are using Windows, make sure you haven't put KSP in places like "Program Files" or on the Desktop. Windows DEP is known to cause issues from time to time. Other than that, please see the Bug Report sticky to provide us more info (like log files). Cheers, -Claw

I noticed in your log that you are running a few mods, so I'm going to slide this over to the modded support forum for now. If you can get it to happen in stock, let us know and we'll move it back. Otherwise you will probably get better help over here. Cheers, ~Claw

Hi joethebeast22, Pictures of what you've created so far would help, since we can give you specific advice on what you're designing. juanml82 provided some good advice about asymmetric thrust issues and intakes. I do the same thing, although I typically place my intakes, engine, intakes, engine in that order, but I think it'll work either way. I also agree that you only need three ram or three shock intakes per TurboJet at the most. More helps, but you aren't really going to see much of an increase unless you double them. Also, you can try looking around in the spacecraft exchange forum for ideas. There are several good examples in there. Good luck, ~Claw

While it's a fine hobby, please no discussions of alcohol on the forums. And even if we could, it's a bit off topic for the thread (so you're right about starting a new one, but it'll be closed for alcohol content). Thanks, ~Claw

Yes, this is a someone common problem. Assuming that you confirmed the docking ports are the same type and that the attached to the craft facing the correct direction (these are more common problems than you'd think), then you can check out the link below. Sometimes docking ports aren't "ready", and the link below contains a fix for resetting your docking ports. http://forum.kerbalspaceprogram.com/threads/78863-FIX-Dock-Undocking-Bug-in-0-23-5 Cheers, ~Claw

Bugs like this usually start with one failure that cascades into many problems. That's why the log will be very important here. Once you run into a problem, you can stop. Because the bugs that come after are usually just the result of the earlier bug. -Claw

I'll try this out later, but pictures might help. -Claw