Curveball Anders

Do you really think that a studio that has no previous experience in developing software for consoles would be able to do a better and/or faster job than a studio dedicated at console development? I sure don't think so. Outsourcing porting doesn't absolve Squad from responsibility in any way, regardless of contractor. But what Squad did wrong was choosing the wrong contractor for the initial port (FTE). Once the first (not very good ...) ports where released to the public they had no choice but either continue to pour money into FTE, hoping that they could fix the port, or drop them and redo the port with a new contractor. It would probably been cheaper for Squad to pay FTE (or hire someone else) to patch the initial port to a 'reasonably' functional state (as in good enough not to get sued) but that would have left their customers with a bad, if not obviously broken, product. Instead they decided to bite the bullet, take the economical hit and pay a new contractor (Blitworks) to do a proper port more or less from scratch. I've been involved in way to many projects where the management have decided go the cheaper route, refusing to accept that the horse is lame, and chosen to dope it so it stumbles across the finishing line. Only to fall down dead once across the line. So while the current situation is annoying and frustrating I would have loved to have that commitment from management in those 'yes it's a donkey, but let's paint it silver, stick on a carrot and try to pass it off as a small unicorn'-projects ...

I do it the other way around. I mainly use career, but uses a sandbox for experiments and 'tests' when I run into trouble.

Since I suck at graphic design I always nick a logo/flag from some organisation that I like (or I find funny). Then I invent a name that matches the logo/flag

1.3.0 All mods I wanted updated automagically with CKAN.

Since it doesn't seem to be the actual reads from the disk and the CPU goes up quite drastic I'd guess that it's related to some form of 'unpacking' of the data.

Exactly so. My point was that Blitworks can't shout "Woohoo! We're done!" (or done in a week, a month or a year) because it has to be accepted by Squad first. And Squad can't shout "Woohoo! We're done!" (or done in a week, a month or a year) because nothing will be released until it has passed certification by MS and Sony (and at least when it comes to Sony it's individual certification per region ...). Which is why the progress reports that we get are "Whee! It's getting closer!" ...

1m47s (and that's w/o SSD )

I agree that the handling of the console port(s) has been a complete and utter <expletive implied> job. But the lack of progress reports, other than "Hey, it's moving forward!", isn't unusual when several companies are involved. Squad isn't doing any actual development on the console ports, they've handed that over to Blitworks (after a less successful run with FTE). Then add that nothing gets released on consoles until it's been cleared by the powers that be at the respective console stores (MS and Sony). That setup creates a really ugly minefield for the people at marketing and/or customer interaction. Blitworks can't say much, since they are paid by Squad to deliver working ports to Squad and have no information on how Squad wants to communicate with it's users. Squad can't say much because they rely 100% on Blitworks to deliver working ports that are accepted by MS and Sony. MS and Sony can't say anything until they've got the ports to evaluate. And none of the companies involved have any interest of pointing out the other as 'the bad one' in a business relationship. So they stick to "Hey, it's moving forward!" until they have anything more solid to say. A boring but very normal state of affairs

What seems like the majority of users who doesn't seem very interested in multiplayer. Myself for one.

From start to at KSC with a small (5-ish vessels) save Unmodded: 1m13s Slightly modded: (10 mods) 1m47s KSP_x64 1.2.2 OS: Win10 Home 64bit CPU: i7-2600 (@3.4 - 3.7 GHz) RAM: 8GB (PC3-10700 (667 MHz) Dual Channel) GPU: Gainward GeForce GTX 570 HDD: 500GB Hitachi Sata2 (system and KSP on same disk)

And when said with certainty is almost always wrong "Four legs good, two legs bad" -- George Orwell - Animal Farm

Do that really work? Birds aren't normally scared off by bats, they're more scary for insects ...

I think you've missed one vital part. Most current players know English enough. Localization opens the game for all the potential players who don't think they do.

Almost all my points too (slight edit )

I hope he is: Chilling. Pondering his future. Twiddling with stuff he likes. Having a generic good time.

I stumbled over KSP in Jester's EvE blog. Downloaded the demo, got confused, used a lot of bad language, went for a pint, calmed down, paid for the game and never looked back.

Most, if not all, indie development programs starts on a wing and a prayer. KSP is no different but still started under a bit special circumstances. HarvesteR was given a limited amount of time and a sliver of budget to present his backers (actually his employers) with a business plan and a proof of concept. And that is exactly what Unity delivers better than most other engines (and better than writing from scratch (unless possibly if you're both a borderline genius _and_ your own boss)). The only reasonable time to switch away from Unity was when the project got final go ahead from the backers. But that would have meant throwing away much of the work done and restart from close to zero and that it had been included in the accepted business plan. I believe that every project lead in history have screamed "Why did we base our project on this scrap of turd!" but very few have actually decided to redo from scratch in a new environment (unless forced by extreme external circumstances). So the answer to "why Unity" is "it worked".

I like Dres because it's there and it's a challenge.

Eve of Kerbal ... Design, build and launch a ship into orbit. Then get it to market and sell it, without getting scammed or blown up

9+/10

I try reuse every bit of scrap that I launch on one way or another. Because every bit of junk that I've spent resources on getting into to space gnaws at me greedy soul when wasted or burnt. But my rabid greed is moderated with some sensibility, so I do crash (or send off into oblivion) empty stages and such (but sometimes I use empty or near empty refuellers as spare storage on stations). I then have one specific class of landers (or up-down gadgets as they are classified in my space program). This includes landers that shuttle between the surface and orbiting stations/motherships and a few very specific crew (and science) rotation vehicles (aka Soyuses).

Don't be silly, there is no underwear in space. (At least that's what George Lukas told Carrie Fisher ...)

engineer/flight director/benevolent dictator

the thousand eyes (and legs) of the illumillipede ...

Fly safe