Jump to content

PLAD

Members
  • Content Count

    333
  • Joined

  • Last visited

Everything posted by PLAD

  1. 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.
  2. 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
  3. 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 K
  4. 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
  5. 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
  6. 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.
  7. 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.
  8. 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.
  9. 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 lau
  10. 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 file
  11. 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
  12. 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 ch
  13. 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 t
  14. 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
  15. 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.
  16. This works for setting up flybys too. I'm in the middle of a Earth-Venus-Mars, land, Mars-Earth mission and I used it to set up the Earth launch and departure (as usual), the Venus flyby, and the Mars orbit selection. I realized I can always find an arrival orbit that will pass through a given DA line, you just might not be able to reach everywhere on the planet from that orbit. On setting up a flyby it doesn't give a perfect DA direction because my arrival energy will probably never be exactly right for a given transfer, but it is so close that it is easy and fast to fine tune the flyby using
  17. Looks like you Ninja's me. Here is a little album showing what I have in mind but I shall download what you just made and look at it now. Adding the periapsis circle sounds nice, that is basically the departure circle in reverse I think. Let me study your work before I say anything else. edit: OK, I ran it and that is superb! It did just what I wanted, I've put 2 more frames in the album above that show it worked. I went into an orbit around Mars that crossed the AD line your addon gave, then set up a node for execution 18 months later with the magnitude that FF gave me for the
  18. 1. I would have to select the planet independently of the SOI I'm currently in. For instance if I am currently in the Sun's SOI while traveling from Kerbin to Duna I want to see the departure asymptote (DA) for a future trip from Duna back to Kerbin. That way I can make a mid-course correction to adjust my incoming (to Duna) path to cross the DA, which makes it possible for my future Duna-Kerbin burn to be as inexpensive as possible. 2. I don't need the future ejection trajectory, just the straight line of the DA. You are right that if I go into an elliptical orbit I would need to set the
  19. Yup, you would have to eyeball the solar inclination after a flyby, and usually it will only be a couple of degrees. The ony time I think it might be useful is when there is a very high inclination generated by a gas giant. Note that the inclination of a prograde flight is alway positive x degrees, so I'd have to find a way to tell if the flight goes South of the ecliptic or North of it during the transfer to the next planet or it wouldn't be too useful. That error is troublesome, if that is common and not a high-Z flight then I would want to fix it. If you find something like that I wou
  20. I got slightly different results from Zhetaan on the lowest dV K-D-K flight in the first window and the lowest flyby altitude flight. You can see the Flyby Finder readouts along with images of what the flights look like in the game. I'm using the latest KSP and v0.85 of Flyby Finder, maybe that was different? His start date and flyby date are right on. Both flights leave on the same day and fly by Duna on practically the same day (at vastly different altitudes), but the arrival times back at Kerbin are different. Check out the last panel though, there are many di
  21. I think we are talking about different inclinations, I mean the inclination relative to the flyby planet while you are in its SOI, I think you mean the inclination of the solar orbit between the flyby planet and the destination planet. You must approach a planet from a specific direction, but you can tweak the flyby so it is over, under, East, or West of the planet so the flyby path can have any LAN or inclination relative to the planet. But you are right, the solar orbit between flybys or encounters is set by the encounter times. So I think you would want a new line that says something like:
  22. Hello Okder, I still use your addon everytime I start a flyby mission, I'm glad you are keeping it updated. I have a suggestion for a new function if you are looking for ideas from your users. Here's the quick version- I'd like a way to enter a start date and start planet, then an arrival date and arrival planet, and then see the departure asymptote line for the transfer projected onto the start planet. I won't need delta-v info, or a drawing of the departure orbit itself, just the asymptote line. There will be the complication that the Lambert finds two solutions but I'd only want the sola
  23. It's a good suggestion, I have spent quite a bit of time sometimes trying to find the proper flyby to get me to the next planet at the right time. It's easy when the flight stays near the ecliptic plane, but sometimes a gas giant flyby will surprise me by needing to send the ship on a path way above the ecliptic, and that can be really hard to find. The problem though is that knowing the inclination of the flyby to the planet is of limited use when you don't know the LAN of the flyby path, and most of all because I can't see the inclination or LAN of my flyby until I am in the SOI of the flyby
  24. The link to the latest version of Flyby Finder, 0.85, is available in the first post of this thread.
  25. TOT and Flyby Finder, both mentioned above, are the two tools I know of for planning flybys in KSP. I've done Kerbin-Duna-Jool and as mentioned above Duna does not give you much of a push, it reduces the roughly 2000 m/s a direct flight to Jool would need to roughly 1900 m/s. On the other hand it is easier and much faster to execute than the more powerful Kerbin-Eve-Kerbin-Jool route so you might want to try K-D-J first.
×
×
  • Create New...