Spicat

@Sade, merged your bug report.

@Sade, merged your bug report.

@Ghosty141, merged your bug report.

@NicHudson, merged your bug report. If you want to report several bugs, you need to make a bug report for each and not put them into the same bug report.

@Shiny55, merged your bug report.

@StrandedonEarth, moved to suggestion. If you want to submit a bug report do not use it to talk about other things that this bug (here suggestions) The issue you had was reported here:

@DaVincGa, merged your bug report.

@Oak7603, merged your bug report.

@CiberX15, merged your bug report.

On the IG discord, this conversation was brought up a lot, so I will just relay what Dakota said about this, so it's the official response to why they don't do that (yet at least): (and I'm managing the bug reports forum so I agree that it will be even more of a headache to manage two versions, it's already a tough process right now lol)

An other cause of this was fixed with 0.2.0.0: The save file provided here is unfortunately after the bug happens so can't really reproduce it. So if anyone have a craft file of this bug happening before the bug happens (so the craft is not already in the ground and you can make it happen again), do a new bug report with it and we will merge it into this bug report. It will help a ton!

Because people think it’s a bug, which it isn’t, So the warning is there to show it’s intentional.

@voystur, merged your bug report.

@The Aziz, merged your bug report.

I base this because it was said by the devs those kind of heat tweaking are feedback: https://forum.kerbalspaceprogram.com/topic/221803-bug-status-1222/ We move those to the suggestions forums sometimes when it fits, but most of the time it's weirdly phrased to fit into a suggestion post, so that's why asking people to post in the suggestion forum in DMs will probably be good. (I moved your topic to suggestion, you can change the title because I didn't have the original title: https://forum.kerbalspaceprogram.com/topic/222992-reentry-heating-vfx-need-to-stay-longer/ ) (Btw "bug hunters" are not devs, just volunteers who manage the bug reports forum, no "internal" decision from us, we can sometimes discuss with Anth or Dakota about some choice though (QA and CM))

I can explain this: One was about reentry vfx disappearing too quickly, this is feedback One was about description of report for Surface Sample data being the same that for Surface Sample, probably has been considered a feedback One is in the waiting area (sorry if a report takes time to be public) One was unjustifiably categorized as a feedback so I moved it to the public area: https://forum.kerbalspaceprogram.com/topic/222989-water-inside-command-pods-when-splashed-down-in-the-ocean/ All of the ones considered feedback above can also be discussed and could be considered as a bug. So we might, in the future, ask in DMs why you consider it a bug rather than a feedback before deciding to not make it public. With that, we also want to remake the old bug reporting guidelines to a better and updated one so it's easier for people to judge the quality of their bug report. Yours are mostly of quality (so that's not the problem) and we're very happy about people taking the time to report bug, so thank you!

@tweaked9107, merged your bug report.

@cubinator, merged your bug report.

@wuschelfun, merged your bug report.

@wuschelfun, merged your bug report.

I would say it's always good to report bugs if you have the time. Performance and crash issues will probably be more uncertain coming from an emulator. For other problems, I think it's absolutely fine. I would even say there is a higher chance your problem is not linked to your emulator rather than the opposite. Besides, if you report bugs on machines not officially supported (below specs or different platform), people who have this bug can also answer it (to say they have it too). People that might have supported specs, removing the doubt of the hardware specific problem. And it can even be an advantage; to pinpoint that the problem is hardware specific, I can think of this bug for instance: That we think is linked to having an iGPU.

@dhervas, merged your bug report.

@Suppise, merged your bug report.

@Glaive, merged your bug report.

@Mushylog, merged your bug report.