You guys are way over thinking this. When you press the heading select button on aircraft that have heading sync the heading bug will center up at the current heading on the directional gyro, period.
In the sim trying to program a key or button ‘set heading bug’ in the manager causes the heading bug to go to ‘N’ or 360 instead of the current ‘straight up’ current heading displayed on the heading indicator.
It is a bug and always has been. It is very annoying that they won’t fix this. The third party systems with ‘heading sync’ by pushing the heading select knob all seem to work fine, regardless of the autopilot system.
The wind, the drift, etc. are issues but have NOTHING to do with heading sync.
I am a retired 23,000 hour plus pilot and always used heading sync to center up on current heading when tracking a couse in NAV/LNAV modes. One push of the heading select button kept me on course when switching navs, gps or vor failure, or whatever. ASEBO obviously doesn’t have many experienced pilots on staff that know heading sync working incorrectly (going to north) is worse than no heading synce at all. HeadindH
3 Likes
You are kind of late to this party.
- You are correct in your first sentence regarding what pressing the heading select button does, and I always understood that the bug should centre on the current heading. The problem was that the sim was gradually adding gyro drift even if that feature was turned off in the assistance settings. The fact is that the G1000 does not even have a gyro:
Source: Max Trescott’s G1000 and Perspective Glass Cockpit Handbook, Fifth Edition, chapter 3, page 14. "The AHRS is a solid-state replacement for mechanical gyros."
The modern solid state devices do not suffer gyroscopic precession, so the sim adding gyro drift was completely wrong in the first place.
-
Several of us understood the nature of the problem quite clearly and it was reported to Zendesk.
-
Your comment about programming a button is actually a SimConnect issue and not the subject being discussed here.
-
The gyro drift issue seemed to have been fixed long ago. I am actually surprised that this topic has not been automatically closed.
PS. I have done a wee bit of real flying too, as have quite a few others here using this sim since it first launched in August 2020 
Still seems to be an issue?
That does not look anything like a Cessna 172 G1000.
Well, I just learned about this feature, so I’m thankful!
CRJ
(and some d u m m y text here because, annoyingly, posts need to be longer than 10 characters)
AviatorDown, I was replying to the original title of this post. Pressing heading or any other method of SYNCING heading moves the heading bug to 360, not the current heading. I wasn’t talking about drift.
Not for me it doesn’t, it moves the bug to my current aircraft heading and has done so correctly for a long time.
You appear to have a problem that is different to the one discussed here that has been resolved for some time now.
I think you might find it more useful to raise a new topic of your own where people with the same problem as yours can discuss it.
AviatorDown, Please look at the name of the title of this thread. If you have nothing to contribute to that subject then mind your own business when it comes to my questions/comments on the subject named in the title. I won’t respond to any more of your replies and I thank you not to respond to any of mine in this particular thread. I am glad the drift issue is resolved. I used to fly airmail (almost 50 years) ago, IFR, night over Nevada every week night and had to reset the gyro about every 2 minutes to keep it within 10 degrees. I would write it up frequently but the company never fixed it. Oh the good old timebuilding days when any multi time was gold. Peace.
Folks - do NOT start engaging each other. Constructive, Relevant, Respectful. Final call.
1 Like
I am the topic author so it is my business and I definitely know what the title is because I wrote it.. No need to be rude, when nobody is being rude to you.
Hi,
I would be quite happy if you close this topic because the problem as discussed and identified quite clearly in the early posts on this subject appears to have been resolved by Asobo some time ago.
Thank you.
Closed at Topic Author’s request.
