nestor

To clarify, Yes, there will be a 0.2.2.0 update and we are currently working on it.

Mun Landing is the name of the tech tree node. We will be sharing more info on the tech tree leading to the release. Same with other Exploration Mode systems.

Discoverables are points of interest of different kinds that can award you science.

Discoverables is the term we use.

For clarification on my post, My comment about it not being a bug refers to the fact that this is not something that can be fixed with one change but rather a long term goal of improving perf. We will fix this but gradually and one step at a time.

Number 2 is not really a bug but a side effect of all the calculations that are running in the background and that are needed for future features such as colonies. This will need a mix of optimizations and adjustments to the plan to be able to have something that can scale with future updates of the game. As with other areas we are exploring both short term improvements and long term solutions to the challenge.

The game not opening anymore never happened to us and I am not sure why. This issue is not new, it's been there for a long time. We are glad some one noticed it. Checking the registry is not a common test case but it will definitely be now!

We usually don't estimate bugs because the solution to the bug is not always obvious so I don't have those stats. Almost every sprint has some bugs scheduled to be worked on. We do meet every week to look at incoming bugs and prioritize them and every sprint we pick the top priority stuff from the backlog. Some interesting stats from this release cycle, about 4 out of 5 of the check-ins to the repository did not make it to the patch notes. Those check-ins will include internal bug fixes and feature work for future versions. It also includes other stuff as localization, project cleanup, art source files, etc.

You would have to convince @Nertea about it.

That is one of the ones next in the list to get fixed.

Not other projects but other features. We are always looking for a balance between doing fixes for the next minor update vs future features such as heat, science and others. We are constantly looking at the top reported bugs and we try to fix as many of those as time and other priorities allow.

Number 5 Number 6, it was wrongly classified and didn't make it to the patch notes. It is fixed. Number 15, it was wrongly classified and didn't make it to the patch notes. It is fixed. Number 20

We identified and removed two issues that were slowing down the game but even after that, there is still a difference in perf between 0.1.3.2 and 0.1.4.0 that we want to keep investigating and fix in upcoming patches. It is not a general thing, some players might notice it and others might not but it is definitely there so we will continue looking for the changes that are dragging us back.

Please do, and also vote on the ones you care about.

I don't want to spoil the interview. @TriggerAu will also do a better job at explaining it than me.

Some additional context on some of these: Orbital Decay. The team has identified one source contributing to the orbital drift and fixed it. Unfortunately that has not fixed drift in all situations. The team continues to investigate other sources for orbital drift. Undock/Decouple/Physicsless Parts causing Crafts to Fall Apart. As we have mentioned before, these type of issues have more than one source causing them. We keep working on fixing them one by one. Let us know if you see this still happening and in which conditions.

It usually means we were able to reproduce it, it is tracked and it is going through the process. It will eventually be scheduled to be worked on depending on a lot of factors. It does not reproduce in the AMD hardware we have available to us.

Hey, I want to provide additional context on the status of some of these. Wobbly Rockets - Unfortunately there is no easy solution here. We are testing a bunch of ideas internally and we will assess from there. Orbital Decay - At some point some of us thought this would be fixed by some other work around orbits but unfortunately that was not the case. Engineers have been working on this area for over a month, trying different methods and finding new challenges to deal with. They are still doing as much as possible to get this fixed ASAP. Graphic Glitches on AMD Hardware - This one has been a sneaky one. So far we have not been able to reproduce internally. We have a theory about it and we are also working with AMD on it. Engine Sound Effects Not Playing - This one has also been hard to reproduce but we have a fix that we hope will help.

I will keep that in mind next time.

I mentioned a few weeks ago that we are trying find a balance between bug fixing, performance improvements, new content and update releasing. That means that we are making progress in all of the above but probably none of them is as fast as people would like to. We have been sharing more on the bug fixing side because we have seen a lot of interest in that area but that doesn't mean we are not making progress in other areas. We are actually making very good progress on Science and we already have a bunch of stuff ready to be shared in the following weeks (if you don't mind us showing in-progress stuff). On Re-entry, the team working on that has been exploring several solutions but they all come with challenges and they are working through those challenges in order to pick the best solution. There is great material for a future Dev post for sure.

Devs have different skills, only a handful of people have the right skills to work on those bugs. The rest are working on stuff that is adequate for their skills. People working on new parts has no impact on those orbit bugs being fixed sooner or later. The right people are working on those bugs and we will let you know once we are certain about the fix.

Update 0.1.3.0 will include new parts, as we've said we are trying to balance new content, bug fixing, performance improvements and science development. I can confirm that all of those are being worked on right now.

Nice catch, yes Ryan recently joined the team.

Not yet, we do have that one on our list though.

We are aware of that one and we are working on it.