To obtain your version, use any of the following:

• Open the "buildID.txt" file located in your installation folder. The version is listed in the first line of the file.
• Open the "readme.txt" file located in your installation folder. The version is listed just below the ASCII art in the top of the file.
• Start KSP and look in the lower right corner of the main menu screen.

The KSP version will look something like "0.24.2.559". Also list whether you're using Windows, Mac, or Linux, if it’s 32 or 64-bit, and if it's Steam. Knowing the version allows us to avoid recommending things that are not applicable to your operating system. Also, there are some issues which only turn up in specific operating systems or specific versions of KSP.

KSP is capable of taking screenshots in-game by pressing F1. The screenshots are stored in the KSP installation folder under a folder called [SCREENSHOTS].
You can upload screenshots directly to the issue using the files button, or any image sharing site

Screenshots usually illustrate the problem better than trying to explain with several paragraphs. Feel free to mark up your screenshots with a noticeable colour to highlight important points. Also, avoid excessive drawing since it may end up making your problem less clear.

Please attach these files directly or as a link.

Video's can be very useful when trying to describe visual challenges or hard to describe situations, and sometimes you might be asked to provide one of these if people are having trouble "seeing" it for themselves. Videos can be recorded and uploaded to Youtube or a similar video sharing site, and the link added in an update. Don't worry, you don't have to speak if you don't feel you can. Annotations are generally much easier to do and see.

In the KSP installation folder, you should be able to find a folder called [SAVES]. Open this folder and select the save file name that applies. Inside you will find three things: one or more files (usually two) with a .sfs extension and a folder called [SHIPS].

• Craft Files: Any ships that you created will be stored in the [SHIPS] directory under [SPH] for Space Plane Hangar vehicles or [VAB] for Vehicle Assembly Building vehicles. Craft files are named the same as what you titled your ship in KSP and have a .craft extension.
• Save Files: To attach a save file, you need the file called persistent.sfs (or any file ending in .sfs in the [SAVES] folder - generally quicksaves, but also named saves).

CRAFT NOTE: When attaching craft files, please ensure that no mods or parts are used in the creation of the craft. we won't be able to open them - see Modded Installs
SAVE NOTE: Using ALT+F5 to quicksave will allow you to give the save file a specific name, which can make it easier to find for uploading.

Please attach these files directly or as a link.

Craft files should be provided whenever you are having an issue with a specific craft, or have found a potential bug that you find easiest to reproduce with that specific craft. Having the craft file to work with will make it much quicker and simpler for us to diagnose and attempt to replicate the issue, and hopefully get it resolved much quicker.

When KSP crashes it will general a folder with files with details surrounding the crash. Usually a window will pop up ingame asking you to send this information to the developers, along with the name of the folder. You can find this folder in the KSP install directory.

If KSP doesn't crash, start KSP and cause the problem. Quit KSP and find the output_log.txt (not the KSP.log) at the location below:

• Windows: KSP_win\KSP_Data\output_log.txt OR KSP_win64\KSP_x64_DATA\output_log.txt (depending on which used)
  - In case you installed KSP into a Windows protected directory (C:\Users, C:\Program Files or C:\Windows\ and their subfolders) the output log file may be stored in the folder called C:\Users\[Username]\Appdata, this folder is usually hidden so you should enable the view hidden folders option (more information). Note that for the demo you should find the output_log.txt file located in the KSP_Data folder.
  - Steam users should right click KSP in Steam, click on Properties, then in the Properties box, click Local Files, then Browse Local Files.
• Mac OSX: Open Console, on the left side of the window there is a menu that says 'files'. Scroll down the list and find the Unity drop down, under Unity there will be Player.log Aka Files>~/Library/Logs>Unity>Player.log
• Linux: The log is written to /home/user/.config/unity3d/Squad/Kerbal Space Program/Player.log

Please attach these files directly or as a link

The output and crash logs are useful because they help us understand exactly what you were doing when the issue happened by providing a "play-by-play reenactment" (in text form) of your KSP session. Anything out of the ordinary will often show up in the log files, and it gives us a good idea of where to start looking for solutions.

The method to gathering system specifications will vary over different operating systems, choose which one applies to you.

• Windows: open the start menu and select (or type) 'run'. Type in 'dxdiag' and press the [ok] button. A new program will pop up called the DirectX Diagnostic Tool. On the bottom of this screen a [Save All Information] button is located. Press it and save the text file to a location you will remember.
• Mac OSX: use the "System Report" app from the 'About This Mac' menu and hit cmd+s to save the file in .rtf format in a location you will remember.
• Linux: for linux an application called 'hardinfo' will gather all required information. Save the information to a location you will remember.

Please attach these files directly or as a link.

Having detailed system specifications is useful in more ways than one. At a glance, we can tell if your system should be experiencing any performance issues, and whether the system is correctly registering and utilizing an installed video card, sound card, and so forth. All the hardware information for your system is contained within these files (and is extensive). As such, it's a must-have for those of us trying to diagnose and solve certain issues.

You can upload files directly to the issue tracker subject to a maximum file size of 5Mb. If your files (say the crash report folder) exceeds this size, please use any file sharing site (such as Dropbox, Mediafire or File2web). Images can be hosted on imgur which is free to use and allows albums to be built. These sites will give you a link you can include in your posts to share your files.

!Ideal report.PNG!

Subject Controlling all Craft in Physics Range - A short descriptive title works best
Set the fields at the top accordingly - some are mandatory. see below for details
Description: All craft within physics range respond to control inputs. - A brief summary of the issue, This will be seen in the issues list.

Steps to Replicate:
1) Make a Mk1 pod and hold it down with a TT-18A Launch Stability Enhancer (yes, just the two parts), and launch the craft with a kerbal on board.
2) Hold ALT-W to push the pitch trim all the way to 7 notches nose down. (Just short of max.)
3) Turn on SAS (important)
4) Stage to release the pod to the ground, then go EVA
5) Walk forward with your EVA kerbal

Expected: Only the Kerbal should be controlled. - this is optional, so no need to include obvious statements.

Result/Observed: Pod will flip over while controlling kerbal. Pod stops when kerbal stops walking.

Fixes/Workarounds:
- Zero out trim (ALT+X) on each craft within physics range.

Notes:
This behaviour may be related to issue number xxx
Keys for controlling each vessel must be mapped the same (i.e. Walking forward for a kerbal & pitching a pod must both be ‘W’).

- Files added
- Images Link: http://imgur.com/a/LEeCB
- Craft File if required
- Log File if required

Pretty self-explanatory; this issue type is for behaviour you encounter that appears to be unexpected or not intended by design. If you suspect that the issue is based upon opinion it is more than likely not a bug, but feedback instead. Excessive consumption rates would be feedback, not a bug. But lack of resource consumption or incorrect displaying of consumption would be a bug.

When you encounter behavior that you feel is unexpected, but perhaps not unintended, this is the issue type you would use. Generally, you should try to suggest alternate behavior that you feel would be more suitable or balanced. Well reasoned suggestions on improvements and comments on how the game plays overall are welcome here.

Each bug should have its own Issue ticket. Please try and break down your issue into smaller chunks where possible. Compound issues do arise, but each element may lay in different parts of the game. We much prefer reports for each section so they can be dealt with in isolation, but with knowledge of the connections. We are able to set relationships between issues, so please indicate in your report if you believe those connections exist.

Please be sure to search for existing reports before submitting your own. Using the search button (top right) you can enter keywords separated by a space. This will return all issues that contain all or combinations of those keywords as a list. Please review these to see if they describe your particular issue. If one exists, please feel free to add extra information to it.

Many issues are related to each other, and we are constantly adding links to these so they are easier to find. Any related issues that might also describe what you see can also have pertinent information added if you feel it is missing. We welcome any suggestions on relationships you feel are missing.

If an existing report describes exactly what you see and you have nothing to add, please do add a comment about some aspect so we know how widespread the issue might be. Also check against the platform to see if it matches your own.

Advanced search allows for much finer grained results.

Any duplicate reports will be marked as such, and a link to the original added. Please also feel free to point out any duplicates.

It's highly desirable that you can recreate the issue with a Stock Install. We appreciate that there are many game enhancing mods out there, and that you may be using them, so please also consider using a KSP install that has never had mods installed in it (as opposed to deleting mod directories).

1. Completely stock, with no mods ever installed
2. Your "main" playing version of KSP with any modifications you desire.

Please note: savegames may not be interchangeable between a stock install and a modded install. Even if there are no extra parts, some game parameters may have been changed that have consequences for a stock game.

This ensures a solid report while preventing accidental damage to your main save games when replicating bugs.

Try to keep it simple, stating facts in as clean and concise a manner as possible.

For Squad to find a bug, they need a way to consistently cause it to happen in a mod-free, clean install of the game, and using a completely new spacecraft (when possible). If at all possible, try to find the minimal set of actions that will cause a bug to happen. That can be extremely helpful to narrow down the source of the problem. If the bug can only be reproduced with a specific spacecraft design, please include a .craft file of the simplest design where the issue still happens in your report.

Remember, steps to reproduce the issue help the most. Bug reports like 'I've seen this happen, and it ruined my mission attempt don't help replicate the issue. They just state it happened, but it doesn't help find the source of the problem. On the other hand, extremely detailed reports of what was happening when the bug took place are also a bad idea because it's difficult to dig through a wall of text to figure out what happened.

If you found a way to fix the problem in the short term, please post how. This can help out other people who are having the problem, and also allows the bug squashers to focus their efforts.