attosecond

Different thread models, perhaps? The only commonality in the hardware described in this thread is AMD processors. Seems like a known processor issue that causes hiccups would be a good place to look... lowest hanging fruit and all.

Seems more like it's a CPU-bound problem than anything else.

There is a known issue with AMD Ryzen processors using their firmware trusted platform modules (fTPM): it causes stuttering. See this article: https://www.tomshardware.com/news/amd-issues-fix-and-workaround-for-ftpm-stuttering-issues

From the link that @Wylegposted, words about EA directly from Steam: "Early Access is a place for games that are in a playable alpha or beta state, are worth the current value of the playable build, and that you plan to continue to develop for release." Is KSP2 worth $50 in its current state? Debatable. Is KSP2 in a playable alpha or beta state? Yes.

@Nate Simpsonthank you for the transparency - those of us who have participated in beta programs before understand that there are processes in place to turn feedback into action, and that it takes variable amounts of person-hours to root out and squash each bug found. Perhaps this has been requested before, but I'm far too lazy to read through every post, so I'll make the following suggestion/request: Please consider providing a community update on current activities on a set cadence - once per week, for example. Here's the part I'd like to stress: publish your intent to update weekly (or bi-weekly, or whatever) and stick to that schedule. Make the post with your intended schedule sticky at the top of a sub-forum. Much of the angst expressed in the forums would be alleviated, I think (or hope), with regular updates on what's currently on your big blackboard of stuff to do. Details with timelines are obviously a mistake, but a running list of current tasks with no timelines seems appropriate. The important piece is keeping the communications flowing.

This actually bugs me.... a lot. Steam lets me choose the installation directory for the game, which in my case is on a separate physical drive from my OS drive. I want control over where the game saves are going, also. Burying them deep inside a hidden folder (AppData) on my primary drive with no option for changing the location feels wrong. What was wrong with the way KSP1 did things? Each copy of KSP1 had its own saves folder structure, so there was never a need to worry about my RSS install overwriting my crazy no-holds-barred FTL install saves.

Kerbal Alarm Clock was a must-have for many years in KSP1. 100% on board for KAC2!

I had this also... circularized at 30km and saved. When I returned and loaded the craft, the PE was negative. Re-circularized and changed focus to another craft, and looking at the misbehaving one in map view it didn't have a trajectory line. Switched back, and the PE was negative again.

I had this happen, too. Restart of the game got rid of it.

Same just happened to me... critical bug that makes the game unplayable when it happens. All that time spent in VAB and the only solution seems to be to start fresh with a new vehicle. Ugh.

I am excited for interstellar travel and all the challenges it will offer. I'm also looking forward to a new look and feel and the promise of better, more consistent resource utilization for unloaded crafts.

There's quite a bit we don't know about Stardriver ICF fusion reactors, too. Didn't stop them from modeling it and showing us the visuals (non-symmetric beam configuration is a head-scratcher).

space elevators, with appropriate apparent gravitational field physics.

No change to the wobbling behavior, unfortunately. That seems to have fixed it, thanks! Unsure why the jump from 1.18.3 to 1.19.1 would have exposed this issue. Scatterer has been part of my modkit for a long time and hasn't been updated in a while. *shrug*

1.19.1 made all the planetary bodies wobble in both flight and map scenes for me. Didn't notice any FPS improvements that would make the wobble worth it, so reverting to 1.18.3 for now. Playing RSS/RO with Parallax and PRVE.