Yes I have a long term plan of doing high efficiency trips with massive rockets in future.
The Oberth effect messes with my plan to map the ΔV boost effect. Depending on the starting point, it could have a huge affect on the map. This is one of the complications I have to deal with.
Yes, I have seen many ΔV charts, but what I working on is a gravity assist chart which shows ΔV boost with each flyby, depending on some characteristic which is easily measured in game. This may be impossible to chart, unless I can work out some standard procedure for removing extraneous effects. Oberth, dwell angle, insertion angle, are all difficult to measure in game, particularly if your own orbit is elliptical. If I have a standard LEO of 31km perfect circlular orbit as my starting point, I will eliminate the variation of Oberth affect from my tests.
The insertion angle is key to determining the magnitude of the boost affect, but so far the only way to adjust this, is by changeing the dwell angle, how long after the encounter window opens, before doing the initial burn. Once we are already on the Interplanetary Network, dwell angle will be impossible to measure, as we have already entered the SOI with some variable insertion angle.
We could get a protractor to measure the angle on the screen, but that is some crazy level of play style. I think what I will be doing is baseing the chart off rocket speed, altitude, periapsis, or something else which is a close approximation, and is easy to read in game.
I don't want to detract from the VEEGA approach, I think it is a very straight forward method for getting onto the Interplanetary Network from LEO, and which most people can easily grasp. I am interested in mapping what happens after that first flyby of Venus, weather that is towards a second Venus flyby, the first Earth flyby, or a flyby of Mercury. Mapping that second leg is going to help people like me who want to go places other than Jupiter on a regular basis.
That said, I don't need to do this. I could just use Veega to get to Jupiter and wing it from there. Since I plan to visit at least 12 planets outside the Solar System, having a very efficient chart will have a huge effect on how much fuel I will have left when I arrive at each Super Earth.
I am still working on my Modded map of the Galaxy. Since there are dozens of recently discovered Super Earths, I don't think I can add them all. I have arbitrarily set a boundry of about 20LY, any Super Earths within 20LY of the Solar System are already on my map. As is their parent star. I am hesitant to add neighbouring stars and planets, because each additional object is extra processing load on my old phone.
That said, I am still learning to mod SFS, but have already worked out how to delete clouds and fog. I am not sure how much effect this will have on my processor, as the best way to measure is to zoom out and run timewarp at max speed until the game locks up. Since the size of the custom map affects the maximum timewarp, this is another crucial factor for my own galaxy design.
I am keen to learn more about modding later, as I already have a very long to do list for SFS, so BOT? I want to make a boost chart which can be used for any planet/star combination, which will be some heavy matrix calculations in a spreadsheet. I am considering using google docs with an Automatically scaling graph. When the crucial parameters are entered for the three bodies in question, it refreshes the graph. This would be my dream result, but it may not be possible, despite SFS being 2D with no ecliptic planets.
The Oberth effect messes with my plan to map the ΔV boost effect. Depending on the starting point, it could have a huge affect on the map. This is one of the complications I have to deal with.
Yes, I have seen many ΔV charts, but what I working on is a gravity assist chart which shows ΔV boost with each flyby, depending on some characteristic which is easily measured in game. This may be impossible to chart, unless I can work out some standard procedure for removing extraneous effects. Oberth, dwell angle, insertion angle, are all difficult to measure in game, particularly if your own orbit is elliptical. If I have a standard LEO of 31km perfect circlular orbit as my starting point, I will eliminate the variation of Oberth affect from my tests.
The insertion angle is key to determining the magnitude of the boost affect, but so far the only way to adjust this, is by changeing the dwell angle, how long after the encounter window opens, before doing the initial burn. Once we are already on the Interplanetary Network, dwell angle will be impossible to measure, as we have already entered the SOI with some variable insertion angle.
We could get a protractor to measure the angle on the screen, but that is some crazy level of play style. I think what I will be doing is baseing the chart off rocket speed, altitude, periapsis, or something else which is a close approximation, and is easy to read in game.
I don't want to detract from the VEEGA approach, I think it is a very straight forward method for getting onto the Interplanetary Network from LEO, and which most people can easily grasp. I am interested in mapping what happens after that first flyby of Venus, weather that is towards a second Venus flyby, the first Earth flyby, or a flyby of Mercury. Mapping that second leg is going to help people like me who want to go places other than Jupiter on a regular basis.
That said, I don't need to do this. I could just use Veega to get to Jupiter and wing it from there. Since I plan to visit at least 12 planets outside the Solar System, having a very efficient chart will have a huge effect on how much fuel I will have left when I arrive at each Super Earth.
I am still working on my Modded map of the Galaxy. Since there are dozens of recently discovered Super Earths, I don't think I can add them all. I have arbitrarily set a boundry of about 20LY, any Super Earths within 20LY of the Solar System are already on my map. As is their parent star. I am hesitant to add neighbouring stars and planets, because each additional object is extra processing load on my old phone.
That said, I am still learning to mod SFS, but have already worked out how to delete clouds and fog. I am not sure how much effect this will have on my processor, as the best way to measure is to zoom out and run timewarp at max speed until the game locks up. Since the size of the custom map affects the maximum timewarp, this is another crucial factor for my own galaxy design.
I am keen to learn more about modding later, as I already have a very long to do list for SFS, so BOT? I want to make a boost chart which can be used for any planet/star combination, which will be some heavy matrix calculations in a spreadsheet. I am considering using google docs with an Automatically scaling graph. When the crucial parameters are entered for the three bodies in question, it refreshes the graph. This would be my dream result, but it may not be possible, despite SFS being 2D with no ecliptic planets.
