Cheaterman

Chasing some magic smoke on Gentoo Linux? /me high fives steve Join us on Freenode buddi :-) (btw I'm here because I have the bug too)

Hey djungelorm, Just wanted to thank you for the awesome mod, I made a neat little autopilot with it: http://imgur.com/a/wQC6m (source: https://github.com/Cheaterman/kautopilly ) I'll add support for orbital maneuvers and more neat stuff in the future. Stay tuned! :-)

"only" 20 passenger space although you could easily make it 36, and more fuel than needed to fly around Kerbin four times or so (call it unlimited range). Can land anywhere too (17.5m/s vertical speed tested, nothing broke) :

Hello, Settings aren't saved in my fresh install of KSP (from zip file). I tried removing settings.cfg, changing its permissions, etc... to no avail. I wouldn't say no settings are persisted at all though - when I start the game, it's fullscreen, at my desktop resolution... and half the time I don't get the "send statistics" dialog. Even though I don't get the dialogs, still important settings such as terrain quality (which is the main setting to lower in my situation, Intel HD 4000 is so slow whenever I have terrain in sight) aren't kept after I closed the game. Please help! Thanks in advance!

Weirdly I feel the same, it's like my Evian system missions always go right, my Duna missions are okay, my Joolian missions are good, but my Moho/Eelo missions always fail! I didn't try a Dres mission yet and will actually do it immediately, just to know how it goes.

Build cheap and small rockets like the MNMS from the americans - but even smaller, I want payloads in the hundreds of grams and I want operating costs to be as low as the price of a good car. Make it affordable enough to sell "NASA KITS" to KSP users to have their own satellite and run a space program from their garage. Earn loads of money contributing to the Kessler syndrome. Use this money to design lower weight life support systems, and send them into space using the R&D you invested for your small rockets - scale them up a bit (even JPL scales things down in the wind tunnel), and put a few humans into orbit. Oh and earn 10 extra millions as a prize if you can make it happen again less than two weeks later IIRC. Since these persons would be tourists, they'd pay much more for their ticket anyways.

I used to support such threads, but nowadays I'm more like "okay put L1 and L2 [for each body that needs it] as invisible SOIs": you get in there using Hohmann, do a capture burn, and voilà.

I actually posted a thread myself explaining RK4 and showing the solution to a n-to-1 body physics problem. However the issue here is that you'll need to be able to change the current ("on-rails") trajectory while warping - assuming you can do it, you'd simply need to integrate enough. And to solve the potential CPU performance issues, just consider the bodies in the adjacent system - ie, Duna doesn't affect you in Kerbin's SOI while both Kerbin and Duna would while you're orbiting Kerbol (this is to ignore Jool's Moons most of the time - they would not influence you as long as you're not orbiting Jool itself).

Make it do a round trip to Jool and post screens. That's how you become famous here

Thou shall avoid cross-bracing moar than once even if it looks awwwesome, for this very reason. Keeping the part count low in general is an extremely good advice - when you're ready for it, see Scott Manley's smallest interplanetary vehicle. Oh and very important: as someone mentioned above, when you found better ways of doing things, screw the rules and do it your way. If you can handle lower simplicity for instance, go for efficiency, etc - shaving off the 300kg of that handy reaction wheel you used on your interplanetary spacecraft for instance (not a great example though - rather lower the delta V budget of your payload/interplanetary stage to ~10% fuel margin first if you can).

Brotoro - nice, but I think we should rather assume that non-weightless fundamental particles basically weight 10 times heavier in the Kerbol system. As such, consider Jool as being a Jupiter-massive-planet. Other than that, Laythe doesn't have a moon (a protoplanet collision would melt the planet and force heavier elements near the center), and its ground colour (when not standing in the sand) suggests that heavy materials exist on the surface, therefore not forming a huge, rotating, conductive core like Earth, that would deflect whatever radiation Jool would throw at it (that is - according to the Solar system - about 1.5 times as powerful as whatever Kerbol would carry from such a distance). Indeed, life in the oceans of Laythe is non-optional: it resides too close to the Kerper Belt (HarvesteR said long ago they will put asteroïds in KSP) for not having experienced comet/asteroid collision, leading to amino acids presence in the water. However, radiation would destroy nucleic acid if life was to come out of the oceans, so I guess it's indeed confined there.

Most valid if Jeb - or any orange suited. It's really funny how this turns into a flame war so quickly. The case you presented has a low probability in itself, and honestly I'd rather launch the rescue mission if I can. Other than that, I like the idea, and it's cool that a mod is planned since its drawbacks will prevent it from being added to the stock game (namely - low interest/challenge and high development time to make things deep and proper).

If he needs a hand coding/bugfixing, I'd be glad to help, as everything is on GitHub, I'd just need a few tips to get started as not to waste time reading the whole code if I can avoid it

Haven't tested the mod yet - love you already for being an IT engineer and would have had developed this myself if time constraints allowed! THANKS A LOT!!!

OMFG Norad II!!! /me WANTS!!!

Quick, dirty and easy fix: put a few rotation wheels & RTGs near the center of mass of your craft. Results guaranteed!

I meant applying it to the trajectory marker but thanks for pointing it out - however for clarity let's keep in mind planets wouldn't have to (shouldn't) use the n-body physics but would stay on rails, decreasing needed computation, not mentioning how current timewarp is incredibly less resource-intensive than physics-enabled modes which leaves a lot of margin for new systems to be implemented. - Actually now that I think about it, wouldn't this (doing prediction) be the tricky part with n-body systems? (although not impossible at all since planets would remain on rails)

Considering we're talking about an engine causing a series of nuclear explosions and forces its dampener to withstand several dozen G's every 3 seconds or so, not mentioning most of my KSP rockets built with this fall apart on takeoff, this is one of the best quotes ever. If you don't consider the extra isp.

I understood what makes it algorithmically difficult - integrating is hard (but there's RK4 etc...). However for this latter issue, keeping the planets on rails would be a solution

Hello dear KSP community, The following paper (apparently from the Harvard NASA lab) describes a solution to the n-body gravity problem: http://articles.adsabs.harvard.edu/cgi-bin/nph-iarticle_query?bibcode=1991CeMDA..50...73W&db_key=AST&page_ind=0&data_type=GIF&type=SCREEN_VIEW&classic=YES So why wouldn't we apply this to the rails, in order to make interesting realistic slingshots possible? Like Mariner 10 or Voyager... Not like these aren't possible yet, but dynamic rails would be cool Disclaimer: I didn't understand much about the paper, but from a purely computer-oriented perspective doing sums of sums in a linked list of gravitational bodies seems piece of cake compared to all HarvesteR&Co have already done, this is why I proposed it

I'm working on a ridiculously fast and agile SSTO, it features two turbojet and 9 intakes, weights around 5.5 tons, and gets to orbit very easily (MECO (well AECO -atmospheric engine cut off-) @ 65km alt. & 2.3km.s^-1 or so, the apo was like 150km) and... lacks energy, or a pilot, or both. I'll add a few passive solar panels. Oh and it goes at mach 1 at about 5.5km alt that's just how powerful it is. (mach 3 @ 10km or so) If you want the craft file, just ask

If your main concern is efficiency, you will want to: - Circularize as low as possible around Kerbin (75km) - Do a Hohmann transfer that puts you on low Munar altitude (10km, even 5 if you're badass like Jeb) and circularize there - Then aim for your landing site - it doesn't matter how far from the landing site you do it, further will give you more time to react though - however if you make it too far your path will come across some craters... - Suicidal burn is best, leave that to MechJeb though - at this point you'll have saved enough dV to be able to do a manual landing without considerable waste. - Enjoy!

That especially makes sense since HarvesteR stated some time ago that most of the content that was initially planned will probably instead be implemented through expansion packs. Economically, it does make a lot more sense.

That's pretty much the hammock example again! We could also take a skateboarder on a half pipe: it's more efficient -assuming his foot can be faster than the max speed he's moving at- to accelerate more at the lower point of the half pipe than pushing himself further in the air when he's at the top.

I certainly expected some people not to understand