Dakota

This has been fixed as of v0.1.3.

Moved all bug reports to the archive in preparation for v0.1.3.

More focus on video content and devs on camera. Less barrier to entry than Discord. Also on the technical side, it's easier logistically compared to using Discord Stages. There will still be an #ama-discussion channel in the Discord and we'll take feedback there afterwards, as we did before.

Sure. Look out for this Friday's Dev Update for some new science info.

Just to clear up a few things: Intercept Games has been hands-off when it comes to community moderation since KSP2's launch. I can't speak to how it was before I got here, but I've been pretty adamant about letting the community moderate itself. There have been quite a few times that the forum moderation team has reached out to me about a disputed situation and, they can attest, that my usual response is "here's my two cents, but I defer to your decision-making. You know what's best." I did community moderation for about 3 years for a different role and so I can form guidelines that I think lead to the best discourse (like the new Discord rules), but enforcement is always best to be laid upon the shoulders of those most integrated with the community - the KSP forum mods and you all using the report system to flag rule-breaking messages to them. The only actions I've taken personally have been on the Intercept Games Discord against hard-and-fast rule-breakers (transphobic comments for example), when I was around and saw the comment first. All other actions on the forums, subreddit, and Discord are taken by community members like yourself that work hard to create a space to encourage discussion about our games - for which I am, and I hope you all are, thankful. None of the community moderators on any platform are paid or in any way pushed to sway sentiment in one direction or another. While we've made significant changes to our communication style over the past couple weeks/month, that is not a result of any one user or even a group of users. As the liaison between the community and the development team, I read basically everything posted on all of our community platforms and social media. And it's my job to come to other teams with actionable sentiment, but also not overemphasize the importance of one piece of sentiment over the other. People often blame community platforms (especially in gaming) to often be echo-chambers, just either repeating the same positive (or negative!) sentiment over and over, with the opposite opinion always being drowned-out by the most vocal. I'm sure that some PhD student could probably talk in detail about what leads to this trend, but when it comes to actually bringing these messages to the development team, I work pretty hard to keep things equal to ensure the team is given the best insight into how the WHOLE community is feeling, not just the vocal majority (or vocal minority.) On the transparency note, I personally have been advocating for our new "style" since the very beginning. That's not to place blame upon any member of the team; it's to show that we think very critically about everything we do here and, very often, popular complaints about any sort of action we take were first voiced internally by members of the team. We understand the current state of the game and we're working hard to meet your expectations. There seems to be this idea that our entire team is "acting like everything is okay" and that we're all just blindly trudging ahead ignoring everything around us. I can tell you whole-heartedly that that is not the case. Every single member of our team wants this game to be the best it can be and we're all very attached to Kerbal as a brand as well. We want to see the game succeed, reach new heights, new audiences, and there's nothing more enjoyable than seeing someone have a blast with something you worked so hard on. That's why we often highlight some of the amazing creations created by members of the community internally and on socials. It's easy to get discouraged, especially with the vitriolic nature of some of the discourse around the game (more on that later) - and so we do our best to keep morale up and show how important KSP as a franchise is to you all. Just this past week, I got to share with the team a note sent to me from a community member about how critical KSP1 is to his relationship with his son who has a learning disability. The community team wouldn't be putting such a focus in this area if we felt like everyone on the team was comfortable with the state we're in. Outside of the actions my team is taking, there is a ton of work being done to progress towards each step of the roadmap because we know how important it is to you all that we not only get the game to a playable state, but also add new depth to the game through new features, parts, and progression systems. --- On Respect The Forum's guidelines exist to "keep our community welcoming to all and to encourage mutual respect." The Discord rules say to "treat everyone with respect and politeness," and to avoid "encouraging or engaging in disruptive, aggressive, abusive, disrespectful, creepy, or inappropriate behavior." Some of you have a deep connection with this franchise. A deep connection. I mean you're here actively participating on the official KSP forums, right? And at the same time, many of you feel cheated, lied to, disappointed, and many other negative emotions towards our team after the wildly anticipated release of KSP2. Often that's directed towards Intercept, but then others, who ALSO feel a deep connection to this game, feel the need to defend against the negativity. I think through over the past few months, there has been a relationship breakdown between many members of the community and the development team and it has caused a schism that, as described in this thread, has split this forum (and the general KSP community) in two. It comes down to respect, I think. At its core, a portion of the community feels disrespected by the development team after investing their time (and potentially money) into KSP2. They feel like they aren't being listened to and demand an explanation/apology/someone's head on a silver-platter. Trust is an easy thing to break and it's often incredibly difficult to build back up that relationship to it's original state. For those people, we're doing our best to build up that trust again. There's always the possibility that sometimes we have to share bad news, but our goal is for the good news to always outweigh the bad. My hope is that, in the future, you can look back on these past few months and see how much progress we've made towards changing your mind. I only ask two things: As we work towards rebuilding, you meet us there. Keep voicing your opinion and telling us when we're wrong - but attacking the team (and community members) with a bitter attitude is only going to work against our goal of building back to that ideal. Keep focused on what's in front of us. It's very easy to look back and say "oh they did XYZ wrong days/weeks/years ago" and speculate on why things happened one way or another, and you might be right - but none of that helps us move forward, towards Science, Colonies, Interstellar, Multiplayer, and beyond. --- Sorry for derailing this thread a bit, but OP's post really spoke to us on the community team, and we've also been having roundtable discussions about this exact topic for a couple weeks now. Appreciate you all, Dakota

Hi all! Whew, another two weeks have flown by and we're so close to the release of v0.1.3! Soon(tm) soon(tm) soon(tm)!!! We're hard at work getting that prepared and beyond, and it looks like you all have also been hard-at-work making some amazing creations! Below is a small selection of some of the community contributions throughout June thus far. Did I miss anything awesome someone made? Did YOU make something awesome? Share it in this thread! Enjoy, Dakota @pyasupro Suppise (Discord) Avoidance (Discord) TheUSSLoliChan (Discord) @S_Coriolis Kerman_von_Braun (Discord) Maddie (Discord) GoldDragon (Discord) The Space Peacock (Discord) @Socraticat Zyfle (Discord) dianagearhead (Discord) mushylog (Discord) StronkTrix (Discord) Tr1gonometry (Discord) HolsterSP (Discord) VinFaz (Discord) Pennyless (Discord) @Davidian1024 SciVirus (Discord) @sumghai @GalileOh-No Ghost-San (Steam) ykurokhtin (Steam)

sir.

We hope to get the game officially supported on Linux someday, but it's pretty far down our priority list. Translation layers are definitely helping, especially with the work that Valve is doing on Proton and Apple is doing with their own project - but we know it's still not ideal. Trust me, I too want to play KSP2 on my Steamdeck one day!

Not a bug report, moving to suggestions.

Not a bug report, moving to development discussion.

Thanks for submitting this. I've passed it on to our Writing team and they're looking into getting the descriptions updated in a future patch.

This is a bug report specifically for the Private Division launcher and should be directed to Private Division Customer Support. I will also add that Linux / running the game through translation layers is not officially supported by our development team. Will move this to Technical Support so discussion can continue if needed.

Moving to suggestions.

Good callout. I think Kerbodyne developed the Rhino before the Mammoth-II, so their marketing descriptions must not have been updated. Will be fixed in an upcoming release.

Thanks for the report @Anth12! This is indeed a bug @Pat20999 even if it's just a localization mistake. We've identified that there's some missing strings for that particular part and will look into getting that fixed. No ETA at the moment but I'll update this when I know more.

more to come soon(tm)

That's what we call the dev updates internally :p

As seen in today's Upnate, this project continues to move forward. Still cleaning things up and figuring out how to wrangle this old-school forum and teach it some new tricks. Feel free to give feedback on the process thus far or how things look. Appreciate ya!

Poked the hamsters a bit and got them running again. Let me know if the issue persists on your end.

Heya, sorry the update caused some issues. I'll look into this and see if there's a fix. Can you let me know what iOS version your iPad is running? Screenshots of what it looks like would be awesome. Also if there's anyone else who is experiencing this issue, more details would help a lot. I just tested the forum features on my own personal M1 iPad Pro and it worked fine. Guessing it's an issue with the Safari version you're stuck with. There's some reports here of a similar issue with older devices and the forum software we're using. Does that seem like the issue you're experiencing @Scarecrow71?

Work over the few days week: - Cleaned up the Bug Reports Subforum and enabled a "fluid" view - giving us a sidebar filtering box for the various categories. - Added new feature to the forums for colored tags and prefixes. Easier on the eyes when skimming. - Added a custom indicator if a developer has responded to a report - Added bug report form. Supports file uploads. - Added bug report form link to main page - Automated form->report for quality-check msedge_6LQPbuXaFB.mp4 - Updated a whole bunch of css and custom code on the forums backend to make all this happen. - Added some new moderation tools to ease the approvals process. - Probably a lot else I'm forgetting. Progress!!!

.ipsEmbeddedVideo { max-width: 900px; } Hey all! Welcome back to another round of Community Highlights. The past few weeks have been BUSY over here, so I'm thankful there's been so much positivity and creativity going around the community recently. We constantly share screenshots from players internally and your creations inspire us, make us laugh, and fuel us to keep development moving forward. Below is another amazing series of community creations from the past two weeks, including some incredible space stations, a bug named Greg, and some wicked fan-art as well. As always: did I miss anything? Use this thread to show off something amazing you saw within the community over the past fortnight. Appreciate ya, Dakota lmKTn7CS-ZXLo2ME.mp4 @KSpaceAcademy with an awesome showcase of why Starship "did a kerbal" [Full 55min Video] @Davidian1024 @iron256 @ylizur foxhound @S_Coriolis kuriente spartandh211 @SebMendonca @exospaceman <[I Flaze I]> (Discord) Geezee (Discord) GoldDragon (Discord) zfblone (Discord) @Heretic391 HitchHacker (Discord) わかまつ (Discord) @TwoCalories @Spicat Concertym (Discord) ᗩᐯOIᗪᗩᑎᑕE (Discord) IgnitionFreddylange (Discord) s4vior (Discord) @Terminal_Vtuber Sylvi Fisthaug (Discord) ElectroLlama (Steam) Abelinoss (Discord) @Socraticat @Temmie_Ten @Madishmike @Well Yim_The_Muon207 (Discord) ringedwood (Steam) Enzoishet (Discord) Somebody (Discord) @LoSBoL @Speeding Mullet the_space_peacock (Greg) dec21164 (Steam) TNTFortress (Discord) Rend (Discord) @Kavaeric (+ @Anth12)

They have their own internal tools that they'll keep using. Again, still need to lock everything in.

The solutions in the above screenshots aren't 100% locked-in. I'm still trying things out and coming up with ideas on how to make the process as painless as possible for the userbase, but also for us. We need to be able to take-in these reports in an efficient manor, so have to make sure all the internal stakeholders are on-board as well. I just wanted to provide a peek behind-the-curtain into what's possible, our general thinking for this initiative, and to show that progress is being made in this area. Glad to hear the work might inspire you to contribute again. That's the point!

Invision (the forum software we're using) has a "fluid" forum mode that allows for subforums to feed into one big category like this: It's possible we may use that feature or something else to help categorize reports. The technical roadblocks need to get resolved before I can fully start to implement the features that will make this a whole lot easier. --- Similarly, the platform has a feature to allow for upvoting on threads and responses - so I think most would just upvote the thread to imply "I too have experienced this", and perhaps reply to the thread if they'd like to provide more information. See below for a small sneakpeek: Individual threads can also be merged very easily, so we can keep things organized if a user can't find the original report. --- Definitely. I don't know if we'll go as in-depth with "reproduced" or "working on it", but the plan is that we'll mark/reply that it's been seen and again once it has been fixed. A tag could also be a solution. Or the Bug Hunters could mark the latest reply by a dev so it's pinned to the top of the thread, as seen here: --- Still figuring out how this all should come together, and definitely need these roadblocks to get resolved before I can start implementing the kinda "next-level" part of this - but appreciate the feedback and ideas. Hopefully this provides some more insight into my general thinking into these improvements. Dakota