Autopilot ATT engagement only with 2nd press

Hi folks,

this is a long term story.

I have this issue since a very long time (I think it was right from the beginning on the module release), and unfortunately it wasn't fixed by any patch so far.

I fly in VR and also without, and use the keyboard massively with my left hand.

Engaging the ATT mode with my keyboard (using key "a"), needs a 2nd press to really engage it. It doesn't need a second press to disengage it once it was engaged.

I wasn't able to find a suitable thread here.

Kind regards,

TOViper

I mapped this to my hotas in the DCS control settings and it only takes me one press. Are you sure you're giving no stick input when you press it? Sometimes I'll jump the gun on the button press and it won't engage because I am giving too much stick input at the same time. ATT won't engage if the pilot is currently exceeding the mode's authority (which I believe is 20%).

I mapped this to my hotas in the DCS control settings and it only takes me one press. Are you sure you're giving no stick input when you press it? Sometimes I'll jump the gun on the button press and it won't engage because I am giving too much stick input at the same time. ATT won't engage if the pilot is currently exceeding the mode's authority (which I believe is 20%).

fu.., I didn't recognize and even thought about the 20 percent margin ... which can be found ... where?

For sure I'll give it a try very soon & report back.

Thanks for your comment!

After updating to today's version, I am still having it from time to time, but I wasn't able to figure out what causes it. Most times it works, but it seems that after not using it for a longer period of time during flying it then doesn't engage at first press.

Doing more testing ...

After flying a lot this and the last week, I managed to reproduce this problem very often.

Despite I was not able to nail it to one specific event, I can now say that if the autopilot (attitude or altitude) is not used for a while (maybe its just a few minutes), only the second press activates it.

I can reproduce it easily if HB is interested.

Hey TOViper, thanks for reporting. I've had the same issue for years but I wasn't really aware of this.

I've just tested ATT activation/deacivation in all ways possible using only mouse clicks, and I managed to isolate the issue. You don't even need to wait a certain amount of time. It's only a matter of autopilot modes sequencing. Here's what I found (current stable version 2.5.5.33184).

SPAK (on) > SPAK (off) > SPAK (on) > SPAK (off) : OK

ATT (on) > ATT (off) > ATT (on) > ATT (off) : OK

SPAK > ATT > SPAK > ATT : OK

HOJD > SPAK > HOJD > SPAK : OK

HOJD > ATT > HOJD > ATT : OK

HOJD > SPAK > ATT > HOJD > SPAK > ATT : OK

Now occurs the issue (100% reproductible):

SPAK > HOJD > ATT > ATT (here goes nothing!) > ATT (and now it works)

Basically, when you disengage HOJD mode, you have to use the HOJD button, not the ATT button. If you use the ATT button, re-engaging requires two presses.

OK, but is that a feature or a bug?

OK, but is that a feature or a bug?

I'm guessing it's a bug, but if they want to fix some more serious issues first (being able to repair the jet ever, that rocket salvo thing from the other thread) I'm fine with this one being low on the priority list. :)

I'm guessing it's a bug, but if they want to fix some more serious issues first (being able to repair the jet ever, that rocket salvo thing from the other thread) I'm fine with this one being low on the priority list. :)

Hm, some say if it is moved to the "low priority list", it takes 2+ years of beeing implemented. :music_whistling:

Sorry.

I am a damn customer.

I only payed some money, nothing else.

I will shut up.

Thanks for reporting and investigating the issue!

Thanks for reporting and investigating the issue!

RagnarDa, when will the time come where you have a "full" dev-team with you to finish up the Viggen? Hm ... weather is now getting worse with every single day, nights are getting longer ... so is the out-of-early-access-move our next christmas present? Because if so: I would love to take it :)

Thanks for your work already done on our beloved beast!

As far as I've experienced this, it's to do with having "forced" the autopilot to disengage. So if you have autopilot on and you pull some hard manuveures and it turns off, then I have to double press the autopilot light/button/switch to get it to re-engage. I always thought that was just the way it was, but maybe it is a bug.

As far as I've experienced this, it's to do with having "forced" the autopilot to disengage.

I never did this during normal flying.

I think the logical rules of the autopilot selection modes and buttons may have to be reviewed by HB.

I'm still having the cold start issue described previously in the thread https://forums.eagle.ru/showthread.php?t=224126. When starting from cold the autopilot is disengaged when changing mode twice, e.g. going from initial SPAK mode to ATT and then back to SPAK (or to HOJD). I basically have to disengage and engage the autopilot from cold start for it to operate as normal.

I'm guessing it's a bug, but if they want to fix some more serious issues first (being able to repair the jet ever, that rocket salvo thing from the other thread) I'm fine with this one being low on the priority list. :)

I think its a bug, which is still present in OB 2.5.6.52437 :(

Thanks for reporting and investigating the issue!

RagnarDa, what was the result of your investigation?

Is it a bug or a feature? ;)

I just discovered this bug report and I'm a bit annoyed, that I have missed it when it was first reported, because I'm very much aware of this bug and what causes it for many years. I'm actually so much aware of it, that it became part of my routine to always make sure to disengage HÖJD mode by using the keybind for HÖJD again instead of ATT. I got so used to it, that I totally "forgot" that it's actually a bug and should be reported...

So in short: I can very much confirm this bug and that it happens if you cancel HÖJD mode by pressing ATT as Flappie described!

The autopilot activation/deactivation logic seems to be wrong in general, which has been reported in this thread. This might be a reason for the bug reported here.