Ragnar

I concur. I actually opened up a text editor to specifically acknowledge and thank whoever the devs were that cycled through this event 9000 times to identify what it was. Also this one: "Fairings disable parachutes placed inside or near them, even after fairings are ejected ". Like...'near'? How near? How many times did they have to test this to nail it down. I appreciate you KSP2 dev team. This is some pretty impressive work considering the expected morale in the office as well as anybody naturally burning out any saved up time off.

I will be more committed when I can make more than single shot missions. I need to be able to refuel somewhere. Additionally on-orbit construction is still a laborous. I miss the grappler, and while docking is significantly better than it was a year ago, I still have occasional issues with docked things that won't come apart, not being able to swap control to a ship that is floating away but somehow 'still connected'.

1050 was a budget card in 2016 that has been released in 2G, 3G and 4G varients. All of which are clearly well under requirements. just loaded the game up and went from VRAM usage of 950M to 1885M just loading to the seizure warning screen. Clicked create new campagn...immediately up to 9297M. To KSC 8966M. Inside VAB 9562M. I've also run it on an old RX590 with 8GB. Performance was bad, but at least the card could fit fit the game inside it if you turn everything down. I just don't think a 1050 is going to cut it even if the GPU chip itself is capable of low framerates - it is going to choke loading things in and out of the card.