PLAD

OK. It's weird though, I can see the imgur primer just fine by clicking on the link, but I know there are so many possible security settings and ways of linking to something that it won't always work on all devices. A simple link to the primer Now a spoiler-style link: -PLAD PS-Here is a link to execution of an Earth-Venus-Mars, land, Mars-Earth mission using Okder's addon. Going Kerbin-Eve-Duna-Kerbin in stock is a similar mission.

Hello, sorry, no. Those are great packs but I already have FF for 5 different systems and it is too much for me to keep track of any more (every time something updates I have to install it and check flybys around every planet to make sure nothing has changed, or figure out and test and release a new version.) The supported packs are: Stock KSP Outer Planets mod Real Solar System Kerbol Star System Galileo Planet Pack (1x) GPP 10.625x -PLAD

Yup, in the OP I link to a primer on using it. Okder's Mechjeb addon makes it much easier to determine the best launch time and start orbit inclination and LAN to get into, link is at the bottom of the OP and a couple of examples in using it are in that thread. You can see typical values to use when searching for flybys in the various flyby reports I've done over the years, here are some examples: Kerbin-Duna-Kerbin : Here K-E-K-Jool: here If you look further through my older adventures be aware that I used to use "Earth Time" (365-day years, 24-hour days) even in stock Kerbal so the the search date values will be wrong for modern KSP and its 6-hour days and 426-day years. -PLAD

I have released versions of Flyby Finder and the Lambert and Moonfinder spreadsheets for GPP version 1.5.x with the 10.625x rescale only. They are in the OP above. Note that I assume the user will install Kronometer and therefore have 347-day years for Gael. In earlier versions of the 10.625x rescale this time change was put in automatically, now you have to install Kronometer yourself. GPP v1.5 moved most of the planet start positions, so all the flyby paths I had used so far are obsolete. A quick check shows Tellumo is still the boss for throwing you to other planets, and the gas giants are even better positioned for an early grand tour. No plans for other rescales right now, they have custom day lengths as well as custom year lengths so will take more time.

I've updated FF to work with the latest version of the GPP. FF v0.86 is for stock-scale GPP v1.5x. Keep using FF 0.85 if you are using an earlier version of GPP. Two small changes were made to the detail box- Vinf out has been removed since it was redundant with Vinf in, and I added total travel time in years to the summary. It already had total travel time in days but for long voyages years seemed useful. -PLAD

It would be an honor! Or if more a more formal reply is needed I authorize anyone to use that picture any way they see fit. Especially Galileo.

Just look at it... Taken during a very low 10.625x Tellumo flyby. Look at the feathering in the planet's shadow, as if some parts of the ring are thicker than others. Did you design that in or is it luck? And then the probe spotted Beautiful work.

Here is a flight from Gael to Tellumo-Niven-Icarus. This is the lowest-dV way I've found to get to Icarus launching in the first year. This one takes 5618m/s from a 240x240km Gael orbit, but at the end of the album I show the next GTNI window that can get you there for about 4880m/s in year 5. https://imgur.com/a/dfCz4 Note that it is hard to do a giant burn accurately, I had to do a 100m/s correction right after I finished the burn because of burn time and position inaccuracy, but after that it was less than 10m/s total for all the rest of the course corrections.

I have released a version of Flyby Finder that is just for GPP with the 10.625x rescale. It is here. Also there is a version of my Moonfinder spreadsheet for Gael 10.625x, and a version of my Lambert spreadsheet for GPP 10.625. For those using stock GPP regular Flyby Finder is still the place to go. I don't know if I'll make ones for other rescales since I have to play them first, and once you've gone full scale it's hard to go back to the little ones as @Yakvi said. FF is most useful for the full scale in my opinion, especially in the GPP system. In other news I made a rocket to launch from 10.625x Tellumo's surface to orbit. It was much easier than I anticipated because of the launch site I chose, it was at 9600 meters ASL and the air pressure up there is only 70KP, less than at Earth's surface! It is 1013KP at sea level, I'll probably try launching a rocket from there next. But because of the low air pressure up high, which drops off very quickly relative to Earth or Gael, a rocket can accelerate brutally fairly early and not burn up. I wouldn't want to ride it mind you, two stages hit 7 gs during the ascent. As an aside it is hilarious to launch this thing on Gael, it burns and explodes pretty quickly. https://imgur.com/a/wlIfi Now the problem is landing something big enough to get back to orbit from orbit. It would be easy to land low with the thick air as a cushion, but takeoff needs to be high up. *Note-launching from Tellumo's equator gives you 580m/s to start with, which is nice.

This is a set of tools to use with the 10.625x rescale of the Galileo Planet Pack only. If you re using stock GPP then you must use the standard Flyby Finder available here. Tools for the Real Solar System mod are here. I don't offer any other rescales at this time. GPP 10.625x uses a custom time scale with 24 hour days and a 347-day year, and I have to tweak some other parameters to fit the giant size of this solar system. Here is Flyby Finder itself, I'm assuming that by the time you get here you have used it in stock, if not the instructions are in this thread. The following files are for GPP versions 1.2.2 and 1.4 (with the 10.625x rescale) Executable: https://www.dropbox.com/s/fop7rdzdql9z0ah/Flyby085GPP106xExe.zip?dl=0 Source Code: https://www.dropbox.com/s/g21ig7ieb7z51ps/Flyby085GPP106xSource.zip?dl=0 Next is my Moonfinder spreadsheet, this tells you the next time to launch due East into an orbit that will allow an efficient transfer to Iota, and the next time to launch into the plane of Ceti. it's taken straight from the version for RSS that is in the FFRSS thread. https://www.dropbox.com/s/tpu8wyrrqhdxgts/GaelMoonfinderC10X.xls?dl=0 Finally here is my Lambert spreadsheet modfied for GPP 10.625. This is tricky to use but powerful, it helps to have a fair understanding of astrodynamics to use it. https://www.dropbox.com/s/pwoo8k6dbvcg1h2/LambertGalileo10625Xb.xls?dl=0 GPP version 1.5.x moved the starting positions of the planets so a new version of FF is required for it. The following files are for GPP version 1.5.x, 10.625x rescale only. Flyby Finder and Moonfinder assume you have installed Kronometer and have the 347-day Gael years only! Executable: https://www.dropbox.com/s/r7bbu2hq9eriasl/Flyby086GPP150r10625exe.zip?dl=0 Source code: https://www.dropbox.com/s/lymue9g31brkl6p/Flyby085GPP150Res10625source.zip?dl=0 Moonfinder spreadsheet: https://www.dropbox.com/s/hc173ls95439zhh/Gael150MoonfinderD10625X.xls?dl=0 Lambert spreadsheet: https://www.dropbox.com/s/ac01ibhr6onwhfp/LambertGPP15010625X.xls?dl=0 okder has made a Mechjeb addon tool that makes finding the best time and orbit to launch into when starting a mission, and it now can help you set up flybys as well. I use it 100% of the time for interplanetary flights. Try it out! PLAD

Yes, thanks, I am going to need it. I just have to know what it would take for some hapless species that evolves on a planet like this to get into space. First will be building anything that can go surface to orbit, and then 2nd trying to fly that from Gael's surface to Tellumo. I calculate a Tellumo orbital speed of 14,011 m/s at 90km altitude, and then the gravity and drag losses should be savage. With a surface gravity of 1.9 the TWR will need to be well over 2 all the way... I'm not above trying an Orion with realistic stats. I was worrying about entering the atmosphere at the 20km/s that you get when falling from infinity, but then I remembered the Galileo Jupiter atmosphere probe hit Jupiter at 47km/s and survived, so it's reasonable (though it was 45% heat shield by mass).

I'm working on a version of Flyby Finder just for 10.625x GPP. A question-I'm using my RO mods and configs so I'm sticking with KSP 1.2.2 and therefore GPP 1.2.3 for now. I see no .cfg changes to the planet orbit parameters in stock or 10.625x between the GPP1.2.3 and 1.4 versions. (Things related to rotation don't matter to FF.) Is there anything that isn't visible in the rescale files that changed between the two? For instance the atmosphere heights get multiplied by 1.8 in 1.2.3 but I can't see that number in the rescale files or Sigma configs. I can't think of much else that could have changed, but I got thrown for a loop when KSP slightly changed the value of big G a couple of versions ago. I'd like to be able to claim FF GPP 10.625x is good for both 1.2.3 and 1.4 without having to build a KSP1.3 RO setup. Tellumo is awesome in 10.625x, that giant rock can throw you all over the place. For 4800m/s from a 200km orbit you can go Gael-Tellumo-Niven-Icarus (though you'll fly by Icarus at 27 km/s). But how will one return from a trip to Tellumo's surface?!?

As some have noted, it can be time-consuming to set up a flyby when you only know the flyby altitude. However, okder has updated his Mechjeb addon to add a graphical departure asymptote indicator. This makes it much easier to set up a flyby path past the intermediate planets. (It also has some other uses, more details below.) Here is a little primer on how to use it. https://imgur.com/a/MzWwR This little album shows more detail on using it to plan a future departure from a planet you are arriving at. https://imgur.com/a/vSGZB I experimented with putting more info in FF's text output, like the inclination of the transfer orbit from one planet to another, but this graphical indicator is much easier to use. It works with stock, RSS and other planet packs. Note you will need Mechjeb in order to use this. The biggest trick is deciding whether to use the short path or long path when setting up a flyby. Long path means you will go more than 180 degrees around the sun during the transfer, short path means less than 180. For a given flight one of them will require you to go retrograde around the sun, that is the wrong way. Looking at the number in the '"boost from circular" field will tell you which that is because the retrograde path will have a much higher value than the prograde one.

As @aluc24 and others have noted, it can be time-consuming to set up a flyby when you only know the flyby altitude. However, okder has updated his Mechjeb addon to add a graphical departure asymptote indicator. This makes it much easier to set up a flyby path past the intermediate planets. (It also has some other uses, more details below.) Here is a little primer on how to use it. https://imgur.com/a/MzWwR This little album shows more detail on using it to plan a future departure from a planet you are arriving at. https://imgur.com/a/vSGZB I experimented with putting more info in FF's text output, like the inclination of the transfer orbit from one planet to another, but this graphical indicator is much easier to use. It works with RSS and other planet packs as well. Note you will need Mechjeb in order to use this. The biggest trick is deciding whether to use the short path or long path when setting up a flyby. Long path means you will go more than 180 degrees around the sun during the transfer, short path means less than 180. For a given flight one of them will require you to go retrograde around the sun, that is the wrong way. Looking at the number in the '"boost from circular" field will tell you which that is because the retrograde path will have a much higher value than the prograde one.

Hello @okder, I just wanted to say that I have tried this with stock KSP, RSS/RO, GPP, and the GPP 10.625x rescale and it works well with all of them. I use it for all my interplanetary flights now including simple 2-body transfers, since the launch guidance, transfer node, and correction node work for any flight whether it will lead to a flyby or not. It also greatly simplifies setting up a flyby, I don't bother to try setting one up without it now. Thanks again for this.