What's the best way to find the window of a flyby orbit in RSS?

[_username]

I have been trying to solve the question for two weeks,but it seems I have not found a good solution.

A mod named Transfer Window Planner IS REALLY FIT for RSS,but it doesn't support flyby orbits. (http://forum.kerbalspaceprogram.com/threads/93115)

An application named KSP Trajectory Optimization Tool is a very great tool for squad,but when I tried it with RSS,it couldn't find a good flyby orbit. (Often need 20km/s delta-v,it is too large to be a good flyby orbit.) (http://forum.kerbalspaceprogram.com/threads/36476)

I have searched google,but I didn't find any better tools or ways.

Thank you and sorry for my bad English.

[Taki117]

Psst, I found this for you!

http://trajbrowser.arc.nasa.gov/traj_browser.php

[_username]

Psst, I found this for you!

http://trajbrowser.arc.nasa.gov/traj_browser.php

Thank you for your help.I tried it just now,it is a really good tool!

However,it limits the Launch Year. "Query error. Launch year must be between 2010 and 2040."

It may take more than 10 years to arrive Saturn,so 30 years may not be very enough.

(And the Year1 in RSS is 1951 instead of 2000.)

[Taki117]

Thank you for your help.I tried it just now,it is a really good tool!

However,it limits the Launch Year. "Query error. Launch year must be between 2010 and 2040."

It may take more than 10 years to arrive Saturn,so 30 years may not be very enough.

(And the Year1 in RSS is 1951 instead of 2000.)

The great thing about years is that they are cyclical, meaning that every so often the days of the year will line up perfectly. Back in the day there was great concern at the turn of the Millennium (Y2k) that the entire infrastructure would shut down. The year 1972 had the same calendar days of the week and month as the year 2000, meaning that any clocks could be set for 1972 instead of being allowed to roll over.

Now, using that comparison every 28 years the cycle repeats, meaning that we can roll the clock back to 1951 and predict when, in the 2000's those dates will come up again. The next date is 2035.

[_username]

The great thing about years is that they are cyclical, meaning that every so often the days of the year will line up perfectly. Back in the day there was great concern at the turn of the Millennium (Y2k) that the entire infrastructure would shut down. The year 1972 had the same calendar days of the week and month as the year 2000, meaning that any clocks could be set for 1972 instead of being allowed to roll over.

Now, using that comparison every 28 years the cycle repeats, meaning that we can roll the clock back to 1951 and predict when, in the 2000's those dates will come up again. The next date is 2035.

Thanks!

Today I tried this tool carefully,it can save 1000~3000 m/s to Mercury , 1000~2000 m/s to Jupiter and 500~1500 m/s to Saturn.

But when I want to try it in KSP,I have some trouble.

This tool only gives me "Delta-V" "C3 Energy" and "DLA",but I don't know how to get the "Prograde Normal Radius" delta-v information.

What's the way to get the information?

[NathanKell]

While KSP Trajectory Optimization Tool may not be the best, you might try the one for Orbiter by the same author. That uses real planets and their alignments...

[Superfluous J]

While the Transfer Window Planner doesn't have a setting to do flybys, flybys are the same as transfers without the 2nd part.

You can still use the tool and just ignore the total dV and look at the dV to eject. If it's not actually the lowest at the same place it should be close.

[metaphor]

What about this one?

Do you mean flybys as in gravity assists to get to another planet, or are you flying by your destination planet? Or do you want to end up back on Earth after a flyby? The last two are pretty simple to plan without the need of a transfer calculator.