Kayser

A fantastic mod! Instead of dynamic calculation of scan altitude, I would propose a fixed minimum and maximum altitude per antennae. It would mean: You have to carefully select antennae based on which body you are planning to scan, to stay out of atmosphere, inside SOI, and avoid moons. It more accurately reflects how a lens would need to stay within a distance where it can focus. Region size scanned would depend on altitude and antennae field of view. Closer = smaller region but faster speed across surface. Further away = larger region but slower speed across surface. More advanced antennae can still be "better" in terms of wider min/max altitude and FOV. Less risk of getting stuck in resonant orbit when there is no "ideal" distance to aim for. It may be easier to understand in general.

Wonderful mod!! Kudos to you. Since you asked for improvement suggestions: - An overview which shows the science collected per celestial body (in % and numbers), so you can see where you have most potential in going next. - Some marker (yellow?) next to each item if you have captured the science but not returned it to KSC, so I can see where I have gaps when I'm working on a celestial body.

Sounds like a sensible workaround.

You understood it correctly. I'm not looking for an automatic correction in terms of the results, just a correction in terms of the initial conditions. In fact, this is done natively by the game whenever you have your first maneuver node in front of you, your actual trajectory changes for some reason (e.g. you make a burn, release a stage, etc.). Then your first node will fall out of your path and be in "the air". However, if you make a slight change to that node, it will correct itself and fall back onto your actual flight path (including all the subsequent maneuvers that follow). It just doesn't work when your first node is in the past. The situation is quite common for me, when I e.g. have planned out a Hoffmann transfer with a mid-plane change. The initial burn is often a fraction of a second or a few delta-V off target, and this can mean the difference between a SOI intercept or not upon arrival. Consequently, I want to perform a correctional burn or adjust one of the later nodes, I just can't do it and see the results without re-planning all of the nodes, because I can't insert the correctional burn into the sequence or delete the initial burn without deleting all the subsequent nodes.

Thanks for the quick and verbose response. I think I got the essence of what you are saying, and I think I do understand the complications, even though I'm not into the coding of all this. The reason for asking is that I commonly come across a situation in the game where, in a series of maneuvers, the initial maneuver is not executed to perfection. This means that, the actual trajectory of the ship after the first maneuver node is not exactly the one planned, but slightly different. What I want at that point is to update the subsequent nodes to take into account the new actual flight path, and not the one that was originally planned (i.e. to simulate what would be the result if the subsequent nodes are still executed at the same time as originally planned, and maybe to be able to adjust them.) I wanted to achieve this by deleting the first node in the sequence, but since that deletes the entire sequence, it's not possible. Neither is it possible to insert a node at the beginning to play around with a correction burn and get the results to show. Only way I see is to re-make all the subsequent nodes. Maybe there's a better way to do that?

Love this mod. Semi-bug/Feature request 1: Deleting a node in a sequence deletes all subsequent nodes. I would wish it was possible to delete a node without deleting all subsequent nodes. Feature request 2: Adding a node currently adds a node last in the sequence. I would wish it would be possible to add a node in the beginning or middle of a sequence.

I just installed this and I can't see the difference between Unitverse Time and Timer. It seems Universe Time is also a Timer. Could it be that Universe Time is just mislinked to Timer, or am I doing something wrong?