Claw

Your log indicates that you are running out of memory. Here are a few things that you can try. 1) Delete your settings.cfg from the root KSP 2) Launch KSP directly from KSP.exe instead of through if it crashes again... 3) Edit settings.cfg and change the TEXTURE_QUALITY line to TEXTURE_QUALITY = 3 if still crashing... 4) Copy KSP to another directory such as C:/Games/KSP and try it again. Do NOT move it. Make sure to use copy and paste. If still not working, and you are able to. 5) Delete KSP and reinstall from steam. See if that helps. There has been a rash of this problem, and it's usually been associated with the install location. However, you are using steam, so that /shouldn't/ be a problem. Cheers, -Claw

Get it out of your downloads directory. Windows sometimes causes problems if you install KSP to protected areas like downloads, documents, program files, or the desktop. The safest bet is to install it to somewhere like C:/Games/KSP If possible, I recommend installing from a fresh zip. If you try to move your current install, you must copy & paste it. Do NOT "move" it, because windows might try to cause problems still. Also, there are a few empty folders in KSP by default. It's an old holdover from past versions. Cheers, -Claw

Hey Avagontamose, I replied in your other thread and shortened the steps. If it doesn't make sense, let me know. It actually sounds more like you have a file permission problem, but I posted a bit of info in the other thread. Cheers, -Claw

Sounds like you might have one of two problems. You can open the debug log (Press ALT+F2)and watch for errors. That might help you figure out which problem you have for sure. 1) Check the permissions on the VAB directory. Make sure the directories are not set to "read only." (Most likely.) 2) You have a corrupt .craft file in the VAB directory. If you have a corrupt craft file, you'll have to delete it. Often, corrupt craft files are much smaller than the other files (on the order of 1kb). The VAB directory will be located in /KSP_Install/saves/your_save_name/ships/VAB Welcome to the forums! ;D Cheers, -Claw

Hi DiggyDogg24, I'm actually going to refer you to the support forum, and the support sticky. It is difficult for us to guess what your problem might be without more information. It might help us if you can upload a log file and give a brief description of what you are doing. You can post a new thread in the support forum, and you'll likely get help a little faster. Support Forum: http://forum.kerbalspaceprogram.com/forums/76-Support-%28unmodded-installs%29 Support Sticky (how to find your info): http://forum.kerbalspaceprogram.com/threads/92230-%21%21%21-PLEASE-READ-BEFORE-POSTING-%21%21%21-Stock-Support-Bug-Reporting-Guide Welcome to the forums! Cheers, ~Claw

Achievement board is updated. Nice job, and I love the little story bits interjected in your posts. Cheers, ~Claw

The X200-16 is about the smallest tank that will sink. If you add any air intakes, expect to get a lot of bouyancy. However, you can use engines (including jet engines) underwater to give yourself some extra downward push. Cheers, -Claw

Diomedea is right. Generally speaking, the area at the engine nozzle needs to be clear out to about 2 to 3 times the length of the fire plume. That's not an exact number, but works as a pretty good rule of thumb. If that isn't working for you, it would definitely help if we had either a craft file or some pictures. Cheers, -Claw

Dude, this is awesome! I will update the achievement board tomorrow (it's getting late). And I love the look of that plane. Reminds me of one of those weird cargo lifter helicopters (Russian I think?). Cheers! ~Claw

Awesome! I'm glad this is still helping people. Cheers, ~Claw

If you purchased the game through steam, you can also verify the games cache. That should fix any files for you. Cheers, ~Claw

I see you've posted in my main docking thread, and I responded there. I'm more than happy to help you in there, to keep things from being less confusing. So in that case, I will close this thread for now...Unless you would rather it stay open. (In which case, just let me know.) Cheers, ~Claw

After you turn off the crossfeed, you have to do another quicksave. If you just open the persistence.sfs, if might not have saved unless you force one of the auto-save triggers to occur. So the safest thing is to press MOD+F5 and give it an obvious name. Cheers, ~Claw

Sometimes, when you run into engines (even if unrelated to the engines), it can cause something like this to happen. Especially with exploding ships, restarting KSP is often helpful. I'm glad it worked itself out. Cheers, -Claw

Symmetry in the SPH is a little wonky sitheyradial symmetry has been unlocked. You can try downloading my SymmetryActionFix (in my stock bug fixes) and see if that helps you out. I'm not in a position to double check your specific bug it at the moment, but this is the sort of thing my bug fix is aimed at. http://forum.kerbalspaceprogram.com/threads/97285-0-25-Stock-Bug-Fix-Modules Cheers, -Claw

Locked, per OP request. Cheers, ~Claw

Moved to modded support, since it appears that you have mods installed. Cheers, ~Claw

Check out this thread: http://forum.kerbalspaceprogram.com/threads/92230-Stock-Support-Bug-Reporting-Guide I recommend you start a new thread, and upload a log file and probably your save. You can upload them to a place such as dropbox, google docs, mediafire, pastebin, or anything similar. You might have the same problem listed here, but it sounds like you're experiencing other problems as well. So uploading the log file can help us figure out what's wrong a little faster, and we can help you out better. The crew roster should have more kerbals listed in it than the tracking section. Listing them five times isn't necessarily a bad thing either, if they managed to obtain several "firsts." Also, welcome to the forums! Cheers, ~Claw

Yes, this is actually a game bug. As posted above, it's recommended that you zero out trim on any craft within physics range by pressing MOD+X. Moving a ship (doesn't have to be a kerbal) causes the SAS on all craft within physics range to disengage. So if a ship has trim input, the trim input will take over. Cheers, ~Claw

Hi thegodmobile, I fixed your image links so that they are easier to see, but also put them in a spoiler tag since they are large. The other neat thing about IMGUR is that you can upload multiple pictures and make an album. Then you can post a link to that album here in the forum by using the [noparse] [/noparse] tags. Just replace the Xs with the five letter IMGUR album identifier (that shows up in the address bar).Nice craft, and welcome to the forums! Cheers, ~Claw

Well, without an output_log file, it's hard to tell if something else is causing problems. So all I can do is give you the standard spiels... - So, make sure that you have granted an exception for KSP for your virus scanner, so that it isn't interfering. - Make sure the files are not set to Read-Only. - Try running it directly from KSP.exe - If you currently have (looks like it's in C:\Kerbal Space Program\), or have ever had, your copy of KSP installed to a place such as Program Files, Documents, or on the Desktop, then COPY and paste it somewhere else. If you move it, windows will still interfere. (This has been the culprit in several of these crash problems lately.) - Make sure your video drivers are up to date. - Make sure direct x is up to date. - Try using the -force-opengl flag (might cause graphics problems) - Kill or disable as many other programs as you can before running KSP. - Try another fresh download and install. Again, make sure to not put it in a windows protected area. Cheers, ~Claw

Not that I've sent an asteroid to Duna myself, but I agree that I would probably lean toward redirecting the Class E toward Duna, vice trying to capture it around Kerbin first. I imagine it would be far less expensive (fuel and ship wise) to push the station infrastructure to Duna and meet the asteroid there, vice capturing around Kerbin, building, then pushing that huge mass out to Duna. I might also consider trying to do the slingshot off of Kerbin, but probably wouldn't try to speed up station parts to meet it, since it's likely going faster than I care to push the station parts. But that may all highly depend on the asteroid and it's path. Yes. This is precisely why I posted my tutorial about intercepting well outside of Kerbin's SOI. With a small probe, you can really pour on the dV when leaving Kerbin for the intercept. Even without trying to go excessively fast, you can intercept asteroids in 1/3 to 1/4 of the time compared to waiting until they get into Kerbin's SOI. That still leaves plenty of time to dispatch a proper mission craft for the job, and know what kind of rock you'll find when you get there. Cheers, ~Claw

There are a couple things that can corrupt a .craft file. - The game crashes when it is trying to save: The file will be truncated and will not contain all the needed info. - The game experienced a bug before saving, and that interfered with the save process: Again, the file will probably be short. With these two cases, it generally leaves KSP unable to open the "Load" dialog. The remedy for this is to delete the corrupt .craft which, as GiantTank pointed out, is generally small. However, if you are able to actually load the .craft but it's somehow broken, or only that .craft doesn't want to load, then it's possible the file was corrupt another way. Sometimes this happens if you use some excessive clipping techniques, especially if the ALT+F12 menu or UNDO is involved. You can sometimes tell if this is the case, because the .craft file will have an excessive part count (which you can see in the Load dialog). This can cause weird ghost parts or things to disappear. Looking inside your craft files at the fuel tank, it looks like the fuel tank was somehow connected incorrectly by the game. The links are broken and misreferencing parts. I have a suspicion that perhaps UNDO was used, or that the game failed to connect correctly while symmetry was on. Unfortunately, this means that your corrupt file is probably too much of a mess to manually fix. Or at least, it's probably not worth the time to fix it. I would say that the corrupt .craft was probably also responsible for the crashing/buggy behavior that you saw when launching. Your .bak version looks okay, although I didn't inspect it too deeply. Hopefully that narrows down where your problem might have come from, so that you can avoid it in the future. Cheers, ~Claw

Sure, although I've never bothered to look at how harmonic the windows are. But really, my comment was based on... In which case, if the areocapture around Kerbin is with the AP pointed the wrong way, it won't do him much good because he doesn't want to wait for another transfer window. Cheers, ~Claw

Fantastic! I am glad to hear that you got it working. And I have no idea why it sometimes works fine, and other times doesn't load in those locations. It is very strange how finicky it can be there. Yes, the Pilot SAS modes aren't tweaked very well. They have problems with craft that have too much control authority, which is pretty common with small craft. Cheers, -Claw