The Space Peacock

@Rubeniomerged your report

merged the two reports and removed the mention of the bottle rocket from the title to avoid confusion in the future. thanks!

merged your report

@Homer_S moved your report out of the archive after @Stephensan let me know this is still hapening in the latest version. link to their report made in 0.1.4.1 here

@Stephensan moved your report out of the archive

This KERB was brought to you by: Darrin’s Phone

@wuschelfunmerged your report; i think its fair to assume that the kerbal freaking out had something to do with EVA being incorectly blocked

How To Report Bugs This is a detailed guide on how you should report bugs on this subforum. Please make sure to go over every step before submitting a report. you can find a blank bug report template at the bottom of this page. The basic rules: One bug per bug report Avoid Duplicates (bugs that have already been reported) Include ALL necessary files (save/craft files, logs, images/videos...) Do not report feedback or suggestions Step 1. Is This A Bug? A bug is any form of unexpected behavior that occurs while playing the game. This can range from small typos in mission descriptions to mission-ending problems with say, docking ports. Bugs come in all shapes and sizes, but they all have one thing in common; The game is not doing what it's intended to do, and it's (usually) negatively affecting gameplay. If your issue does not meet this criterium, please ask yourself if it might be better suited as feedback instead. Bug reports that are really feedback usually don't make it through our quality check. Feedback and Suggestions can be posted in the appropriate channel here. Some examples: "I want to be able to see upcoming transfer windows!" => This is a Suggestion "The VAB should let in more ambient light, it feels too moody in there" => This is Feedback "My vessel falls through the surface on Vall..." => This is a Bug! "My DeltaV readout in the VAB is completely wrong!" => This is a Bug! Step 2. Has This Been Reported Before? To keep the bug reports subforum clear of clutter and avoid spreading upvotes over multiple reports, we urge you to please make sure the bug you are reporting hasn't been previously reported. Don't forget to check the KSP2 Bug Reports Archive too; all bugs below a certain upvote treshold and/or age are moved into the Archives each time the game receives an update, and we rely on you to identify what bugs are still in the game. You can quickly let us a know a bug is still happening by submitting a new bug report that links to the one in the archive, or by tagging us under it in a comment (@Bug Hunter). Thanks! Additional information on a bug can still be helpful, so if you run into a previously reported bug and would like to report it anyway; make sure to include a link to the existing report in your new report. This makes it easier for the Bug Hunter team to merge your report into that one, ensuring reports about a given bug stay centralized in one thread. For this reason, we also ask you to Please limit yourself to ONE bug per report. How to search the forum for existing bug reports: (important!) Step 3. Gathering Information Before submitting a bug report, try to collect as much information about the bug as possible. Try to describe the issue as well as you can. Be concise, but also include details: If you ran into an issue with a rocket, how did you build that rocket? If your trajectory looks weird around a certain planet, how did you get there? what launch vehicle did you use? Ask yourself these questions: What is happening? [REQUIRED] What did you expect to happen? Can this be reproduced? If yes, how? How severe is this bug? Other information for your report: Your Systems Specifications: CPU, GPU, RAM and OS [REQUIRED] Images and Videos Craft and Save files [in .json format] Game logs Player logs [For Localization bugs only] Localization string Not every bug report needs to have all this info. Sometimes a single line describing the issue is enough ("Hey, there's a typo in this part description..."), but in general try to include as many of these items as possible. The more complex the bug, the more info should be in the report. Save files, Craft files, Videos/Images, Reproduction Steps and Game Logs help the Bug Hunter team and QA to understand, reproduce and test your bug. Your efforts to collect these are greatly appreciated! How to Find Save/Craft Files, Game Logs and System Specs: A Note On System Specs: If you are below the minimum required specs for the game, you can still report bugs. Please mention this in your report however, and be aware that depending on the nature of your report your issue may not be a priority for the QA team. Step 4. Formatting And Submitting Your Report Once you have all the information you think you'll need, it's time to make a report. This paragraph will deal with what needs to be in that report, and how to format it properly. You'll also find an empty report template at the bottom of this paragraph. You do not have to be logged in to submit a bug report, but please note that submitting a report anonymously makes it impossible for the Bug Hunter team to contact you if they need more information about your report! Also keep in mind that Bug Hunters may change certain aspects of your report (such as title or category) or add context if deemed necessary. To begin writing your report, go to https://forum.kerbalspaceprogram.com/forms/2-ksp2br/ This will take you to the Bug Reports Form. It should look like this: Category First, you will need to choose a fitting category for your bug. If you are unsure what category best describes your bug, take a look in the spoiler below to see the various categories and which bugs generally fall under them. Don't worry about getting it wrong: the Bug Hunter team will change the category to whichever one fits best during the review process (if needed). Title Next, choose a title for your report. This should be a short sentence that accurately describes the bug. Ideally, your title should follow the Problem-Action-Location Format: - Problem: The bug itself, e.g. "Vessel Explodes" - Action: The action you were doing when the bug occurred (if applicable), e.g. "After Loading Quicksave" - Location: The situation the bug occurs in, e.g. "In Low Orbit Around Kerbin" Example of a Good Title: "Vessel Control Is Not Transferred When Clicking 'Control' In The Tracking Station" => Perfect! Examples of a Bad Title: "Tracking Station Bug" => Not descriptive enough "This stupid bug wont let me control my rocket after i click 'control' a thousand times in the tracking station!" => Too long, too informal Description This is the 'body' of your report. It should contain a concise description of the bug, steps to reproduce it, videos and images, and additional information if needed. To keep all reports as uniform as possible, we ask you to follow the following format (a blank template can be found at the bottom of this guide): Severity: Choose how severe you think this bug is. Choose between (None/Low/Medium/High). Frequency: Choose how often this bug occurs. Choose between (Once/Rare/Inconsistent/Always). How do i rate Severity and Frequency? Issue: Describe what's happening, what you expected to happen, what you were doing when it happened, etc. If the bug happened to a specific craft, tell us how you built that craft. If it happened around a specific celestial body, tell us how you got there. The more information here the better, be as specific as you can! Important Note: do NOT rely on the title to explain the bug! Your report may get merged into an existing report thread, which will cause the title to be lost. Steps To Reproduce: If your bug is reproducible, list the (simplest) steps to reproduce it here. Saying "Load this quicksave" is good; saying how you got to when that quicksave was made is better! (tip: use the "Numbered List" tool in the format header) Videos/Images: (optional) See '4. Attachments' Additional Information: (optional) if you have any additional info you'd like to share with the Bug Hunter/QA team, this is the place to do it. Example of a good Bug Report Description: Attachments Next up, you'll add Videos, Images, Craft/Save Files, (Player) Logs and other media to your report. There are multiple options to add media and files. The most conventional method is to use the built-in upload feature (see spoiler below). Any file you upload will automatically appear at the bottom of your report after submitting. Using this feature, you can upload one file to each category. If you want to include multiple screenshots, videos, or files, you can either put them into a single ZIP file or use an alternative method for adding media (see further). Guidelines and alternatives for adding images and videos: Please Read! Computer Specifications This is where your system information goes. You will need your CPU, GPU, RAM and Operating System. These will automatically be formatted into your report after submitting. If you think your report might benefit from additional information about your system, feel free to add a screenshot of your extended specs to the report. Other You're almost finished writing your report! All that's left to do is select the game version you encountered this bug in, to let us know if you had any mods installed, and if the bug was reproducible without them. Do not report bugs that occured on modded installs, unless you are absolutely certain they are reproducible on unmodded installs. If you do wish to report a bug that is reproducible on an unmodded install, please only use save files made in the unmodded install; the Bug Hunter and QA teams can't open modded save files. Once your bug report is ready, read and acknowledge the statement on information and content posted on the forum, and press 'Send'. Your report will appear on the bug reports subforum as soon as a member of the Bug Hunter team approves it. Please be aware that this may take some time. If we deem your report needs additional information, we may reach out to you via DM. Happy Bug Reporting, Kerbonauts! BUG REPORT TEMPLATE: (please do NOT copy paste with formatting) Public Postings If you share personal information, post an image or video, or provide other content in public forums such as on a message board, chat room, comment field, or profile page, other people can view, collect, and use that information. If your user name or ID contains your name, your name will be publicly available on leaderboards and elsewhere as described in this Privacy Policy. Users of such public forums may be able to identify you, use the information to send you messages, or copy any of the images, video, or content you have shared. There is no expectation of privacy or confidentiality on any of these public forums. Please do not share your personal information in public forums or in your user name or ID. You are responsible for any information or content you publicly post using our Services. Thanks! -The Bug Hunter team

@Mutant87 merged your report

@Aiurwarrior1 merged your report

Happy first birthday, KSP2! They get old so fast

@Vortygont merged your report

@CameronLeroux merged your report @Meb Kat moved your report out of the archive (again)

@SolarAdmiral merged your report

hi there! bug reports are reported via this form, please report them there in the future The bug in your video has already been reported (a lot) though, so i moved your video into this thread

Yeah, it's a bit liberal in that regard; mostly for the purpose of allowing long videos if those are needed. Your size is actually not that outrageous for the length of the video, but it still makes it hard for us to embed it into the forum so other people dont have to download it (for files that large that can take up to 15 minutes). Don't know if you've ever heard of Handbrake? its an amazing tool for condensing large video files into smaller ones without losing quality. I was able to bring your video down from 200mb to just 30mb with it

try filtering categories in the menu on the right. it's under "parts and vessels"

@NightLoad added the image you submitted in a follow-up report to this one

Wouldn't you panic if you were just casually eating a snack in orbit, only to find yourself warped ahead a few months the next moment?

@SuperBoots moved this report out of the archive and merged your report

@brobiwan merged your report, think this one describes it better than the landed state bug. it sounds like it might be a variation of it, but best to keep them seperate for now. also a quick heads up: please make sure the video files you submit for bug reports arent too large, that prevents us from viewing them/embeding them in your report @PicoSpacemoved your report out of the archive

@NovaRaptorTV merged your report

@magnemoe this is fixed in 0.2.1

moved this bug into the archive. It's a bit outdated now that the icon scaling is fixed. vessels having priority over planets is still an issue tho, so there's now a new standalone report for that:

The main reason would be for those bugs to stay in the active bug reports thread so people can continue to upvote them i guess. You assumed correctly that all reports below a certain upvote treshhold/age get moved to the archive each patch. We usually pull those reports back out when they get re-reported in the current version. I'd say its not always needed for minor bugs, but; if you see any significant bugs in there that you've experienced again in the latest version, always feel free to submit a report linking to those and telling us they're still in the game and they should be back up in no time