Autopilot

[Vino]

I can't use autopilot. I have to press the buttons ten times and still don't get the autopilot always on. Which parameters should I fill in to get the autopilot on?

 

(Google translator :megalol:)

Edited April 27, 2019 by Vino

[LeCuvier]

I understand that the autopilot only engages if there is no control signal from the roll and pitch axes. If you have not added deadband to these axes your stick might generate control signals even without you touching it. I use a 2% deadband on my pitch axis and that fixed the problem for me.

[Eaglewings]

I can't use autopilot. I have to press the buttons ten times and still don't get the autopilot on. Which parameters should I fill in to get the autopilot on?

 

 

 

(Google translator :megalol:)

That is weird. Autopilot functionality in the Hornet is working well here. Altitude, Heading and Balt parameters are all working.

 

When you press AP(autopilot), Altitude, Heading and Balt are displayed. Click on the button the left of these parameters to select desired autopilot working.

 

Yes as mention in 2 post, set some deadzone for pitch and roll axes.

Edited April 27, 2019 by Eaglewings

[Habu_69]

Be sure A/P Disengage switch is not accidentally on.

[Cytarabine]

Also the autopilot is multiple different things;

 

BAR - hold barometric altitude

RAD - hold radar altitude

CRS - hold selected course (which you select with the course select lever just above the bottom MFD)

ATT - hold current attitude

 

There is no 'follow waypoints' autopilot or anything like that. Might also be worth setting a small deadzone for your axes on your stick, as it might be just enough to stop the autopilot engaging.

[Nanne118]

Also the autopilot is multiple different things;

 

BAR - hold barometric altitude

RAD - hold radar altitude

CRS - hold selected course (which you select with the course select lever just above the bottom MFD)

ATT - hold current attitude

 

There is no 'follow waypoints' autopilot or anything like that. Might also be worth setting a small deadzone for your axes on your stick, as it might be just enough to stop the autopilot engaging.

 

AFAIK the F-18 is also capable of a 5th autopilot mode, CPL ('coupled') which does do automatic waypoint following. I not entirely sure if this will be implemented (might be a later block than the one in DCS), but it might not be implemented yet as it has some advanced functionality as automatically determining the most fuel efficient or fastest route

[sideshow]

For me to get altitude hold to work I have to nudge the stick forward after engaging the autopilot. Otherwise it will not work. All other modes work like they should.

[fitness88]

Put dead bands on your stick around 3. It may help.

[i see it has already been mentioned]

[dorianR666]

its very problematic when playing on keyboard. if so, show your input axes with rctrl-enter and fiddle vertically around the zero position and keep trying to engage the autopilot.

 

 

its a bit ridiculous because you really need to hit precisely the zero value with quick keyboard presses :) no deadzone there

[rob10]

It would be nice if the parameters were a little looser for AP engagement on the Hornet. Never had a problem in the A10, but you really have to be dead on or AP won't take in the Hornet.

[LeCuvier]

Yes, with the A-10C you can have a positive or negative pitch of a few degrees, and the AP will pull you to level flight. In the F/A-18C sim, your pitch needs to be exactly zero (or very close to zero), which often requires a bit of fiddling.

As many simmers have joysticks that are less than ideal, ED should add a bit of tolerance there, even if that's not "realistic".

Personally, I use a TM WH grip in a T-50 base, and since the grip is very heavy the stick produces a nose-down signal of about 2% when I don't hold it. I had to set a 2% deadband on the pitch axis to enable the altitude AP modes.

[whaaw]

Yes, with the A-10C you can have a positive or negative pitch of a few degrees, and the AP will pull you to level flight. In the F/A-18C sim, your pitch needs to be exactly zero (or very close to zero), which often requires a bit of fiddling.

As many simmers have joysticks that are less than ideal, ED should add a bit of tolerance there, even if that's not "realistic".

Personally, I use a TM WH grip in a T-50 base, and since the grip is very heavy the stick produces a nose-down signal of about 2% when I don't hold it. I had to set a 2% deadband on the pitch axis to enable the altitude AP modes.

 

f18 AP doesn't care about your current pitch (otherwise ATTHOLD wouldn't work), it cares about the input you give. if he is not able to activate it I can think of 3 problems already mentioned here.

 

1. no dead zones on input devices

2 AP disengage button somehow activated.

3. Jitter in any Axis that surpasses the dead zone. (rudder perhaps?)

(4.INS not NAV)?

 

Also i can activate BALT with 3-4° Up and he still pulls me down.

maybe even more than that

 

my deadzone's on all axis are at least 5

Edited April 29, 2019 by whaaw

[marcj]

Easiest way to diagnose unwanted control inputs (IMO) is in the Windows Game Controllers "Test" Control Panel, which displays all your axis and button states. You can tell very quickly for instance whether you have an axis that is jittering, or a button stuck in an "on" position etc.