Broadly, we see this as part of the Kerbal DNA, and want to preserve it in some form. A big part of what originally got many of us hooked on the original KSP was the silliness and emergent problem solving that came from playing "World of Goo" with rocket parts. Wobbly rockets are sometimes fun and funny.Docking two vessels in orbit should result in a strong, non-wobbly connection that doesn’t fold on itself as soon as the player tries to move the resulting vehicle.Wings should not require struts to stay rigid.There are some applications for which manually-applied struts should be required. For radially-attached boosters or cantilevered subassemblies with single-point radial connections, some flexibility is expected.This is especially true when neighboring inline parts are the same core size. For inline parts that are connected serially, in most applications there should be little to no flexing.For the record, this is our official view on what a successful implementation would look like, and against which we continue to measure the effectiveness of ongoing mitigation work: We have introduced a number of mitigations to address aspects of that issue (altering inertia tensor values to decrease joint issues that emerge when high-mass and low-mass parts are connected, introducing various bespoke multi-joint augmentations to areas of known over-flexibility), but we still see this as an area where major improvement is needed. In the interest of avoiding repetition, I will not re-post the current top-ten list here, as all relevant fixes will officially continue to be in QA review until the update goes live.Ī Word About Wobbly RocketsOur team shares the community view that overly-wobbly rockets are a major issue in KSP2 (it is number 10 on our top-ten issues list). On the following dev update, I’ll post our new top-ten most wanted list based on that information. Once the update is live, we will reset the upvote counters on the Bug Reports subforum on the KSP Forums and re-assess our internal priority list based on both community feedback and our own internal testing. The list of fixed items is significant for this one, but major bugs still remain (to give just one example, we still have not completed our fix for the orbital decay issue, which is number one on our priority list). We have a couple of critical bugs that we think will significantly affect the quality of the update, so we’re giving our team a couple of extra days to knock them out and test the changes.Īs always, we will post detailed patch notes when the update goes live. The release date for the v0.1.3.0 update has been revised to June 22 (a two-day delay, from next Tuesday to next Thursday). Credit to Kavaeric for this week’s update graphic remix, thank you!
0 kommentar(er)
