Manouvre node issue

[technion]

Hi,

I'm trying to understand how this can possibly happen.

I've seen it on occasion from the early beta, but right now I'm looking at the most blindingly obvious example.

• Trying to make a corrective manoeuvre to target Dres
  
• Separation: 1.3million
  
• +1dv: Separation 1.25 million
  
• +1 mode dv: separation 1.2 million
  
• +1 more dv: no separation markers any more
  

Given each single dv is clearly pushing closer, how do we get from "closing in" to "no encounter".

If it would at least show me where these things are separated I could try and fix it, but now it's just an insane guessing job and I've been resetting this node now for over an hour.

[The Aziz]

Basic question, have you tried radial and normal buttons? Sometimes that's the problem, your trajectory may be very close to the border of planet's SOI, that's why you see only about 1.2mln km periapsis.

[Warzouz]

Encounters can be glitchy. I already had encourters that I didn't get in the end, even without changing SOI...

If you need to do very small adjustements, try "Precise Node" mod (MJ has a similar feature)

When I'm in your situation

- I delai my burn and set a node closer to SOI.

- If I can't, I give prority to plane change and select the closest encounter I can get. Then I fix another node later to tweak it more.

I usually do more than 1 dV correction during flight (usually less than 5m/s). KAC mod is my friend !

[tbarcello]

Dres is tricky like that. Did you try Eeloo?

Anyhow, sometimes game will decide that your closest approach has changed, and you won't see SoI change at all. This usually happens when your inclination is different from target.

Get satisfied with that node, then do the inclination chqnge until NaN, and then change some prograde and see what happens - it will work.

- - - Updated - - -

Encounters can be glitchy. I already had encourters that I didn't get in the end, even without changing SOI...

If you need to do very small adjustements, try "Precise Node" mod (MJ has a similar feature)

When I'm in your situation

- I delai my burn and set a node closer to SOI.

- If I can't, I give prority to plane change and select the closest encounter I can get. Then I fix another node later to tweak it more.

I usually do more than 1 dV correction during flight (usually less than 5m/s). KAC mod is my friend !

He is using mod already, it's obvious.

[technion]

Thank you for that, a few radial points did the job.

But the point remains, if my current separation is X, and presumably a node doesn't move significantly further from X, shouldn't the separation markers still be there so we can look at it and identify that some radial work would do the job?

[tbarcello]

Thank you for that, a few radial points did the job.

But the point remains, if my current separation is X, and presumably a node doesn't move significantly further from X, shouldn't the separation markers still be there so we can look at it and identify that some radial work would do the job?

No closest approach - no separation, right?

[Kryxal]

Look at the target, watch the trajectory behavior as you alter the node. Assuming you use KAC, you can approximate a lower flyby and set an alarm at a time just short of the SoI change that isn't appearing. I've had similar problems with Minmus, line's one one side of the moon, goes to not intercepting, line's on the OTHER side of the moon.