Jump to content

[ NO BUG - USER ERROR]Autopilot no longer working


Recommended Posts

It is working for me. Bear in mind that the autopilot only activates under certain stability conditions (I don't remember exactly), but basically if your nose is moving, even slightly, the autopilot will not activate. Also double check that A is your binding for autopilot.

Kind regards,

Vince

 

PC:

 

i5-7300HQ@2,5GHz | nVidia GTX 1050 Ti | 8Gb RAM | 256GB SSD for Windows+DCS | Windows10

 

Modules:

 

Mirage2000C | AV-8B N/A | MiG-21Bis | F-5E | L-39 | Gazelle | FC3

Combined Arms | Supercarrier

NTTR | Persian Gulf

Link to post
Share on other sites

Works for me on the latest OB - make sure you're pretty much level trimmed before engaging Alt HOLD.

Also make sure the autopilot (AFC) is on otherwise Alt Hold won't engage.


Edited by Blackeye
Link to post
Share on other sites
Nope, no stick pressure, deadzones set and working. It seems to trim the aircraft but doesn't hold attitude the nose just drifts.

 

The only way i can reproduce this issue is to hold back slightly on my stick, trim the aircraft into level flight whilst still holding back on the stick, and then engaging AFC. This leads me to believe that your deadzones are not significant enough and you should increase them. (To test try setting the deadzones to something abnormally high so you can tell if it works or not.)

Link to post
Share on other sites

Autopilot is working, The AFC switch to the right of the ALT hold has to be engaged before the ALT hold switch will lock.

Win 10 - Intel I7 7700k@4.6ghz water cooled - ASUS Z270 -EVGA GTX 1080 Ti SC2 Hybrid - 1000W PSU - 32GB 3200 G-Skill- Oculus Rift S

custon mip panel and side panels

Bodnar BU0836X, BBI32x2, BBI64x2

DSD 64

TM Warthog HOTAS

TM Cougar MFD'sx3

TM TPR pedals

Saitek Radiox2

Link to post
Share on other sites

I had to increase my deadzone. Its stick dependent.

i9 9900K @ 5.1Ghz - ASUS Maximus Hero XI - 32GB 4266 DDR4 RAM - ASUS RTX 2080Ti - 1 TB NVME - NZXT Kraken 62 Watercooling System - Thrustmaster Warthog Hotas (Virpil Base) - MFG Crosswind Pedals - Pimax 5K+

VFA-25 Fist Of The Fleet

Link to post
Share on other sites

From my experience -- and I use AFC a lot -- you have to hold the aircraft's attitude within the AFC constraints -- which are fairly generous -- and be fairly stable in flight, to activate AFC. Trimming is not necessary at all. In fact, using AFC is the best way I know to get your aircraft perfectly trimming in the shortest amount of time, because AFC sets up your trim for stable flight. Then simply disengage AFC (NOT emergency cancel) and you are perfectly trimmed.

When you hit the wrong button on take-off

[sIGPIC][/sIGPIC]

 

System Specs.

[TABLE]System board ... MSI X99A GAMING 9 ACK

CPU ............ Intel Core i7-5820K @ 3800MHz per OC Genie

CPU cooling .... Noctua NH-D15

Memory ......... 16GB DDR4-3000 G.Skill Ripjaw

PSU ............ Corsair AX860i PSU

Graphics card .. Zotac Nvidia GeForce GTX 1080 Ti Amp! Extreme

System disk .... SanDisk Extreme PRO 480GB SSD

Monitor ........ ASUS MG279Q, 27"

VR ............. Oculus Rift CV1[/TABLE]

Link to post
Share on other sites
From my experience -- and I use AFC a lot -- you have to hold the aircraft's attitude within the AFC constraints -- which are fairly generous -- and be fairly stable in flight, to activate AFC. Trimming is not necessary at all. In fact, using AFC is the best way I know to get your aircraft perfectly trimming in the shortest amount of time, because AFC sets up your trim for stable flight. Then simply disengage AFC (NOT emergency cancel) and you are perfectly trimmed.

 

This is how it's always worked for me in the past, but ever since the last patch it does not. Now even if I am holding completely straight and level as soon as I engage AFC it starts pitching up in a constantly positive rate. I can then pull the stick back slightly and arrest the climb, but that is NOT how it used to work, something is definitely amiss.

Aorus Z370 Ultra Gaming WiFi MB | i7-8700k @ 4.9 GHz | EVGA GTX 1070 Ti | 32 GB CORSAIR Vengeance 3000 MHz DDR4 Ram | Corsair H100 Pro Cooler | RaidMax TX 850M PS | Samsung 970 Evo Plus M.2 NVMe SSD |TM Warthog Hotas w/ F/A-18 Hornet grip | Corsair Gamer 570x Crystal Case | Oculus Rift S

 

DCS | AV8B | F18C | F-16C | A10C | Mig 29 | F15 | SA-342 | Huey | Persian Gulf | NTTR | Combined Arms

Link to post
Share on other sites
This is how it's always worked for me in the past, but ever since the last patch it does not. Now even if I am holding completely straight and level as soon as I engage AFC it starts pitching up in a constantly positive rate. I can then pull the stick back slightly and arrest the climb, but that is NOT how it used to work, something is definitely amiss.

 

So, you engage AFC and the nose starts climbing, and the solution (immediate solution) is to pull on the stick... and then? Is AFC still active? What if you push the stick forwards -- which would be my automatic reaction to an unwanted climb behaviour.

When you hit the wrong button on take-off

[sIGPIC][/sIGPIC]

 

System Specs.

[TABLE]System board ... MSI X99A GAMING 9 ACK

CPU ............ Intel Core i7-5820K @ 3800MHz per OC Genie

CPU cooling .... Noctua NH-D15

Memory ......... 16GB DDR4-3000 G.Skill Ripjaw

PSU ............ Corsair AX860i PSU

Graphics card .. Zotac Nvidia GeForce GTX 1080 Ti Amp! Extreme

System disk .... SanDisk Extreme PRO 480GB SSD

Monitor ........ ASUS MG279Q, 27"

VR ............. Oculus Rift CV1[/TABLE]

Link to post
Share on other sites
So, you engage AFC and the nose starts climbing, and the solution (immediate solution) is to pull on the stick... and then? Is AFC still active? What if you push the stick forwards -- which would be my automatic reaction to an unwanted climb behaviour.

 

Sorry, my bad, I meant push the stick forward to arrest the climb, and yes @Idle Wild you can make slight corrections to flight path in the Harrier with AFC on. Yes AFC is still on, and it will start drifting again.

 

@lukeXIII Not being a jerk, serious question: Why should I need to increase my deadbands when the AFC has worked fine for a year and a half at their current setting? That tells me something has changed.

Aorus Z370 Ultra Gaming WiFi MB | i7-8700k @ 4.9 GHz | EVGA GTX 1070 Ti | 32 GB CORSAIR Vengeance 3000 MHz DDR4 Ram | Corsair H100 Pro Cooler | RaidMax TX 850M PS | Samsung 970 Evo Plus M.2 NVMe SSD |TM Warthog Hotas w/ F/A-18 Hornet grip | Corsair Gamer 570x Crystal Case | Oculus Rift S

 

DCS | AV8B | F18C | F-16C | A10C | Mig 29 | F15 | SA-342 | Huey | Persian Gulf | NTTR | Combined Arms

Link to post
Share on other sites
@lukeXIII Not being a jerk, serious question: Why should I need to increase my deadbands when the AFC has worked fine for a year and a half at their current setting? That tells me something has changed.

 

From the last patch notes: "Added ability for small stick movement to adjust AFC trim"

 

Before this patch with AFC engaged it basically ignored stick input until you added enough stick input to break out of AFC (which hid any neutral stick issues). With the corrected AFC; even though your deadzone may be the same, it is not big enough and as a result is taking this minor "stick input" and constantly adjusts the trim.

Link to post
Share on other sites
From the last patch notes: "Added ability for small stick movement to adjust AFC trim"

 

Before this patch with AFC engaged it basically ignored stick input until you added enough stick input to break out of AFC (which hid any neutral stick issues). With the corrected AFC; even though your deadzone may be the same, it is not big enough and as a result is taking this minor "stick input" and constantly adjusts the trim.

 

 

Ah, I must have missed that, that would explain it thanks!

Aorus Z370 Ultra Gaming WiFi MB | i7-8700k @ 4.9 GHz | EVGA GTX 1070 Ti | 32 GB CORSAIR Vengeance 3000 MHz DDR4 Ram | Corsair H100 Pro Cooler | RaidMax TX 850M PS | Samsung 970 Evo Plus M.2 NVMe SSD |TM Warthog Hotas w/ F/A-18 Hornet grip | Corsair Gamer 570x Crystal Case | Oculus Rift S

 

DCS | AV8B | F18C | F-16C | A10C | Mig 29 | F15 | SA-342 | Huey | Persian Gulf | NTTR | Combined Arms

Link to post
Share on other sites
From the last patch notes: "Added ability for small stick movement to adjust AFC trim"

 

Before this patch with AFC engaged it basically ignored stick input until you added enough stick input to break out of AFC (which hid any neutral stick issues). With the corrected AFC; even though your deadzone may be the same, it is not big enough and as a result is taking this minor "stick input" and constantly adjusts the trim.

 

 

Thanks Luke, this seems to explain the behaviour for me too as to why the nose was drifting. I increased my deadzones by 3x from 3 to 10 and the autopilot works as expected.

 

 

Apparently this was brought about through this observation:

https://forums.eagle.ru/showthread.php?t=275178

 

 

And they fixed it in response, but omitted the behaviour change from the DCS release notes:

https://forums.eagle.ru/showthread.php?t=279106

Link to post
Share on other sites

I used AFC extensively before the latest update, and I recently tried it out again since the update.

 

1. Adjusting the flight attitude through the trim-hat is now far quicker that it used to be. In some cases you can use the trim-hat to put the airframe into such a position that is actually jumps out of AFC.

 

2. It used to be that if you activated AFC that the aircraft would be trimmed perfectly. And attitude variance was controlled as if the stick were holding the attitude. If at any time your turned AFC off, the aircraft remained in its current attitude -- including the prefect trimm -- and you could easily simply start controlling the aircraft through stick and pedals without issue yourself.

 

3. Now when trying to change the attitude through stick input, the aircraft seems to try to ignore input, changing only very minimally. If you use larger stick input, you break out of AFC.

 

4. If you do break out of AFC while the aircraft is holding a fairly a high rate of turn, you discover that the turn was not caused by AFC manipulating the stick, but by manipulating trim. If you put the stick in its neutral center position you will veer sharply in the direction you were turning in AFC and the noxe will pull up sharply, until you neutralize trim.

 

5. You used to be able to start ATH during AFC as long as you didn't have more than about 5° climb or dive (in reallity it should be restricted by the actual feet/minutes climb or dive rate, but I don#t recall what the numbers are.

 

Now, even while being fairly close to 0° nose up or down, ATH will not catch, especially if you had been in AFC/ATH and ATH broke out, bc you pulled the nose up or pushed it down.

 

For me the worst things are, in this order:

 

- Trim used to fly the aircraft and not the stick (aircraft not trimmed when ARC switched off with AFC switch).

- Reaction to stick inputs too slow.

- ATH won't catch if the aircraft previously broke out of it.

When you hit the wrong button on take-off

[sIGPIC][/sIGPIC]

 

System Specs.

[TABLE]System board ... MSI X99A GAMING 9 ACK

CPU ............ Intel Core i7-5820K @ 3800MHz per OC Genie

CPU cooling .... Noctua NH-D15

Memory ......... 16GB DDR4-3000 G.Skill Ripjaw

PSU ............ Corsair AX860i PSU

Graphics card .. Zotac Nvidia GeForce GTX 1080 Ti Amp! Extreme

System disk .... SanDisk Extreme PRO 480GB SSD

Monitor ........ ASUS MG279Q, 27"

VR ............. Oculus Rift CV1[/TABLE]

Link to post
Share on other sites
  • 2 weeks later...

I just encountered this issue.

Even if there is no input of the stick, altitude hold will just turn back off immediately. I have tried increasing deadzone to unreasonable amount, it didn't work.

But if I pull a little bit of the stick with no deadzone, altitude hold is engaged until I take my hands off the stick.

Well, harrier have to stay at hanger again until this bug get fixed.

Link to post
Share on other sites

Im sure no any problem here, it works and alt holding works too very well (tested open beta).

Use proper settings of plane for this and stick position (in settings of DCS too, sometimes a larger death zone helps on joystick Axis).


Edited by YoYo

Webmaster of http://www.yoyosims.pl

Yoyosimsbanner.gif

Win 10 64, i9 9900k, RTX  3090 24Gb OC, RAM 32Gb Corsair Vengeance LED OC@3200MHz,, 3xSSD+2xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: HP Reverb G2

Link to post
Share on other sites
I just encountered this issue.

Even if there is no input of the stick, altitude hold will just turn back off immediately. I have tried increasing deadzone to unreasonable amount, it didn't work.

But if I pull a little bit of the stick with no deadzone, altitude hold is engaged until I take my hands off the stick.

Well, harrier have to stay at hanger again until this bug get fixed.

 

I cant say there is a bug, I cant replicate it, The autopilot system is working fine for me, tried on numerous occasions under differing scenarios, no problem.

 

Open Beta 2.5.6.50979

Intel® i9 9900K Coffee Lake OC 5.1GHz, ASUS ROG Maximum Formula LGA1151 MB, Windows 10® 64bit Pro, 64GB 3200MHz DDR4 RAM, EVGA Black Edition 2080Ti OC GPU, 2 x Samsung Evo 970 NVMe 1TB Drives, 1 x Samsung Evo 860 2TB SSD, 1 x Seagate 2TB HDD, 1 x Acer™ Predator 35" 4K Wide Flat Monitor, TM Warthog HOTAS, MFG Crosswind pedals, Oculus Rift S

Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...