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.