Darrin H

Ok I know I'm going to get a hard time for that vid, but it was spur of the moment - and had our reaction. NORMALLY - we definitely record on our computers. This was special.

Hi everyone! Just wanted to add that I've got a brand new role on the team reporting directly to me! It's a QA Tools Engineer (SDET) role and encompasses the sort of work that was previously done by our software engineering team, that we're now moving into the QA organization. Come join us to make some cool new tools, automation & frameworks for KSP2! https://careers.take2games.com/job/5605197?gh_jid=5605197 And be sure to check out all of our other open roles across the team: https://www.interceptgames.com/#jobs

Gotta give credit to the original finder of this issue:

Please 100% make sure you have no MODs running. We saw a few issues with users having low FPS, but when they completely removed mods, it improved as expected.

FYI - thank you all very much for the info on this issue. We're looking into it ASAP.

So, now that the big news is out: Here's why we waited. In the next KERB, we'll be listed if it's fixed in 0.1.5 or 0.2.0. We wanted to wait to be able to share that info. Next week means: Sometime between 10/23 and 10/27

I'll elaborate a bit on this (I was actually the person who suggested we wait... so it's on me). 1. We wanted to wait and have Anth send out the KERB on Monday since that'll be part of his role going forward and we thought it would be a cool thing for him to do on his first official day. 2. The bigger reason is the next KERB will directly reference items that Nate will be talking about at SCD this weekend. Come back Monday and you'll understand exactly why.

No announced date (to the public) - we have our own internal dates & milestones and I wanted to make sure everyone knew that 0.1.5 was on schedule.

"With Anth joining us on Monday, we've decided to postpone this week's K.E.R.B. status update to then! Plus, since it'll be after Nate's Space Creator Day Presentation, maybe we'll have some goodies to share!" I'll elaborate a bit on this (I was actually the person who suggested we wait... so it's on me). 1. We wanted to wait and have Anth send out the KERB on Monday since that'll be part of his role going forward and we thought it would be a cool thing for him to do on his first official day. 2. The bigger reason is the next KERB will directly reference items that Nate will be talking about at SCD this weekend. Come back Monday and you'll understand exactly why. Also - want to make sure everyone understands this 1 day delay on the KERB will not affect the 0.1.5 date.

The very bottom of the original post: Note: this report is not fully representative of the work our team is focused on. This is just to provide insight into our progress on the most concerning issues to our community. Additionally, the lack of a status update does not imply a lack of importance or general progress - we just do not have anything to share at this time.

We don't want to officially report out our findings until we 100% have all the details. I'd expect the next Bug Status report will include all the information. (But Anth was able to repro on a Radeon RX 6600 also)

We do actually - and we have a great relationship with AMD where they've sent us cards for testing. However, this bug does not occur on every AMD gpu, and in fact we've narrowed it down to a specific series and have a card on the way to confirm that.

We've hot/hotfixed this. Never should have happened and was 100% a missed bug.

This is a bug, we're fixing it asap.

Hey all, just wanted to toss in a note as well. We’ve already seen some very well written bugs reported into the new system..! GREAT job on those. Anyone who runs into an issue – be sure to log it here: https://forum.kerbalspaceprogram.com/forum/144-ksp2-bug-reports/ Also – be sure to upvote the bug if it’s an important issue to you as well. They don’t sort (yet), but we’ll be sorting them manually on our side when we look at them. BUT… most importantly – be sure to add info if you are running into the same bug as someone else. Maybe something they missed (I’ve already seen that done a few times… very nice!). Lastly - within the bug itself, you can upvote comments. If you see a great workaround or something adding great new info – be sure to upvote that. Thanks everyone, Darrin.

Thanks for reporting this, it's a known issue as we implement this new system and get it up and running.

The devs and QA have a fantastic relationship here at IG. (I've been around a long time.... that's not always the case)

Hi everyone, I’m super biased, but this part of the Dev Update is the most important part (to me)! Please read it over, check out the hyperlink to Dakotas post for feedback… and give feedback! It’ll be a pilot program initially and we’ll DEFINITELY make changes over time, but this was a big request from my QA blog, and this is our first big process change in that regards. This is that opportunity everyone wants: to impact change in how we do things…! thanks, Darrin. Bug Reporting Progress I also mentioned last week that we were exploring ways of communicating our current priorities more clearly, as well as giving members of the community more agency to communicate their own experiences and priorities to us. With that in mind, Dakota Callahan and the Community Team have begun to make some changes to the Suggestions and Development subforum. We’ll get into more detail about our specific implementation next week, but Dakota has already shown some of his work in that subforum - he’s taking several steps, including creating a new Bug Hunter member role, reformatting threads so that they can be up-/down-voted (this is just for bug threads), adding recommended tags/prefixes, and setting up a system that allows administrators to combine duplicate issues. This will start as a pilot program, and its success will hinge on how useful the community finds it and how maintainable our team finds it. The best possible outcome would be that players use the subforum to surface the issues they find most pressing, and our devs have the ability to ask directly for additional context. Again, I’ll provide more detail about this new structure when it’s fully in place, but in the meantime check out Dakota’s post - he’s got some great ideas!

Not even the tiniest of bits. The people here are FANTASTIC. I've worked at MS, Amazon and other places and this crew is as good as it gets imo. Very helpful to new person on the team and they really do care about KSP. I can't stress that enough. Most of the team is previous players (like all of you). Regretting to a blog...? eh...... maybe. Some mean people out there on reddit.... ouchies. Appreciate that. Mortoc and I both came from very similar teams at our previous jobs. He's a very cool dude - and I'm very happy to be working with him. Anyone else reading stuff. I think I've answered everything I'm going to for now. I might do an AMA someday... TBD. If you post after this - please don't think I'm ignoring you. I've just gotta get back to work...!

VERY big topic. Great question. There are very good reasons to have one. BUT.... also very bad reasons to have one. We're having discussions about it, thinking of how we can do it and avoid the bad parts (I'm not going to list those out). No promises, but it's high on our list of stuff to make a decision on.

I love this question. This goes to what I mention in the blog about "frequency" To me frequency of a bug actually trumps severity. Let's say it's a crasher but a very small % of the users hit it. And you have... well... something like wings falling off that a much higher % hits. Imo that moves the wings issue above. Now... lots of other factors come into play. Like where the code is, what it affects, how complex is the change, and honestly a lot more, but you get it. So.. in summary. Wings = important, and we need to make sure they get fixed asap. As far as logging bugs. I've said it on the discord like this: If I'm playing the new Jedi game (which I am at home at night). And I find a bug, I'm not logging it for them. I just don't do that sort of thing. They'll find it, they'll fix it, etc. But... at the same time I'm not going to go up to the boards and say "I can't play, I found a bug, and it doesn't work" without any more info. I just want people who I know care very much and are very frustrated to give us the info needed so that we can fix their issue if they care to post about it. (the more info the better, but I don't expect anyone to spend significant time on it... just enough that we can take it from there)

It's a weird phrase. I had it say "decrease" and got comments and then "improve" did also - I should have said it better. Basically: over time we want stuff "below the bar" now to get "above the min bar" as time goes on. Totally get that. I've called it my "QA blog" as I wrote it up. I think the CMs just need a spot to put it here on the board. Definitely didn't want to send a wrong vibe or mixed message there. Apologies from me.

I can't go into the details on Telemetry, but I can say: it lines up with what we see. We got a LOT of crashes, and reports of crashers early on and throughout Patch 1 to Patch 2. Telemetry was telling is the great majority of a certain type of crash (the loading issue) was with video cards below the min bar. When we reached out to users who were sumitting the issue, we got the same results. The key is: automation alone isn't enough. Telemetry alone isn't either. We need user data (with info) to help build the full picture.

I actually had your info in the original version of this blog. But, when it was reviewed, I was told I needed to remove it. Since we didn't directly make it or test it, etc. Aka, IF something bad happened after I told people to use it... that sort of thing. I should have at least mentioned that there are cool tools out there to have people search on their own for them. Yours is great - and we all very much appreciate you putting it together. Not gonna lie, I'm more than a bit bummed that so many are looking for issues in the blog and making assumptions that for example I ignored it without knowing the full info. BUT at the same time I get it... because it wasn't mentioned at all and that's 100% my fault. I'm here to help. My goal in the bug area was more for people who were leaving NO info at all (and there are a LOT of those - actually the biggest percentage). People who have been leaving lots of info - we love it - please keep it up! There is, and I mention there is in my blog. This is incorrect. I started a week before release and I didn't make the original. Also, the current one is generic for all games across Private Division. The primary goal here was to improve the large percentage of bugs & posts that are submitted across the board. A good amount of users are doing a great job, but far too many literally say what I mention in the blog "This game is broke, i can't play". I wanted to stress to people that if they submit that, then nothing can be done with it. For the people submitting great info - fantastic keep it up!