Rendezvous autopilot fails to match planes

[BIGMOS]

Hi mechjeb fubars at at maching planes when using rendezvous autopilot every time. I am using 0.20.2.186 of ksp. It say 68 years, also it flys past manever node and Never matches palnes

[chriscamacho]

I've seen this figure of 68 years when doing orbital manoeuvres round the
Mun, but wasn't able to reproduce it reliably.

On 1 June 2013 15:22, BIGMOS notifications@github.com wrote:

Hi mechjeb fubars at at maching planes when using rendezvous autopilot
every time. I am using 0.20.2.186 of ksp. It say 68 years, also it flys
past manever node and Never matches palnes

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/121
.

Disclaimer:
By sending an email to ANY of my addresses you are agreeing that:

1. I am by definition, "the intended recipient"
2. All information in the email is mine to do with as I see fit and
   make such financial profit, political mileage, or good joke as it
   lends itself to. In particular, I may quote it where I please.
3. I may take the contents as representing the views of your company.
4. This overrides any disclaimer or statement of confidentiality
   that may be included on your message.

[Anatid]

Could I ask you to try the latest dev build at http://jenkins.mumech.com/job/MechJeb2/ and see if it fixes your issue? It contains a fix for a similar problem in the rendezvous autopilot. To install the dev build, just download MechJeb2.dll from that link and use it to replace GameData/MechJeb2/Plugins/MechJeb2.dll.

[chriscamacho]

I can't replicate reliable the 68 year issue but I was using the dev build from 2013/5/28

[BIGMOS]

No it still forever chases the node. When it gets to end of burn it goes crazy +4min trys to burn again.

[Anatid]

OK, could you upload your craft file to http://pastebin.com/ or some similar site so we could fly your craft and see what's going wrong for ourselves?

[BIGMOS]

Yes i uploaded 2 . I think i did it correctly, If not i can e-mail you directly. I am bigmos on pastbin.com

[Travatan]

I am experiencing the issue as well. Everything goes well untill Hohman transfer is completed. This has happened on multiple ships (One station and one mun lander). Once it hits the 68 year bug I have to disable the auto pilot and manually get myself close to the Target. Once I am close enough I can use Mechjeb to do the auto docking. Now the weird thing was I got this to work flawlessly the first time I used it. Also the game has a much more noticeable amount of lag once the 68 year bug hits. It persists through restarts of KSP as well.

[chriscamacho]

I noticed it twice when the orbital inclination was very close (not saying
it was the inclination could have been coincidence - still struggling to
pin down exactly how to replicate it 100% of the time...), a few seconds
thrust in a random direction and in both cases I was able to use the
autopilot again

On 2 June 2013 16:42, Travatan notifications@github.com wrote:

I am experiencing the issue as well. Everything goes well untill Hohman
transfer is completed. This has happened on multiple ships (One station and
one mun lander). Once it hits the 68 year bug I have to disable the auto
pilot and manually get myself close to the Target. Once I am close enough I
can use Mechjeb to do the auto docking. Now the weird thing was I got this
to work flawlessly the first time I used it. Also the game has a much more
noticeable amount of lag once the 68 year bug hits. It persists through
restarts of KSP as well.

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

Disclaimer:
By sending an email to ANY of my addresses you are agreeing that:

1. I am by definition, "the intended recipient"
2. All information in the email is mine to do with as I see fit and
   make such financial profit, political mileage, or good joke as it
   lends itself to. In particular, I may quote it where I please.
3. I may take the contents as representing the views of your company.
4. This overrides any disclaimer or statement of confidentiality
   that may be included on your message.

[Travatan]

Hmm...Ill try it again with the same ships and do different Inclinations and see what happens.

[BIGMOS]

It allways does it for me mun kerbin dont matter. I have only seen the 68 year thing twic, but the forever chasing node thing is allways happening ,,,

[Travatan]

Ok..bug still persists. I created a new ship. Changed the inclination to 3 degrees and targeted an object that was at 0 degrees. My launch was timed with the orbiting station and they were already pretty close, it instantly it the 68year bug and lagged so hard I had to force quit.

[BIGMOS]

It also seem sas dosnt work properly just tried it again' 0.3m/s burn node gets shaky...
I also noticed that i you use the new pods that are in ksp stock, mech jeb will send you out of orbit when trying to land on mun

[Travatan]

Ok. Did a fresh clean install of KSP and only used Mechjeb addon, using the latest dev build. It worked. Didnt get the 68 year bug at all. Not sure if its related to conflicting addons? Im gonna try multiple ships and see what happens.

[BIGMOS]

I did the same, but all im only using parts, and still chasing node. I have not seen the 68same year bug

[BIGMOS]

Issue not solved i closed by mistake i am on phone

[Travatan]

What Mods were you using Bigmos when you saw it?

[chriscamacho]

the only addon I have is mechjeb, I'm still failing to reproduce what for
me is an intermittent issue, odd is behaving so differently for different
people!

On 3 June 2013 05:39, Travatan notifications@github.com wrote:

What Mods were you using Bigmos when you saw it?

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

Disclaimer:
By sending an email to ANY of my addresses you are agreeing that:

1. I am by definition, "the intended recipient"
2. All information in the email is mine to do with as I see fit and
   make such financial profit, political mileage, or good joke as it
   lends itself to. In particular, I may quote it where I please.
3. I may take the contents as representing the views of your company.
4. This overrides any disclaimer or statement of confidentiality
   that may be included on your message.

[BIGMOS]

All im using is mechjeb, isa map, and for parts I am using dsm, kas, home,and Iep hybrid ion pack, and kosmos
Thats it. Even after fresh ksp install with dev dll for mechjeb, it chases node, i havent seen 68 year bug, just chases node

[BIGMOS]

I am going to try make a video of what i am seeing. Ill post link here.

Any luck on my craft files? I put on pastbin.com

[BIGMOS]

https://docs.google.com/file/d/0BxUqMzMdb-piQW55a0t2NFYzX0E/edit?usp=sharing

here ya go just uploaded it might take a few before its ready its in mp4 format might have to download it
let me know

[Anatid]

Thanks for the video, @BIGMOS. I haven't seen that behavior before. It looks like MJ is burning gently towards the node, but the dV meter refuses to decrease? I'll try to replicate it here.

Edit: @BIGMOS, when this happens, if you switch to the main view can you see the engine still burning, or is the engine perhaps turning off?

[BIGMOS]

Think its still buring hard to tell.

[chriscamacho]

I've seen similar issues with PID controllers, just not quite ever reaching
target - you might want to experiment with a slightly larger epsilon
value... (or better yet the parameters of the actual PID controller)

On 4 June 2013 16:50, BIGMOS notifications@github.com wrote:

Think its still buring hard to tell.

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

Disclaimer:
By sending an email to ANY of my addresses you are agreeing that:

1. I am by definition, "the intended recipient"
2. All information in the email is mine to do with as I see fit and
   make such financial profit, political mileage, or good joke as it
   lends itself to. In particular, I may quote it where I please.
3. I may take the contents as representing the views of your company.
4. This overrides any disclaimer or statement of confidentiality
   that may be included on your message.

[Tallinu]

It looks to me like part of the issue here is that the ship's wobbling is adding to the ship's velocity, which is a KSP problem. You can see the dV required rising back up to as much as 3 m/s at several points in the video, just from the ship turning toward the jittery node. As a workaround, you may want to try simply increasing the threshold where it considers a maneuver "complete" to around 0.5 m/s instead of the smaller default.

[BIGMOS]

I am also getting it with stock parts. I might try going to 2.0.7 mechjeb. Do you have a download link ? I was able to get it ti work before you guys made the new one for the new ksp file system

[ZeWaka]

Is there any progress on resolving this issue?

[copester]

Issues #121, #131, #133, and #138 are duplicates and not technical bugs but due to lack of communication in the docs. See my comment #131 (comment)

tl;dr: The probe parts lack the rotational power of the manned command modules. As a result, you need to turn on RCS so MechJeb can adjust your attitude for the burns.

[chriscamacho]

probes seem to work ok for me with an ASAS, or am I misunderstanding the
issue?

On 24 July 2013 20:39, Chris Cope notifications@github.com wrote:

Issues #121 #121, #131#131,
#133 #133, and #138https://github.com/MuMech/MechJeb2/issues/138are duplicates and not technical bugs but due to lack of communication in
the docs. See my comment #131#131 (comment)

tl;dr: The probe parts lack the rotational power of the manned command
modules. As a result, you need to turn on RCS so MechJeb can adjust your
attitude for the burns.

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

Disclaimer:
By sending an email to ANY of my addresses you are agreeing that:

1. I am by definition, "the intended recipient"
2. All information in the email is mine to do with as I see fit and
   make such financial profit, political mileage, or good joke as it
   lends itself to. In particular, I may quote it where I please.
3. I may take the contents as representing the views of your company.
4. This overrides any disclaimer or statement of confidentiality
   that may be included on your message.

[lamont-granquist]

Closing this as an old MechJeb issue. Many MechJeb issues have had little interest in years, have been fixed for years, do not include adequate replication steps, refer to old problems which are no longer applicable, or are difficult to determine what the problem is. This issue is being closed for one of those reasons. We apologize for any inconvenience, but keeping the TODO list tidy helps the developers.

If this bug/issue is still a problem, please open a new issue. For bugs please try to include a Minimal, Complete, Verifiable Example that explains all the steps required to replicate the issue. A link to the KSP.log file should be ideally included, but is often not sufficient information. Screenshots or short videos are often the best way to show a bug.