Changing the gyrocompass (Direction indicator/HSI) with gyro drift knob on aircraft like C172 makes no difference to autopilot as it continues to fly on its own imaginary unchanged (magnentic) compass.
For example, autopilot heading mode on, set heading bug to 100° on DI, turn gyro drift knob 20° to the right so the current aircraft heading is 080° on DI, plane will continue flying on current 080° with heading bug on 100°. Every subsequent heading change will have deviation of 20° (for example turning heading bug to 120° will make plane follow 100° heading).
What should happen: using gyro drift should make autopilot aware of the change and follow new gyrocompass setup.
1.15.7.0 Steam version
The KAP140 gets its heading information from the Heading Indicator Gyro, so if that has drifted, the AP “SHOULD” be getting that incorrect information.
As it is at the moment, it is as if the AP is getting its heading from a different heading system,( KG102A) that has automatic gyro drift. correction (KMT 112 Flux Detector ) ?
The Asobo c172 is clearly fitted with the KI 204 + Directional Gyro.
It is acting as it is fitted with the KI 525A “Indicator” which uses a slaved DG, auto corrected with the Flux Detector ?
Will be interesting to see what happens with Zendesk #102881
Have they given any response yet ?
You seem more knowledgeable about the equipment, I’ll add in that the very same issue exists in JustFlight’s PA28, as far as I’ve seen, which has more primitive autopilot and gyro/optional KI 525A.
I haven’t yet heard anything from them aside from automatic confirmation mail, will update when they respond.
Maybe a little more knowledge after some research, triggered by your revealing observation.
It may be similar to the AP’s altitude issue, where it takes its reference from the Transponder’s FIXED Baro Sensor, instead of the Adjustable one in the AP.
If you just press B, then all Baros are set, and it works, ( because B also sets the Transponder bar – and it SHOULD NOT – but it does) .
If you manually only adjust the Baro in the AP, it makes no difference to the AP, – but you see the Altitude indication in the Transponder change !! —
The whole AP code is a Pandora’s Box !!! lol What a GAME !!!
They have not fobbed you off with some totally irrelevant stock response
They have put the bug into the Asobo internal Bug system
Now, as “far as ZenDesk”: is concerned, they they done their job, and the "SUBMITTING of the BUG, and entering onto the Bug Database s Completed, so they report the Submission process as being “CLOSED”.
Its now up to ASOBO to prioritize this particular bug, and deal with it.
CLOSED from ZENDESK does not mean that the bug is FIXED, it only means that as far as the Bug Submission process is concerned, it is “Closed” and needs no further action from Zendesk or from You.
“Closed” is a misleading term, unless its definition in this case has been defined (as above)
I did look around a bit later and learnt what you said here. I guess biggest confusion was the fact that it isn’t marked as “closed”, but rather “solved”, which should say after update with fix was published . Regardless, I’m happy we did all we could. Hopefully it gets fixed soon as my favorite kind of flying is GPS-less one
Hi, I just checked after not paying attention to this issue for a while. Yes, the autopilot now works correctly and will follow whatever heading on heading indicator regardless if it’s corrected for gyro drift. Also, yes, the hdg_ref_var is set to 1, I assume it got fixed in some update throughout the time.
. Regardless, I’m happy we did all we could. Hopefully it gets fixed soon as my favorite kind of flying is GPS-less one 
