Waxing_Kibbous

I notice when I first launch 1.1.2/1.1.3 on Ubuntu MATE I got crazy flickering, like it was trying to do 2 different window sizes- this last time I paid more attention and it was an error involving Marco, the Window manager (from Metacity). It eventually goes through to KSP and I change it to full screen, and the problem and errors go away the next time it is launched.

Nice bug crushing KSP team!

I am starting to think the extra CPU usage is caused by the new lighting system in U5, Enlighten- from a little bit of searching it appears that for some wacky reason they decided to make it use CPU instead of GPU (yes I realize CPUs are more homogeneous but still). My GPU usage in 1.1.x does seem to be down a tiny bit. Not sure what the light setup in the VAB is though, I imagine it must be simple enough? Just a guess, and most threads containing reference to high CPU and/or memory leaks are a year or two old... If you get reliable CTD or BSOD please post logs to the tracker

I think this http://bugs.kerbalspaceprogram.com/issues/7570 needs to get a higher priority regarding VAB crashes. KSP is working extra hard in the VAB now for some reason, and I'd guess crashes are either from bad code and/or overheating.

So, the two options being a) Steam users get to test beta software for a couple of weeks, guaranteeing some new bugs will be found, and b) no public testing is available at all, which would you choose? I'm thankful that people will be testing even if I can't, and I know in no time I'll have 1.1 on my machine. This really feels like a social experiment, I hope someone is taking notes. It's a video game guys, relax.

I'd love to test this, but didn't buy through Steam, so oh well. The reasoning behind the decision is perfectly solid and the fact they are putting it out there for testing pre-release is a fantastic move IMO.