Mechjeb seems to have issues with using 'large' engines, especially once in 0G.

I generally can 'fix' this issue by using the 'limit throttle' option, but that can be annoying, as I've noticed several time that I've forgotten I'd left it on (or off).

Expected behavior: Engine throttle based on engine power to achieve correct speed.

Actual behavior: Engine power doesn't seem to be taken into effect, so minor course corrections are often overshot, resulting in a loop of course corrections that don't end.

Perhaps there should be some way to account for/calculate the engine power. If this can't be achieved by reading in-game data, then after a failed course-correction or two, it should 'learn' the engine is high-thrust, and lower power on subsequent burns.

Just noticed: duplicate of #235

I've noticed in this latest build it isn't quite as heavy on the pedal, but still overshoots a little bit.
Nice improvement, but still needs a tad bit of tweaking. I think mechjeb could 'learn' the engines instead of taking what it gets from the game as absolute, if it detects errors in course corrections. (This would also apply to control surfaces, and might make it more 'FAR aware"

I suspect you have a mod that disrupt MJ model, or strange design. With stock engine and only MJ it should never overshoot a node.
Did you try the last dev version ?

Using mod engines, nova punch being the main offenders, but the ones from a
few others do this well. Mainly ones with more than one engine.

This message was sent via phone. Please excuse any typos, as my phone loves
to 'autocorrect' to the wrong words.
On Dec 4, 2013 6:16 PM, "sarbian" [email protected] wrote:

I suspect you have a mod that disrupt MJ model, or strange design. With
stock engine and only MJ it should never overshoot a node.
Did you try the last dev version ?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/236#issuecomment-29856205
.

Actually I should have said more than one "nozzle" on the same engine. For instance the "matriarch" and little mother engines

I'll test them. You did not tell me if you tried the dev build.

Oh, sorry, yes, been using latest from Jenkins server. Sorry about that.

This message was sent via phone. Please excuse any typos, as my phone loves
to 'autocorrect' to the wrong words.
On Dec 9, 2013 7:17 AM, "sarbian" [email protected] wrote:

I'll test them. You did not tell me if you tried the dev build.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/236#issuecomment-30127094
.

I just checked with the little mother and MJ use the correct thrust. I executed a few node and it went ok. Not perfect but my ship was too light for such a powerfull engine.
The problem with multiple nozzle was fixed in dev 115.

Yep, appears fixed. Sorry about the delay :P Close this post up :D

On Mon, Dec 9, 2013 at 1:52 PM, sarbian [email protected] wrote:

I just checked with the little mother and MJ use the correct thrust. I
executed a few node and it went ok. Not perfect but my ship was too light
for such a powerfull engine.
The problem with multiple nozzle was fixed in dev 115.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/236#issuecomment-30160314
.