Mitokandria

Thank you so much!!!! Please more hotfixes for the majour issues in the future? I'll give it a playthrough later after I've had my ksp1 fun for the day.

Yeah I kinda do the same for now. I do keep hoping after each update that maybe I can enjoy a game session for longer than an hour before a game/craft/crew-ending bug. I'll of course be back at the next update to play a bit more.

Sad face. Tried to intercept and dock with a transfer stage rocket. At 0.5 m/s the active vessel exploded on contact and sent the other vessel rocketing in the other direction. Guess I'll go back to KSP1 for awhile longer. Looking forward to the next patch in 2 months, but will be pleasantly surprised if there is a hotfix in the interim. (pls?)

After further troubleshooting the issue occurs with all coupler types (Stack, Radial, Stack Separators, and ports). The issue does not require staging only activation either through staging or parts manager. Minimum Setup for replication: any probe core or cockpit, any antenna, any (de)coupler.

Appears to be caused by decouplers. EC acts as expected until initiating decoupling. Setup: Any probe core, any antenna, and any stack decoupler on the bottom. Replication: Launch vehicle on launchpad. Stage decoupler. Time Warp to see EC is no longer being consumed or produced. I have not tried yet with stack separators or docking ports. Will test that shortly.

Experiencing the same thing. Just sent a vessel to the Mun with no solar panels and a small battery.

Looking great so far. Would love to be able to sort by votes.

I wish I had seen this before I scrapped the save as "unrecoverable". I was so upset that such a long mission (and subsequent recovery mission) was so bugged by the time I got the designs for a rescue mission and launched that I deleted the whole save file.

I also tried to do the same thing when I first got KSP2. I still try to do it every now and then before I sigh and have to go directly to the node, zoom in & out at weird angles to keep things in view.

I have a habit of cutting filler words when typing so that may have come out differently. I meant "This is the next best thing to a separate and dedicated (aka not a forum) public bug tracker". "This" being the in-progress sneak peak we were given. Did that come across better?

I'm looking forward to June 20. Thank you so much for this new format of updates. I find it all super fascinating to see how things are going with bugsfixes and their causes so I can squirrel it away as a nugget of wisdom for later. I think tuning out for a few weeks or a month and then coming back to read through the updates has given me some peace with the progress. Thanks for working so hard devteam and community managers!

The next best thing to a separate public bug tracker. I'm greatly looking forward to any form of implementation along this line. Will also likely start reporting bugs again if something like this is implemented.

I may have miscommunicated. This post is the "sometimes diry dev process" that I like and would like to see more in this fashion. I like numbers and formulas. When I say "dirty" I mean the thought processes and ideas that sometimes end up being left on the cutting room floor due to being out of scope or doesn't fit into the game. I suppose an example of this might be sharing some of the possible sources of the bugs they are working on or the methods they are trying out to work through a particularly tricky "accidental feature".

Am a hobbyist programmer and aspiring systems engineer. Being that this is an engineering game I think the community (or at least me) would love to hear more of the nitty gritty from dev logs. Not just the "what" and "when" but also the "why" and "how". Let us in on some of that juicy, crunchy, and sometimes dirty dev process and not just the squeaky clean PR fluff. This post is is a wonderful place to start! I know I already posted once but just wanted to say thank you again!

Thank you I really appreciate this style of update. This is all I really wanted out of these weekly updates. Looking forward to some sort of public facing bug tracker so we know what is and is not confirmed by the dev team or what needs more data.

Does such a patch exist yet? I was reviewing antenna choices and realized I can't use these antennas with my remote tech constellation. I also don't know the broadcast ranges.

Looks like the way ResearchBodies awards Science doesn't work with Play Your Way. Would this be a bug or maybe just a comparability issue?

Peek in at update. See there's very little substance. Go back to playing KSP1 still. Not upset I bought an EA game. It's always a gamble and I accept that KSP2 is....kinda bad right now. I can't really play the game as-is without running into a game breaking bug right now (tried to play last week, but my first ship got the fairing bug in VAB and had to Alt+F4). But I am hopeful that a year from now maybe the game will be enjoyable for me. This is not meant to be sarcasm, just downcast acceptance of the situation.

Confirming that I'm also getting a 404.

@JadeOfMaarThank you! That is so much better than any chicken-scratch I would have been able to put together.

I would really appreciate that. I have memory issues and since the parts do not have what they input/output outside of the VAB I have a very difficult time using them appropriately.

Is there a picture showing the conversion chain for TAC-LS convertors?

Is there a way to change the timescale for remote tech to match RSS (24h) or JNSQ (12h)?

Finally got my first rover on the Mun. That was one hell of a trial! Makes me really appreciate just how much blood, sweat, tears, green, and metal goes into navigating in space! A month ago I didn't care about SpaceX's latest rocket test. Watching another SpaceX launch today? Today I saw one of my failed attempts with JNSQ to get my tiny rover into space.