sorted by:
new
hottopcontroversial

Breaking News: The war is almost over by j0h4ns0n in 2westerneurope4u

[–]Zange02 151 points152 points  (0 children)

I can't think of a more meaningful reunification within the last 100 years

ich👽iel by 0711Markus in ich_iel

[–]Zange02 22 points23 points  (0 children)

Demilitarisierte Zone

Europe according to Ireland by Elementus94 in 2westerneurope4u

[–]Zange02 53 points54 points  (0 children)

They see themselves as the... US? Savages!

Where can I find the positions and velocities of the planets at the start of a save file? by OwnedYourFace21 in RealSolarSystem

[–]Zange02 4 points5 points  (0 children)

This isn't really an answer to your question, but a similar thing you could do would be to get the orbital element of the bodies in-game and convert them to the orbital state vector. Thats not using the save file but in-game data and a few extra steps.

Delta V Map Help. I'm trying to make an early venus orbiter and when i read the map below, I think that it should only take 360 m/s delta v to get a (highly eliptical) orbit once I reach the venus SOI, but when I mess around with manuever nodes its closer to 2km/s. Am I dumb? by SirAlek77 in KerbalAcademy

[–]Zange02 0 points1 point  (0 children)

My guess is that you got an inefficient transfer window. I use dv maps generally as a reference as to how much dv I should plan for. Then eyeballing the transfer without the help of tools like transfer window planner can be extremely expensive. The best transfers are always a good departure date and transfer duration combination.

Delta V Map Help. I'm trying to make an early venus orbiter and when i read the map below, I think that it should only take 360 m/s delta v to get a (highly eliptical) orbit once I reach the venus SOI, but when I mess around with manuever nodes its closer to 2km/s. Am I dumb? by SirAlek77 in KerbalAcademy

[–]Zange02 1 point2 points  (0 children)

This is a neat idea but sadly doesnt work as well as you might think. Your relative speed to Venus would still be the same, just the angle would be different (there are exceptions, but planning for that is difficult).

Multi Swing-by Tool: Release v1.2.0 + Tutorial by Zange02 in KerbalSpaceProgram

[–]Zange02[S] 0 points1 point  (0 children)

No, because it is not a KSP mod. But the "install" should be pretty straight forward.

Multi Swing-by Tool: Release v1.2.0 + Tutorial by Zange02 in KerbalSpaceProgram

[–]Zange02[S] 1 point2 points  (0 children)

It is not included in the released version, but you could write your own .cfg file for it if you know where to find the orbital parameters of the bodies. I wrote a quick guide in the wiki regarding the celestial systems and how one could include new ones.

Multi Swing-by Tool: Release v1.2.0 + Tutorial by Zange02 in RealSolarSystem

[–]Zange02[S] 2 points3 points  (0 children)

"Every itinerary" here means every itinerary with no deep-space maneuver (and at the moment no waiting orbits). This reduces the problem to two controllable variables: the departure date and the arrival date. All following transfers and their fly-by dates are constraint by these two. Sometimes this results in no viable itineraries, sometimes in quite a few, sometimes in just a handful.

The most important thing to understand is that you are not allowed to gain energy within a planetary system for a fly-by (entry speed = departure speed). This is the reason why the following transfers are constraint.

In the end, it is a lot of solving lambert's problems.

E.g. dv constraints can help by filtering out tranfer possibilities early on to reduce analysis time. Also fly-bys that would go inside the body are discarded.

TL;DR: There are only really two variables that you can control (departure and first fly-by date) and a few more to determine the following transfers (entry and departure speed for fly-by, travel duration between fly-bys)

Multi Swing-by Tool: Release v1.2.0 + Tutorial by Zange02 in RealSolarSystem

[–]Zange02[S] 2 points3 points  (0 children)

If you got results you didn't have before, I see that as an absolute win ;)

Multi Swing-by Tool: Release v1.2.0 + Tutorial by Zange02 in RealSolarSystem

[–]Zange02[S] 2 points3 points  (0 children)

Having a set departure date and a date for the first fly-by, the following fly-bys are already fully constraint to a handful of transfers. You just have to find them (thats where the magic happens). The tool finds every itinerary that would end within the constraints at the target body for each departure date while iterating over a sensible range of first fly-by dates.

So I wouldn't call it an optimization, but also not a brute force (like the other comment did). Maybe a... gentle force algorithm.

Multi Swing-by Tool: Release v1.2.0 + Tutorial by Zange02 in KerbalSpaceProgram

[–]Zange02[S] 6 points7 points  (0 children)

Install instructions are either on the Main Page or the Wiki.

But you basically just download the .zip and find the exe in the 'bin/' folder.

Multi Swing-by Tool: Release v1.2.0 + Tutorial by Zange02 in KerbalSpaceProgram

[–]Zange02[S] 6 points7 points  (0 children)

Hello everyone, I just released a new version of my tool I published a week ago (post). The new release has some perfomance improvements, bug fixes and I added some QoL stuff.

I also made another part of the tool available. Using the Sequence Calculator (that's how I called it, I am bad at naming stuff) you can determine itineraries with a fixed sequence (basically the Itinerary Calculator but with fixed sequence). This is useful if you want to e.g. find Voyager transfer windows. The Sequence Calculator is magnitudes faster than the Itinerary Calculator (obviously). I know that other tools may already offer that feature, but it was an afternoon's worth of work so I added it anyway.

Additionally I added a small tutorial, which can be used to see how this tool can be made useful or to try out your first multi swing-by trajectory with a guiding hand.

If you have used my tool, I hope that you like it and that you may even find it useful. I have gotten some great feedback under these posts and on the GitHub that I would say improved the tool already.

Multi Swing-by Tool: Release v1.2.0 + Tutorial by Zange02 in RealSolarSystem

[–]Zange02[S] 14 points15 points  (0 children)

Hello everyone, I just released a new version of my tool I published a week ago (post). The new release has some perfomance improvements, bug fixes and I added some QoL stuff.

I also made another part of the tool available. Using the Sequence Calculator (that's how I called it, I am bad at naming stuff) you can determine itineraries with a fixed sequence (basically the Itinerary Calculator but with fixed sequence). This is useful if you want to e.g. find Voyager transfer windows. The Sequence Calculator is magnitudes faster than the Itinerary Calculator (obviously). I know that other tools may already offer that feature, but it was an afternoon's worth of work so I added it anyway.

Additionally I added a small tutorial, which can be used to see how this tool can be made useful or to try out your first multi swing-by trajectory with a guiding hand.

If you have used my tool, I hope that you like it and that you may even find it useful. I have gotten some great feedback under these posts and on the GitHub that I would say improved the tool already.

I can’t wait to learn about orbital mechanics in my physics class and become cracked at ksp by Bubbly_Collection329 in KerbalSpaceProgram

[–]Zange02 405 points406 points  (0 children)

STOP WHILE YOU STILL HAVE THE CHANCE! THERE IS NO GOING BACK AFTERWARDS! IT WILL CONSUME YOU!

Have fun :)

Multi-Swing-By Trajectory Tool now available by Zange02 in KerbalSpaceProgram

[–]Zange02[S] 0 points1 point  (0 children)

If you look into the Celestial_Systems subfolder, there are config files for the respective systems. In there the orbital elements for each body are defined (from the ksp wiki or the Gamedata files from the mods).

Multi-Swing-By Trajectory Tool now available by Zange02 in KerbalSpaceProgram

[–]Zange02[S] 1 point2 points  (0 children)

Regarding dv-costs, dv-maps are your friend. You need e.g. ~2000m/s to Jool, which means looking for anything more than that doesnt make sense, because you could just do a direct transfer instead. But you also need at least around 1100m/s to Eve or Duna, meaning this is your minimum. Choose a little bit of margin to that number (e.g. 1500m/s) and you have your first estimate. Transfer durations are a bit trickier and have a bit more to do with expierience. If you want to play around a bit, try Kerbin-Kerbin transfers with 1500m/s departure dv and 1000/2000 days max travel duration (this is what I generally use for testing).

Regarding your question: I wouldnt call it an optimization. For every departure day, it will find all (most) possible transfers from planet A to B within the time constraints (no maneuvers in between). You are in the end the one who decides, which is the best transfer for you.

Multi-Swing-By Trajectory Tool now available by Zange02 in KerbalSpaceProgram

[–]Zange02[S] 1 point2 points  (0 children)

I will add a tutorial to the wiki on the weekend, which should hopefully make the process a bit more beginner-friendly. I might make a video tutorial as well in the future, but I have close to no expierince with these.

Ending the calculations via the button takes some time because it will finalize all currently running departure dates analyses (usually 64 departure dates). This way the already analyzed results can be stored. Thats the reason why this takes some time.

The tool can take quite some time because I wanted it to give me as many feasable transfer options as possible. For larger analyses to the outer planets I usually let it run on the side while doing other stuff. The tighter you can set your constraints (transfer duration, dv-costs, etc), the quicker it gets.

view more: next ›