How do I use autopilot?

[Ragnar65]

Guys,

i´m missing the CPL-mode of the autopilot...Is it missing due to EA and will be added later? Or are we bound to live without it?

 

 

RGDS

 

Ragnar65

[Mule]

Guys,

i´m missing the CPL-mode of the autopilot...Is it missing due to EA and will be added later? Or are we bound to live without it?

 

 

RGDS

 

Ragnar65

 

Early EA. Let go of your despair. Bound to live with it..............free!

[Wags]

Will come later in Open Beta.

[==Wiggy==]

Speaking of Auto Pilot - - Mine will not engage at all. No modes.

 

 

Here's what happens:

 

 

On the UFC:

 

 

AP>ON/OFF Button>Select Mode = Aircraft just stays in whatever Attitude it's in momentarily, but gradually will decend and back to whichever side it rolled into most. The control surfaces become locked up. I can override with large stick input or via paddle switch disengage. I get the ":" next to the mode I'm selecting, but the mode does not operate. Period. I can operate the UFC functionality correctly, but he AP simply doesn't do what it should in any mode. What happens is the flight controls lock up in position. When I disengage the AP, the Flight controls come back without issue, but I only get he master caution about 10% of the time with tone alerting me to the disconnect.

 

 

 

I've also tried doing: AP>Mode select>ON/OFF. No combination works. All the symbology appears correctly though. I'm pretty sure it's user error somewhere, but I can't put my finger on it.

 

 

 

 

Any ideas?

Edited June 9, 2018 by 000rick000

[TonyG]

.

[Jetguy06]

Speaking of Auto Pilot - - Mine will not engage at all. No modes.

 

 

Here's what happens:

 

 

On the UFC:

 

 

AP>ON/OFF Button>Select Mode = Aircraft just stays in whatever Attitude it's in momentarily, but gradually will decend and back to whichever side it rolled into most. The control surfaces become locked up. I can override with large stick input or via paddle switch disengage. I get the ":" next to the mode I'm selecting, but the mode does not operate. Period. I can operate the UFC functionality correctly, but he AP simply doesn't do what it should in any mode. What happens is the flight controls lock up in position. When I disengage the AP, the Flight controls come back without issue, but I only get he master caution about 10% of the time with tone alerting me to the disconnect.

 

 

 

I've also tried doing: AP>Mode select>ON/OFF. No combination works. All the symbology appears correctly though. I'm pretty sure it's user error somewhere, but I can't put my finger on it.

 

 

 

 

Any ideas?

 

 

I've been having a similar problem. I can get BALT to work, but not HSEL. Post a track. It's the most helpful.

[fitness88]

My understanding is the on/off is not for the A/P.

You must have no pressure on the stick, put a 1or 2 degree dead band.

 

 

ATT Balt Ralt HSEL all work well.

[bradleyjs]

Assign a Dead-Zone as it might help this issue.

 

“If you don’t set a deadzone, you run into the risk of not being able to engage your autopilot since your stick will always be detected as “not completely centered” even if the position offset is negligible.”

 

Chuck’s FA-18C Hornet Guide - page 6

[==Wiggy==]

Ok -- I will try this. Interesting if so many people are having this issue that it's in the guide, perhaps the best solution would be to give the AP engagement as little more tolerance? Just a siggestion ED...that would improve both AP reports and stop people from complaining that their stick is less sensitive.

[Call_Sign]

Speaking of Auto Pilot - - Mine will not engage at all. No modes.

 

 

Here's what happens:

 

 

On the UFC:

 

 

AP>ON/OFF Button>Select Mode = Aircraft just stays in whatever Attitude it's in momentarily, but gradually will decend and back to whichever side it rolled into most. The control surfaces become locked up. I can override with large stick input or via paddle switch disengage. I get the ":" next to the mode I'm selecting, but the mode does not operate. Period. I can operate the UFC functionality correctly, but he AP simply doesn't do what it should in any mode. What happens is the flight controls lock up in position. When I disengage the AP, the Flight controls come back without issue, but I only get he master caution about 10% of the time with tone alerting me to the disconnect.

 

 

 

 

 

I've also tried doing: AP>Mode select>ON/OFF. No combination works. All the symbology appears correctly though. I'm pretty sure it's user error somewhere, but I can't put my finger on it.

 

 

 

 

Any ideas?

 

My AP wont engage at all :(

[==Wiggy==]

Tried adding dead zone. NO JOY. AP doesn't work at all.

[==Wiggy==]

Ok--- Disregard, 5 is the magic number! AP now works as it should! Thank you guys for all the help!

[Nereid]

Is it planed to remove this behavior? I would call a necessary dead zone just to activate an autopilot a bug.

 

And a dead zone for the stick is a no go in my oppinion.

[Foss]

I set no deadzone, my Stick seems to be centered correctly.

 

So i think it`s not necessary, but can help Input Devices, which do inputs even in centered position. Might be helpful for flying without A/P too.

[Nealius]

I can get AP to engage, but I can't get it to fully disengage. Even if I disengage the AP, I still get an AUTOPILOT caution in the left DDI.

[Growling Sidewinder]

My AP wont engage at all :(

 

make sure game flight mode is unchecked in the options menu,

[Irishlad200000]

Firstly Chucks Guide is hard to beat! If you bought the module prior to the last updates it may pay to delete via module manager and start fresh. That’s helped quite a few with bugs etc!

[==Wiggy==]

Firstly Chucks Guide is hard to beat! If you bought the module prior to the last updates it may pay to delete via module manager and start fresh. That’s helped quite a few with bugs etc!

 

 

yes, I did this as well. Good idea.

[cabzi]

Don't dampen your joystick's center play with an unnecessary deadzone. After you have pressed the baro alt mode, trim your nose down a quick tap or two and the AP will active.

 

Anyway, it is clearly a bug and most likely will be addressed eventually.