autopilot problem

[colubridae]

at the moment every startup of DCS I can fly A-10 missions without problem.

but once I've engaged the autopilot, in any mode, in subsequent A-10 missions I cannot engage autopilot.

to enable autopilot again requires a DCS restart.

 

 

(same thing occurs with PAC-1) .

 

 

both commands were bound to my X-56 hotas.

but even starting DCS with 'autopilot' and 'pac-1' as keyboard only

commands I get the same problem.

 

 

 

 

 

 

Not sure if it's my fault or not, please help.

[A10Yoda]

at the moment every startup of DCS I can fly A-10 missions without problem.

but once I've engaged the autopilot, in any mode, in subsequent A-10 missions I cannot engage autopilot.

to enable autopilot again requires a DCS restart.

 

 

(same thing occurs with PAC-1) .

 

 

both commands were bound to my X-56 hotas.

but even starting DCS with 'autopilot' and 'pac-1' as keyboard only

commands I get the same problem.

 

 

 

 

 

 

Not sure if it's my fault or not, please help.

The autopilot system requires 2 separate functions enabled to operate.

 

-SAS System (Left console 4 switches, Yaw and Pitch)

-EGI (Which requires EAC subsystem engaged aft of the throttle guide after full INS alignment and Nav selection CDU)

 

Sent from my SM-N975U using Tapatalk

[Shadow KT]

Upload a track so we can see what you are doing.

 

End your flight, save the track, upload it here

[colubridae]

Ok was attempting to create tracks.

 

 

couldn't succeed, with simple tracks, the autopilot engaged without problems.

 

 

so did what I was doing when problem occurred.

this was air-refuelling.

 

 

after small refuelling I quit the mission and used the 'fly again' option.

sure enough the problem recurred.

this time though I noticed that at the start of the 'subsequent' mission the refuelling gate was open.

 

 

turns out that autopilot would not engage when the refuelling gate was open.

when I closed the gate autopilot worked fine.

 

 

don't know if this is meant to be, but at least for the moment I've cured the problem. I will investigate further. and report back.

 

 

(FYI refuelling gate was controlled via SW5 on my X-56 throttle.)

 

 

 

 

ed looks like this is my problem.

because I've been doing regular A-10 tanking practice at each DCS startup, I've left the refuelling gate open.

DCS 'remembers' this so that any subsequent mission in the A-10 the gate is still open.

when I close the gate autopilot function returns.

Edited March 26, 2020 by colubridae
more data

[Yurgon]

because I've been doing regular A-10 tanking practice at each DCS startup, I've left the refuelling gate open.

DCS 'remembers' this so that any subsequent mission in the A-10 the gate is still open.

 

I just tested in a slightly outdated 2.5.5 Stable and latest OB and cannot confirm this. I opened the refueling receptacle from "Instant Actions" flights as well as from the "Mission" main menu, quit the mission, started the same mission again, and the receptacle was properly closed and the autopilot readily available.

 

I'm also not aware of any issues with the A-10C module where anything carries over from one mission to another.

 

I would try to run a DCS repair and see if the problem persists. This definitely should not happen.

[Puma]

Are you sure the tank open binding isn't just syncing to your hotas on every startup?

 

Its a real “feature” of an A-10 that you cannot engage autopilot with the refuelling door open.

[colubridae]

Are you sure the tank open binding isn't just syncing to your hotas on every startup?

 

Its a real “feature” of an A-10 that you cannot engage autopilot with the refuelling door open.

 

 

That's what it looks like.

 

 

if I remove the button binding to the fuel cap entirely, the problem goes away.

 

 

 

thanks

any ideas to cure the problem, or do i just live with it, as now i know the problem it's not so annoying anymore.

 

:)

Edited March 27, 2020 by colubridae
added thanks

[colubridae]

problem solved.

 

 

it was the key setting in Logitech programmer.

 

 

the key was set to 'fallback' whatever that means instead of 'unprogrammed'

 

 

thanks for advice guys.

 

:)