When it does gravity turns whatsoever it "overwrites" SAS and shows the circular arrows at the SAS button this also make it roll over and over and over, its not a problem with my craft as when i turn to target manualy with SAS on it doesnt roll so pls fix it!

I can't fix until you explain what's not working with proper sentence.

I think he's saying that when he enables a mechjeb autopilot module, the default SAS is staying enabled. So I'd imagine that the in-game SAS and mechjeb are fighting for control of the ship.

MechJeb should be completely disabling the default SAS, as Mechjeb has its own SAS built-in.

It already does that. Unless you use the "Use Stock SAS" option, and that option makes the SAS mandatory since MJ use it instead of its builtin attitude controller. And using that option is not a good idea when you are out of the atmosphere.

can I mention this URL again ?
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html oh I just did.... :D

On 11 December 2013 12:53, sarbian [email protected] wrote:

It already does that. Unless you use the "Use Stock SAS" option, and that
option makes the SAS mandatory since MJ use it instead of its builtin
attitude controller. And using that option is not a good idea when you are
out of the atmosphere.

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

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.

Possibly related to this, I have in fact noticed that mech-jeb has a tendency to yaw and pitch when it only needs to roll, and in general does not change it's attitude in an efficient manner, though I think there's already a post about that somewhere. Maybe the OP is referring to this effect, and is experiencing it when mech-jeb transitions from vertical assent to gravity turn, maybe amplified by a large sudden change to the commanded pitch and yaw.

The OP mention SAS and as I said earlier the SAS is deactivated whenever MJ need to turn, unless the "use stock SAS" option is active.
The current dev version of MJ has some patch that lower the unneeded yaw/pitch/roll, feedback is welcome in the forum thread.

As for the OP post, I stand by my position. I can't fix anything if the bug is not explained properly.

I agree. If there is no effort given to trying to be descriptive about the problem, there is little that can be done to help. Though, on the other hand, there was no reason to be as aggressive and dismissive as you came across as initially, although you may not have intended it as such.

hey thats really not fair!

how rude and dismissive is a bug report that basically says something vague
is wrong fix it..?

if someone is using a developers time for free (ie a mechjeb user) and
want's to help by reporting a bug, the least ANY developer of open source
software should expect is to not have their time wasted and that bugs are
reported in a coherent and useful manner, while English might not be a
reporters first language I have seen good and useful bug reports in
terrible English...

to reiterate If someone expects to use software for free they should at
least respect the developers valuable time enough not to waste it, in the
past developers have been encouraged to just give up by exactly this kind
of thing...

On 12 December 2013 00:11, Aquilux [email protected] wrote:

I agree. If there is no effort given to trying to be descriptive about the
problem, there is little that can be done to help. Though, on the other
hand, there was no reason to be as aggressive and dismissive as you came
across as initially, although you may not have intended it as such.

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

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.

Agreed. Since this issue was never re reported with more descriptive update, can someone close it? I try to keep tabs on open issues to help bug test, and I'm sure devs wouldn't mind less clutter.
Imagine if he needs to reopen the issue, someone will report it with better written explanation.