Known Bugs/Problems

[Clayell]

Please let me know if you have any information relating to resolving these bugs/problems.

• There is an ArgumentException related to changing the size of the UI with a button. Seems harmless, but can't figure out how to either stop it from triggering, or how to catch the exception.
  • They seem to be the result of a NRE or other exception temporarily occurring during the calculations while the window is being refreshed. This can be seen as the window briefly looking like this:
• The UI goes partially transparent after switching scenes (this seems to be a stock KSP UI bug, it happens with the RP-1 and KAC UIs at the same time)
• The entire game zooms in or out when scrolling in the settings menu. This is a stock KSP UI bug that ClickThroughBlocker unfortunately does not fix. See this.
• We have to use getPositionAtUT to predict the target body's position at a later time, which doesn't take into account perturbations of the orbit due to Principia. Principia's CelestialGetPosition doesn't seem to work for a future time, so I'm unsure how to fix this, however I've implemented the special warp mechanic that uses multiple warps to reduce errors from Principia.
  • Ballistic captures are left to the astrophysicists
• When Principia is installed, the maneuver nodes created are still stock maneuver nodes. There is currently no way to hook into Principia's maneuver system, so you will just have to manually copy the details from the stock maneuver node to the Principia node. They should have similar results in most cases.
• Eccentric parking orbits are currently unplanned, as I believe they would require a radial burn in addition to the prograde burn
  • This is especially true for launch trajectories with a periapsis below the surface of the body, or those with a burnout angle
  • Eccentric transfer orbits into final circular parking orbits before the maneuver are planned, as they don't require a radial burn as long as the maneuver is conducted in the final circular orbit (https://discord.com/channels/319857228905447436/840034852261593109/1399859055555772426)
• Instant launch windows (those without a phasing angle at all) are currently unplanned, as I believe they would require a normal burn in addition to the prograde burn (or perhaps a dogleg?)
  • You can use the phase angle searcher to look for windows with a very low phase angle, which should get you close to what an instant launch window would accomplish.
• Inputting a specific Delta-V instead of a specific Flight Time is currently unplanned, as it would require a significant amount of computation
• Targeting objects with an eccentricity of 1 or above is unplanned
• Accounting for the length of a burn instead of assuming an immediate impulsive burn is unplanned, unless someone can explain the calculations needed to do it