Project

General

Profile

Bug #28071

The stock alarm clock and transfer window planner do not work and are completely wrong all the time.

Added by Screeno over 3 years ago. Updated almost 3 years ago.

Status:
New
Severity:
Low
Assignee:
-
Category:
UI
Target version:
-
Start date:
06/26/2021
% Done:

0%

Version:
Platform:
Windows
Expansion:
Breaking Ground, Core Game, Making History
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

The stock alarm clock doesn't find accurate interplanetary transfers windows, but the original mod does.

I don't know if the maneuver tool is correct but it sets transfer dates either in the past or far in the future, in reference to the transfer windows that the stock alarm clock is setting (incorrect ones)

History

#1 Updated by jclovis3 over 3 years ago

I just tried this today with a sandbox game and ran into two problems. The first of which might match your report. In orbit of "The Mun" I set a transfer to Minmus, but the maneuver node it created only made a wider orbit around "The Mun" which took oddly many days to to the maneuver node (several orbits around the Mun). Then from there, it said it could not calculate a transfer to Minmus due to the high eccentricity. So I normalized the orbit again and tried once more. The second time got me to Minmus, but is was pretty far out. I only had to continue to thrust a little longer to come closer and then adjusted when I got there; no biggie.

The real problem, which might be another bug entirely, is when I tried to transfer to Eve. I couldn't do it from Minmus as that was not an option. Same while in orbit of Kerbin (no option for other planets). Then after leaving Kerbin SOI I got a transfer to Eve that looked OK, but before I could move the map around and look at it, the game froze. Task manager showed memory consumption going through the roof and when my system memory had exceeded 60 GB (out of 64 GB installed) I ended the task manually (it was listed as not responding). I was going to see if this repeats before generating a report.

I uploaded a video of the memory leak in action: https://youtu.be/ra2rhM3gsLc

#2 Updated by immolated over 3 years ago

Confirmed

#3 Updated by ElectroLlama almost 3 years ago

Confirmed on Linux v1.12.3
see #28431 and #28171 for other confirmations and comments, including a possible reason.

Also available in: Atom PDF