What's with the burn planner?

[Guest]

I was planning an Eeloo encounter. Ballistic transfer, burn is about 3,600 m/s, burn time about 5:30. It's a tricky one because I'm ejecting about 25 degrees normal, so I can't just follow prograde like I would otherwis3e. 

The problem is that when I actually execute the burn, keeping the craft pointed at the maneuver marker on the navball, it's not even close to the plan. So badly off that I might as well have eyeballed it.

Am I missing something or is this just bugged or not working as intended?

[The Aziz]

Report it. I don't know where's the difference but long transfer burns seem inaccurate - but capture burns are nearly perfect.

[Superfluous J]

I've had my maneuver pointer on the navball (which the "aim at" button will aim at) be wrong after time warp. F5/F9 fixes it.

[Guest]

A-ha, I'll try again without timewarping, see if it's more accurate. I will write up a report after I've done that!

[Scarecrow71]

There are several reports about warping under acceleration not being accurate.  Which needs to get fixed before interstellar comes online.

[kdaviper]

On 1/9/2024 at 8:56 AM, Scarecrow71 said:

There are several reports about warping under acceleration not being accurate.  Which needs to get fixed before interstellar comes online.

Did my first 4-minute burn last night with a NERV-powered craft and the burn was nearly perfect. Used time warp for most of it too.

[MechBFP]

2 hours ago, kdaviper said:

Did my first 4-minute burn last night with a NERV-powered craft and the burn was nearly perfect. Used time warp for most of it too.

Sometimes the command pod or probe core or whatever is the point of control will get offset from the vertical center of the vehicle, completely screwing up the navball. That is likely what happened here.

Edited January 10, 2024 by MechBFP

[kdaviper]

7 hours ago, MechBFP said:

Sometimes the command pod or probe core or whatever is the point of control will get offset from the vertical center of the vehicle, completely screwing up the navball. That is likely what happened here.

I mean I didn't have any issues whatsoever. I must have been lucky not to encounter such a bug