I disagree, I think that it's the procedural generation that needs to be done artfully! Unfortunately the tools and experience to be creative in this medium are a few years out :)
Is definitely good educationally, but I wouldn't use it to argue against the plans of people who build rockets for a living any more than I would use experience of playing Risk to lecture an Admiral on international warfare.
I'd argue that KSP holds as an upper limit for what's possible - if it doesn't work in KSP, it won't work in the real world (while the opposite doesn't hold true necessarily).
I wouldn't say that. SSTO's are pretty trivial in KSP (even rocket SSTO's with only classical chemical engines, none of the RAPIER/SABRE stuff).
8 Rockomax 48-7S (little orange engine, stuck on with 8 small cube struts) + 1 Rockomax X200-32 Fuel Tank (the large gray tank, one size below the big orange tank) will put a capsule in orbit around Kerbin pretty easily. No such luck in real life.
Typically KSP engines have worse performance than real engines, but Kerbin is pretty small.
> 8 Rockomax 48-7S (little orange engine, stuck on with 8 small cube struts) + 1 Rockomax X200-32 Fuel Tank (the large gray tank, one size below the big orange tank) will put a capsule in orbit around Kerbin pretty easily. No such luck in real life.
That's what I meant by 'the opposite is not necessarily true'. My argument was that if something does not work in KSP, it probably won't work in real life (which was refuted by another commenter because of missing Lagrange points). IMO it still holds true for basic rocket designs and their capabilities for LEO / GEO. To my knowledge, all real world rocket designs have been replicated in-game (albeit with much lower complexity of course) and demonstrated to work.
That makes no sense. KSP hasn't got proper aeronautics and also hasn't got n-body physics. There are plenty of things that work in the real world that would fail in KSP.
edit - and for the same reason there are also things that would work in KSP that would fail in the real world.
Not really applicable to this discussion, but one instance which is highly applicable is that you can't control two ships in KSP at once. If your lower stage needed to do a powered land which an upper stage was still accelerating into orbit, you couldn't replicate that in ksp.
> If your lower stage needed to do a powered land which an upper stage was still accelerating into orbit, you couldn't replicate that in ksp.
.. Unless your name is Scott Manley ;-). But yes, good point about Lagrangian points [1]. I wasn't aware that KSP is only a two-body-simulation - interesting how the game can hide that with its sphere of influence implementation.
Quick save at stage separation, fly the upper stages to orbit. Go back in time (reload the quicksave) and fly the upper stage back to the landing site.
How about very tight hypersonic atmospheric slingshot maneuvers using aerodynamic lift from the shockwave generated by a flexible waverider lifting body? I think it would have significant problems modeling that without some serious modding. http://en.wikipedia.org/wiki/WaveRider#Hypersonic_Sail_Waver...
Also, my point with the logic is that when looking at the differences between physics in KSP and the real world, we are dealing with overlapping, rather than nesting sets.
First time I've seen this, thanks. You certainly have a point that feasible designs in KSP vs. real world aren't completely nested. When I was arguing about KSP being an upper limit, I didn't really think about the SSTO case - at least the stock simulation certainly doesn't hold up to be able do any kind of feasibility check for horizontally launched vehicles.
I learned some C in a "101" class my first year of uni. After applying the concepts to some fun arduino projects, I responded to a craigslist post and ended up putting a few weeks free time (95% reading&learning) into an arduino device for a hobbyist. He paid me $200 + materials which was probably $3/hr but gained a lot of experience and confidence in self-teaching and project management. After this I did some small game and simulation related projects for myself to learn object-oriented concepts. Then recently I responded to an online posting for a software intern and showed them code I had written, + things I had built. They hired me and now I'm getting quality industry experience, albeit with an old technology stack.
I think that a great way for people to break into the industry is to do jobs for those who have even less software experience than themselves! These people may not pay much but they have lower expectations and will give you time to learn.
Or, you know, leave everyone to their own devices, and let people choose the fields that engage them.
blacks and whites are not equal, in metabolism, strength, ability, or anything else. They have equal rights, but this does not mean that they deserve equal representation in all fields. Those with the highest merit deserve representation. Trying to fight this simple fact is the height of folly.
