Curveball Anders

tl:dr But good luck.

Go to Dres, grab a screenshoot for your own fun, get back without wasting Kerbals. And if you do that (within your own rules), have a beer (or a non-alcoholic beverage). It's that simple

I spend 2 hours figuring out why my MechJeb install failed, and the next 3 hour planning a trip to Dres.

If you manage to mentally survive being both 'Claw - the stock bug fixer' and 'Claw - the yellow tag Squad dev' then you'll have a very special place in many coders personal shrines The fine line between "this is broken, lets fix it" and "this appears to be broken in some installs on some platforms under some circumstances lets see if we can lock this issue down and fix it without causing any new issue in other installs on other platforms and make sure that we document what we've done" ...

'infinite' is a mathematical term, engineers deal with reality.

Grats, we all know that feeling. I've got it, I've actually got it, I can do <explitive> rocket science

There's a always Duna for a quick flyby

Questionable, since there's a lot of stuff they can add that doesn't require any more memory. x64 by itself doesn't solve any gameplay issues, it just allows the game to use more memory (and run slower, by a wee bit)

The most good looking part in KSP is the Mk.1 pod. It reminds me of all the stuff I can do in this game. Clouds and better ground I usually turn off if they interfere with my game.

I launched a science station, without an antenna ... That addition was the first part of the wet noodle (that still is alive, and wobbly, in 1.1).

Actually the 64bit binary doesn't add anything unless you mod your game past the dreaded 4 (or 3.75) border. The 64bit binary allows for more memory but also uses more memory so if anything, the 64bit binary runs slower than the 32bit one (marginally in a normal situation, but never faster).

The more cynical of us think that post the release there was no Squad employee awake (or sober enough) to write any devnotes. They've earned their break, let them enjoy it. But next week we'll go for their jugulars ...

I'm well aware that I'm part of the problem. Since I chose to pay for the game. I could be part of the solution, but I don't think Squad wants to pay for my services I've been in the role of several of our esteemed Squaddies, I know their job, I've been there. Which also allows me, as a paying customer, to whine and complain, when I like it.

Isn't that what engineers are for? (Poor Bill must have some use).

We are users of a software that we have paid for (not much but we have). We'll continue to whine, harass and ridicule Squad (once they're back from the release bash) just like any other producer of stuff that we like. And quite frankly, we have the right to complain, and they have the right to giggle and ignore us

Given that not so much has changed regarding to shaders a somewhat qualified guess is that if you had that kind of drop in FPS then you have a computer with more than one GPU and the switch to 1.1 has fooled your settings to use the lesser one.

It's hard to enter IVA in a cupola without having Chris Hadfield's voice on repeat in the back off your head.

It's a classic SciFi dream to use a comet or an asteroid as a ship/base/station. KSP allows it, I'll get around to it once I'm done with Mars/Duna (so 2020 or so).

My name is Curveball and I'm addicted to kickbacks. I've tried aspargus and similar tricks, but I keep falling off the wagon and go back to more kickbacks.

Intel graphics is fine for all serious stuff, like writing reports and getting paid. But they lack a bit for having fun (and welcome to the long standing fight if Nvidia or ATI/AMD is best for gaming, brace yourself for trolls and bad language). In all forms of computers there's a balance between speed, size, heat, cost, noise and usability. A laptop will always be restricted in some of those. So welcome to the scary world of 'gaming rigs', it's actually not as scary, nor necessarily expensive as many (including my significant other) would let you believe. A decent rig can be cobbled together for very little cash, it will perform, but it will most likely be big, noisy and have very bad battery life (as in non at all).

Holy necro (the thread is 18 months old). But what I want for christmas would be some form of construction in space (as in KIS/KAS but simpler). Like the ability to add stuff to my stations without being restricted the wet noodle docking ports.

I have a science station in orbit that looks (and behaves) like a wet noodle because I forgot to add vital parts to it when I launched it. So I had to do a rescue and add a module with the missing part. Only to realise that I've missed yet another vital part so I had to do a rescue and add yet another module with yet another missing part ... I could replace it with a new station including the missing parts, but my pride stops me and the wet noodle dangling in orbit works as a reminder to check that my next design includes all the needed parts ...

KSP has sound? (Sorry, couldn't resist a recurring meme from another part of space.)

(me bold) I feel your pain bro. I actually did a test run on my word processor / intel graphics workstation and while 1.1 works, it's a wee bit laggy. Note that the 64bit exec can both handle more memory and uses more memory in doing so. So unless you want to mod your install beyond the dreaded 4 (or 3.75) limit, use the 32 bit version. And ponder getting yourself an actual GPU, Intel graphics is fine for text, but nothing else.

Real nerds started with a Sinclair ZX-80 with 1 kB of ram, or stuff that we created ourself from chips and veroboards. So called pioneers who got C-64's or even Amigas from their parents doesn't count. Back in my days a 'portable' computer meant that it could be moved with a forklift And so on, I still have an 8" boot floppy for an 11/780 at hand ..