Why is this mission not being marked as complete?

[Proe24]

As you can see, I have reached all of the goals of this mission (after much trial and error and constant reworking of my orbit), however, the mission will not mark as complete.

I can't seem to figure out what it is that I am doing wrong, I have looked over my orbit info and compared it with the required orbit info and I can't find where I've fallen short.

Any help would be appreciated! I just want to finish this damn mission and move on!

[technicalfool]

Just an idea, but is your craft travelling the right way around? You wouldn't be the first person to get confused by having an orbit that has an inclination of exactly 180 degrees away from the required inclination. Check the map view to see what way around the little moving points on the orbit are travelling.

[FancyMouse]

No the orbit info shows 0.003 inclination so the direction should be correct, unless the display mod has a bug.

How does the orbit look like in orbit view?

[Kryxal]

That's the only thing I can think of, too ... that the argument of periapsis is wrong in some way. If the orbits match well in map view (and they ARE the same way around, so the numbers say) you may have to just use the cheat menu (and I checked that the celestial body was right too ... it is).

[stibbons]

Sometimes it can be worth switching to the tracking station and back again to unstick contracts like that (I've only had this happen once, but that helped). Failing that, you're justified bringing up the debug menu and cheating the contract to completion.

[Proe24]

Thanks for all of the replies!

I checked in map mode and here is what it looks like. I can't seem to find anything wrong with it, but I'm not sure what difference I would be looking for, I suppose I'm kind of a noob in that aspect. If it is a correctable human error then I definitely want to try to fix it without cheating, but I'm thinking that it might be something else.

Here are the two images from map mode, one from close up and one with Kerbin in view.

[FancyMouse]

It's definitely a different algorithm for computing argument of periapsis (game is counting toward one direction while MJ is counting the other way).

Just eyeball your orbit, as we all do.

[DeMatt]

As FancyMouse said, MechJeb is apparently computing "argument of periapsis" differently from how the game is. Which is why your #2 screenshot, from just above the Mun, quite clearly shows that your orbit does not match the purple "target" orbit.

Just eyeball it. Make your orbit circular at the target apoapsis height, then burn at the target apoapsis to adjust the periapsis down. I think there's a 7% margin of error on the "marginal deviation", so it doesn't have to be super-precise.

[Rhomphaia]

MechJeb calculates AoP the same way as the game

Argument of periapsis is the angle between the Ascending node and the periapsis.

I suspect that while the contract says Longitude of Ascending Node is "undefined" (since an equatorial orbit should have no Acending node) it does not mean it is irrelevant and expects you to match its LAN as well. (probably 0)

[FancyMouse]

MechJeb calculates AoP the same way as the game

Argument of periapsis is the angle between the Ascending node and the periapsis.

I suspect that while the contract says Longitude of Ascending Node is "undefined" (since an equatorial orbit should have no Acending node) it does not mean it is irrelevant and expects you to match its LAN as well. (probably 0)

It's undefined because inclination is 0, in which case AN doesn't make sense (there's no AN node at all). Has nothing to do contract criteria - I believe all of us completed countless zero-inclination contracts.

It's definitely argument of periapsis problem - see the orbits are perfectly vertically mirrored. That's exactly you count 300 degress in different directions from 12 o'clock. It is different, whether it's MJ different from game, or game internal different from contract display, one of them.

[Superfluous J]

As others have said, turn MechJeb off for this one and just get your orbit moderately close to the target. Once you've done one or two of these by eye they're the easiest money in the game.

[maltesh]

MechJeb calculates AoP the same way as the game

Argument of periapsis is the angle between the Ascending node and the periapsis.

I suspect that while the contract says Longitude of Ascending Node is "undefined" (since an equatorial orbit should have no Acending node) it does not mean it is irrelevant and expects you to match its LAN as well. (probably 0)

Yep, when the orbit is in the reference plane, the convention is to use the reference direction as the location of the ascending node, which would be a Longitude of the Ascending Node of 0°. The game does this as well when storing and restoring orbits in the persistence file. For whatever reason, it's the contract display code that's decided that's an Undefined LAN.

[Proe24]

Thanks again for all of the replies, the problem was just as was said above, so I matched with the other orbit by eyeballing it and completed the contract, finally!