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
As per title, when creating a flight plan, if the only mean of thrust currently active is RCS but no port is facing prograde, adding any dV to the manouver will cause the flight plan duration to increase by 24k days
This causes massive lag until the flight plan is shortened again manually.
Also clicking "0" on the flight plan never works, this message always pops up, even with no manoeuvres present, this is unrelated to the issue described earlier.
The text was updated successfully, but these errors were encountered:
For the first part of your issue, there is a safeguard in place, and it worked: The flight plan only got calculated—and rendered—to 22 hours, which is limited by the Max. steps per segment setting. It is surprising that showing 22 hours of LEO is too laggy, though as discussed on Discord, it is true that rendering shows far more points than is useful, and happens in the UI thread.
For the second part of your issue, good point. The 0 makes no sense here and should go away.
Update: @ezsnackeur reports that something must be slipping past the safeguard. On an empty flight plan with a max steps of 1024, setting the plan length to 25 thousand days apparently causes noticeable lag.
As per title, when creating a flight plan, if the only mean of thrust currently active is RCS but no port is facing prograde, adding any dV to the manouver will cause the flight plan duration to increase by 24k days
This causes massive lag until the flight plan is shortened again manually.
Also clicking "0" on the flight plan never works, this message always pops up, even with no manoeuvres present, this is unrelated to the issue described earlier.
The text was updated successfully, but these errors were encountered: