Arrowstar

Not really, no. It's not too bad, just play with it for a bit and see how it works. Some learning will be involved.

Take a look at the software I wrote and linked to in my signature. It includes codes that attempts to find flybys of planets for gravity assist maneuvers.

Great, thanks! I look forward to the addition.

Regex, could we get a text field in the main display window that shows the current UT and/or Year/Day/Time? Would be really handy for fast forwarding to certain points in the future for optimal departure. It really is one of the best features of MechJeb and pretty much the only thing missing from what you've got here (which is quite lovely, I might add). Given the current date/time and UT I would never have to touch MJ again.

Not outside of something I saw on the KSP subreddit. Still, try visiting the Mun in a different location and see if that helps.

The moon has something like 8 different biomes. Have you been to all of them?

When in doubt, just run fuel lines both ways.

Last week on KospY's github, I saw he committed some fixes for issues like these. Maybe a new version is coming soon with fixes. KospY, any thoughts?

Hey guys, thanks for all your comments. I have been keeping up with them, though life has been busy lately. I'm also in bit of a KSP lull and I haven't had the creativity to do any active development work on KSP TOT. I haven't given up on it and it's not going away, I just needed to take a break for a while. I suspect I'll jump back in after I've had a chance to have fun with 0.22 and get back into KSP. Hang tight until then.

I suspect they're normalized values. So 255 = 1, 0 = 0, etc. Just take your 0-255 number and divide by 255.

Anyone know if Episode 1 is coming today?

They didn't forget, they just didn't tell us. No idea why though as it only hurts them...

I do find it a bit strange that we're less than 24 hours away from the stream (probably) and we still don't have a time yet. It's going to be awfully hard for some people to plan to make it if they don't know when it'll be happening...

During the last live stream, Harv mentioned "DLC" and the community went wild. It was not pretty. They basically shut the streams down to prevent that kind of thing from happening again. Hopefully things go a bit better this time.

Community projects are doomed to fail. The mod should be left to a sole individual who has full authority over it (and may subsequently hire on additional developers as he/she sees fit). If this mod goes to a "design by committee" philosophy, I'm not sure it'll ever get any better. Nope, the solution is to give one talented person with vision the keys and let them take it from there. Mind you, I don't want to completely remove the idea of forking KAS, but I think the "unforked" version should go exclusively to someone else.

Cool. Anything you can show us from the art pass?

Hi Majiir! Is there any news w.r.t. the upcoming 0.8 release?

They also showed sub-assembly loading and saving.

And again, apologies for the lack of formatting.

In the OP I have a link to a tutorial post that explains how to use the output. Take a look here: http://forum.kerbalspaceprogram.com/showthread.php/36476-WIN-KSP-Trajectory-Optimization-Tool-v0-8-Now-with-Flyby-Maneuver-Sequencing!?p=517457&viewfull=1#post517457 I'll take a look into your bug and see what I can't find. Thanks for reporting it. At this time it's not possible to plan more than one flyby at a time. I've addressed this earlier, but basically it comes down to the complexity of the problem. It's really hard for an optimizer to come up with a good solution to a problem like what you're suggesting. I did some testing with just two flyby bodies a while back and the results weren't very useable. Long story short, I probably won't do something like what you're suggesting because it's pretty hard to do.

I just saw this on their Twitter: Somnambulant Gamer â€Â@SomnamGamer 3m Just had a great time talking .22 and more with @KerbalSpaceP. Awesome things ahead! Retweeted by Kerbal Space Program

You may have to adjust the departure time by a few seconds and/or play with the prograde delta-v by a few meters per second. Moho moves quite fast and has a small SoI, making it difficult to reach. Nevertheless, I've done it with KSP TOT a few times, so I know it's possible. The problem is that there is no inbound orbital plane defined. With a flyby, I know which direction I'm coming in at and which I'm leaving at, and the cross product of those two gives me an orbital plane I can use. Here, where I only have an inbound velocity vector, there are a number of solutions and just no way to define which plane you're on. This is why I don't have any arrival information in KSP TOT: it's quite hard with the standard two body model. Thanks!

There was something mentioned about some 0.22 information being revealed at a convention. Has that happened? If not, is there a schedule for it? If so, can we see it?

Sorry about the bad formatting, btw, the forum isn't tracking my line breaks for some reason....

1) Yeah, I could do something like that. It'd just be in the Enter UT as Date/Time dialog box, but I can I see how it'd be useful. 2) An option for this exists in the options menu. Edit -> Options. You can also right-click on the porkchop plot and click Recenter At or something like that to move the plot. 3) I'd rather not use buttons. My goal with context menus was to remove stuff like that from the main GUI where things can get cluttered. Right now I don't have any documentation, but eventually context menus will be documented. Maybe I'll add some tooltips though. 4) You're doing something wrong. The dot with Moho's position is where Moho is at your departure, not your arrival at Moho. 1) Actually, it's pretty hard or impossible to know the arrival hyperbolic trajectory. On the flyby trajectory in the FMS, I have a lot more information to work with and that gives me the flyby trajectory (input and output hyperbolic excess velocity vectors). That information doesn't exist for just arrival, though, so I'd have to make a lot of assumptions about how your inbound trajectory looked at arrival. It's just not worth it because it's going to be wrong anyway. 2) The scoring for the FMS is the sum of the departure, arrival, and flyby delta-vs. It attempts to minimize that quantity. (Mind you, the departure/arrival delta-vs are just "sun-centered" velocity changes because I don't actually know the departure and arrival orbits at that point.)