Bug Report
Describe the bug
Documentation indicates that default value of max_time_of_flight setting should default to twice the ideal Hohmann transfer time. But see line 61 of search.ks
This results in transfers that have large radial components of their planned delta V. Usually this delta V is more than the prograde component. Total delta V can exceed 1800. In some cases it will create transfers exceeding 2000 delta V where the trajectory takes you through Kerbin.
To Reproduce
My game is in a 2.5x system, but it shouldn't matter. In a circular, equatorial orbit around Kerbin, get a transfer to the Mun.
LOCAL options is LEXICON("create_maneuver_nodes", "first",
"verbose", FALSE,
"search_duration", SHIP:OBT:PERIOD * 2.5,
"search_interval", SHIP:OBT:PERIOD * 0.01,
"final_orbit_periapsis", 50000,
"final_orbit_orientation", "retrograde"
).
Expected behavior
A maneuver with ~ 1400 delta V required for the munar injection burn.
Additional context
If you explicitly pass the
"max_time_of_flight", rsvp:ideal_hohmann_transfer_period(SHIP, Mun) * 2
the resulting transfer is "correct."
Bug Report
Describe the bug
Documentation indicates that default value of max_time_of_flight setting should default to twice the ideal Hohmann transfer time. But see line 61 of search.ks
This results in transfers that have large radial components of their planned delta V. Usually this delta V is more than the prograde component. Total delta V can exceed 1800. In some cases it will create transfers exceeding 2000 delta V where the trajectory takes you through Kerbin.
To Reproduce
My game is in a 2.5x system, but it shouldn't matter. In a circular, equatorial orbit around Kerbin, get a transfer to the Mun.
Expected behavior
A maneuver with ~ 1400 delta V required for the munar injection burn.
Additional context
If you explicitly pass the
the resulting transfer is "correct."