Superfluous J

The poll is poorly constructed. Of course out of the choices I'd prefer one of the last 2. If the poll was instead: "How often do you actually use IVAs" I'd answer whatever was next after "never." Something like "To take the occasional screenshot or read the post-its once or twice."

Well if you allow monoprop to make course corrections, then the "only" problem is getting enough dV to get close and then tweak it.

The problem is, nobody who wants it can (or has bothered to) mod it. And while that looks like a lot, it's super simple. Plug in your planets, ignore the plot, and click "add an alarm to Kerbal Alarm Clock" (Oh, and make sure you have Kerbal Alarm Clock installed. It's awesome). Then you'll have an alarm for the next awesome transfer window. But I too think it'd be cool to, if you select a target in map mode, a little angle display comes up and shows the phase angle between your current ship (which is close to the phase angle of the planet you're orbiting) and that target with respect to the most obvious thing (planet or moon if you're both orbiting it, or sun if at least one of you is orbiting it) Like an alarm clock, dV display, digital maneuver node editor, or tool to show how atmosphere would affect your trajectory? No. You're not the only one

This is why I host my own files on my own paid-for website.

For others, go for it. For myself, I'll clip things if it's to overcome shortcomings in the UI and basic construction mechanism of the game. A perfect example is the ship in the most recent devnotes. Sepratrons integrated into the ship is something that you could do if you were working at a real space agency, but we have to stick them on the outside. So, clip them into the craft. Done and done. However, clipping 8 fuel tanks into one space? No. That's breaking the law of conservation of mass.

Without mods, you should just eyeball it, or use AlexMoon's Launch Window Planner instead which tells you the date and time to eject. With mods, you should use the in-game implementation of AlexMoon's Launch Window Planner, the Transfer Window Planner

Aha. I misread your question as "Is there any transfers from Minmus that are worth it?" which was confusing considering right before then you said that all were worth it. I think one of the big things about the Tylo/Jool thing is that at Tylo's orbit, you're actually pretty close to Jool (Compared to how close you are to Kerbin from Minmus' orbit) so you're actually getting help from the Oberth Effect from both Tylo AND Jool.

NOOOOOOOOOOOOoooooooooooooooooo....................* splat * So I do all the Mun stuff, get to Minmus, land expertly, and find out... I FORGOT THE THERMOMETERS. Why couldn't I forget the MUN thermometers? I'd have found out in the first 15 minutes and could have started over! Oh well, I'll still post it but I sadly must pull my hat from the actual ring.

I actually don't remember that pitch. I remember being able to play a not-yet-complete game years ahead of time for cheaper if I'm willing to suffer bugs. The fact that they listen to the community and sometimes decide they agree is a really weird thing to be mad at them about. They are not obligated in any way to actually implement anything that anybody suggests, even if a lot of people suggest it. If in their minds it won't fit in the game, they do in fact have the final say. And don't get me wrong. I'd love ISRU in the game. I'm hoping they put it in and it works great and is fun without being too complicated, too easy, too boring, too much of a clickfest, or anything else like that. Deep down I even think they actually are. I'm just saying, they never ever said they would. Ever*. This thread's title is not just misleading, it's a LIE. It states a faleshood. And THAT is getting me a little mad. *Except really long ago and I don't even know if they said they WOULD, just that they were planning it.

I said both of these things on the first page of this thread, and I see no reason to think either are untrue now, 16 pages later. And this is not Squad's fault. It's our fault, as a group. Squad says they're going to add an inch in the game, we get mad at them for not implementing a mile.

Sweet! But one question... Why not just within, say, 5 meters of a lat/long and "landed"? Then you sidestep the whole "The waypoint is underground!" issue.

I recorded video and took snapshots of the launch and Mun ejection of my hopeful get-all-biomes-from-mun-minmus-and-kerbin mission. It was I think 700 parts, though lots of those were struts and solar panels Laggy as all get out but flew pretty well. I also landed in 2 mun biomes and hope to have the rest recorded by next week.

Yeah it works. I made a (really bad) claw-based crane where the whole idea was to have the pivot locked on all claws and then unlock one, move what it's grabbing to where it should be, then relock it, then unlock another,move, etc. It was super clunky and not worth the effort, but it worked.

Is KER allowed? I have an idea to get all biomes from Kerbin, Mun, and Minmus but it'd require knowledge of what biome I'm over and predicted to land in, or else a TON of trial and error

I wish you could turn SAS on and off for both major systems independently. I'd personally love to be able to have SAS only use reaction wheels and not spurt monoprop everywhere when I'm trying to dock. While we're at it, I'd like to be able to only use monoprop for translating if I so choose.

I don't spend much time around SOI boundaries NOT at warp so I can't tell you if it'd happen at normal time. Once I'm through a boundary, I crank the warp back up and don't sit there for 20 minutes of real time to see what would happen. However, there are more fundamental problems though I of course don't know how the code is set up or how easy anything would be to fix. Projected orbits are impossible (No entry point or periapsis shown, but just a partial trajectory and an exit point) sometimes and sometimes just vanish. Have you ever had a very close encounter planned and then you do a little burn and your projected path vanishes? That's not normal. It's been a very long standing problem that I've always assumed they didn't fix because it wasn't easy, and may require a complete rewrite... which is what you do in Beta. Which is exactly what the VAB was. It got the job done, but was clunky and error-prone. Rather than fix each error one-by-one and then eventually do a complete rewrite, they opted to live with the problems until Beta when a proper implementation could be done.

They do a fine job, indeed, but this should be stock and partless.

I would like this in staging as well, but the ability to do less than 1 second is really necessary when you're trying to synchronize stuff.

Yeah like how they just took the easy route with the editor and instead of overhauling it completely they just hacked new stuff into it. Oh wait, they didn't. I would not be surprised if every long-standing system in the game (Including trajectories, SOIs, and everything associated with them) gets a complete overhaul before 1.0 is released.

So why hasn't this guy been abducted by North Koreans yet?

I would like both, actually. Give me a hotkey AND fix the bug.

I did something similar with my car. I mounted little windmills all over it to harness the wind energy from driving to power the car. Stupid gas companies don't got nothing on me!

That would actually be really sweet. One slightly better workaround than yours though is to F5 to quicksave, then F9 to load it. Usually a bit quicker than switching ships. Just make sure you see the "saving" text! Don't want to not quicksave by accident and then quickload something from far earlier! Not that I've done that or anything...

What r4pt0r said. Life is full of people you don't like but have to get along with on a professional level to get your job done. Currently that job is school, but soon enough you'll be meeting all kinds of annoying people at work. Use this as a learning experience and in the future things will go more smoothly.