FirstSecondThird

Squad would have posted a devnote today hours ago. But it didn't happen. Which proves it's either today or tomorrow. I know Squad. I know when they are surprising us.

Yep. Nothing different in the betas for steam. Except for the usual Previous Stable Release.

I swear no prerelease today means I got excited for nothing, and I'll be real **ssed if it doesn't.

Is it me, or did the hype train just get a whole lot faster?

My explanation for that is probably they are so busy getting the prerelease up the totally forgot to do their devnotes for the daily kerbal.

The hype train's about to get a lot of fuel!!!

No devnotes = a sign. IT'S COMING. BUCKLE UP, IT'S GONNA GET REAL FAST IN HERE.

Increase the throttle to 200% We're gonna need all the speed we can gain.

MOAR SPEED

Prerelease = pooping bricks Simple as that

Aw come on!!!! It's been killing me to wait for this public prerelease. I GOTS TO KNOW WHAT 1.1 WILL BE LIKE!!!!!!!

I don't really understand why they just won't make a TextureReplacer pack for it. (They meaning community modders and such) I mean, anyone who is really good with photoshop and tracing can do it (by really good I mean near-professional-like touch to it). It would just take a lot of time though. I hate necroing, but, nobody ever thought of the TextureReplacer road. It's how several real-life space suits made it into KSP. (Well, definitely not stock KSP, but, you know what I mean).

I wonder how FAR models the aerodynamics for stuff like bullets and crap...

OpenGL does not work at all at best, at least with OpenGL 4.0 on my machine. Rather, try using -force-d3d11 as a command argument. It will further reduce memory usage when used with mods like Advanced Texture Management or TextureReplacer. It may have been shown to decrease stability of your KSP install, but remember, I am not taking responsibility for loss of SCIENCE due to the misuse of the -force-d3d11 argument to reduce memory usage.

Heheheh, yeah. <Stuff> happens; like you losing your landing legs and forcing yourself to land on your side and be stranded forever on the Mun. (True story back in 0.17)

Can someone please tell me where to opt into the 1.1 experimental branch on steam. It's says Previous Stable Release as the only opt in one. Is this the one with 1.1. bump

I'm just asking since you know how you can track Kerbals the same way you track craft; I was thinking that the game treats Kerbals as craft and that's why they are trackable. I just don't want to sound like a idiot or worse, a noob idiot.

I made a Danny-esque mass relay and shot a kerbal out of the Kerbol System. (And triggered the hell kraken.)

It saddens me to hear that Maxmaps is leaving Squad. After everything he's been through with Squad and KSP, I think this is better for both us and squad, and for him as probably he'll have more time for other things in the future and, on the bright side, to do SCIENCE! AND SOME MORE SCIENCE!

Thank you Squad! Have a Merry Xmas and a Happy New Year!

THE WAIT IS OVER, MY KSP BROTHERS AND SISTERS, FOR WE ARE NOW IN BETA. MAY THE LIVES OF ALL KERBALS ON PLANET KERBIN BE MORE STRESSING! MUAHAHAHAHA! Anyways, we are now in beta. I am very excited! See you soon Kerbonauts!

Do you have KSP 64 bits, because if you do, likely the 64 bits version is WAY too unstable to play with >4 GB of RAM. This is why 32 bits has been in use for programs since 1985. Because the virtual memory feature of Wintel PCs is not enough to stop crashes, if not, make more crashes.

Well, I have a new dynabook Tecra M10 with a Nvidia Quadro 150M and Intel Core 2 Duo Extreme with vPro technology, and it runs ksp fine with the max FPS set to 60 FPS. (I called Toshiba dynabook because in my country, that is what Toshiba markets their laptops under)

So, in career mode, you may have seen the error message saying "Insufficient Funds to launch vehicle" or something along those lines. I have seen those words before, and mostly it is with my Laythe Shuttle to transport Kerbals around the Spheroid, outpost to outpost. My one idea on how to allow even more testing of this technology is to make budget cuts on the Recovery Transponders, to allow for less of a recovery factor, whilst allowing testing when on low funds. So, never use this strategy unless you really need to!