You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Landing trajectory is calculated incorrectly on minmus highlands, at least near the following two points:
LAT: 65 LNG: -105
LAT: 4.2 LNG: -65.5
All the other biomes (except Slopes - haven't tested it yet) seem to be fine on Minmus - I've tried a single point for each biome.
"Time to impact" is reported by Trajectories mod to be much more than zero at the time an actual impact happens, and trajectory is incoherent with the calculated point of impact (see screenshot).
Vanilla game HUD ground radar shows correct height of 0m at the moment of impact.
Screenshot
On the screenshot (LAT: 4.2 LNG: -65.5) impact is imminent, but Trajectories reports 27 seconds till impact. Probe's shadow on the screenshot estimates impact point well, but trajectory drawn goes long below the ground (panning the camera makes it obvious; it's not occluded by the ground either), and projected impact point is way off it.
Versions
KSP 1.8.1, Trajectories 2.3
The text was updated successfully, but these errors were encountered:
Landing trajectory is calculated incorrectly on minmus highlands, at least near the following two points:
All the other biomes (except Slopes - haven't tested it yet) seem to be fine on Minmus - I've tried a single point for each biome.
"Time to impact" is reported by Trajectories mod to be much more than zero at the time an actual impact happens, and trajectory is incoherent with the calculated point of impact (see screenshot).
Vanilla game HUD ground radar shows correct height of
0m
at the moment of impact.Screenshot
On the screenshot (LAT: 4.2 LNG: -65.5) impact is imminent, but Trajectories reports 27 seconds till impact. Probe's shadow on the screenshot estimates impact point well, but trajectory drawn goes long below the ground (panning the camera makes it obvious; it's not occluded by the ground either), and projected impact point is way off it.
Versions
KSP 1.8.1, Trajectories 2.3
The text was updated successfully, but these errors were encountered: