iPat

Don't know if it's been suggested, but I think it would be cool to have the option of only showing up when actually descending, so as your lander orbits Mun, the Aim trajectory doesn't show up until you make your braking/landing burn.

I'd rather see it related to crew experience rather than the tech tree. What do you think? Or could it be related to both?

I love the idea of the 'preFailureAlarm' Will players have a chance to shut down the failing engine before it explodes?

Interesting. Mine was more of a physics problem. The station would start twisting upon loading, increasingly, until it snapped apart and all of the parts then exploded. Deleting the MM cfg files fixed the problem.

I don't know if you guys have seen this, but it's a nice acceleration (or in this case, deceleration) calculator. You can enter your max acceleration according KER, and your orbit speed, and come up with a pretty good estimate of how long it will take to bleed off your horizontal velocity, and how much distance you'll cover in the process. http://keisan.casio.com/exec/system/1224829579

I think I found the problem, if not the cause. I noticed that the file "ModuleManager.Physics" in the Game Data folder had a modified date of 19 Aug 2016, which was about the time the problem arose. Deleted that file, and replaced it with an earlier copy from a Backup, and everything works fine.

I'm sorry if that was not clear. I meant to state that I had a game in progress in 1.0.5, that was fine one day. The next day, I loaded up the same game in the same 1.0.5 and everything seemed to have gone haywire. I don't believe that I altered my 1.0.5 installation in any way. The only thing that I believe I did between then and now, was run 1.1.2 once, a separate install, a separate game file.

So, in my last play in KSP 1.0.5, I docked a new module onto my space station around the Mun. But now, when I launch KSP, load up and then go to my station, it begins to twist and contort all on its own and then explodes. I relaunched KSP and tried going first to my Mun surface base, and the weird thing was, it thought that my Mun base was in motion, giving me messages like 'can't save while in motion on the surface'. I feel like the only thing I did in between docking that new station module and all the weirdness was open KSP 1.1.2 once to test the update. Is it possible that some sort of preference file got changed by 1.1.2, causing all the weirdness in 1.0.5? (…that I might just be able to delete in order to get 1.0.5 working properly again?) Thoughts?

My apologies, as it's probably already been answered somewhere in this 200-page thread, but… I run Kerbal on a little MacMini. A full install of EVE seems to be simply too much for it to handle. The one element out of all of them that I'd really like to see is the 2D cloud layer. (Volumetric clouds seem to be too much for it to process.) Could you explain for me how I might build a minimal install, that only creates the 2D cloud layers? Which components do I remove? Which ones do I need to keep? Thank you.

Launched my first ScanSat enabled satellite into a nice 120km polar orbit above Kerbin (KSP 1.0.5) Then noticed that my periapsis is slowly dropping, on the order of .1-.2 m/s. Why? Is this some sort of drag from extreme upper atmosphere? Does is have to do with Kerbin's movement around the sun? Is it a unique phenomenon only suffered by polar orbits? (Never noticed this on my space station.) Is it a bug? Any ideas?

I suspect there may be a brilliant answer to this, rendering it perhaps a dumb question, but having put my first Kerbal space station into orbit, I'm wondering why make it's orbit circular, as opposed to the elliptical one it's in now?