Heading Bug Broken

jcallum

@derek Thanks Derek. I submitted a ticket. I understand that your devs cannot monitor the forum 24/7 but you would think that they could have a quick look every month or so to see if there were any common issues or things that could be quickly resolved. We'll see how I make out with the ticket.
Cheers,
John.
P.S. Given the popularity of this plane, I am surprised by the lack of community response to posts. Why are users not using this forum? I must admit that I have been a Just Flight customer for some time and this is the first time I have visited the forum.

Derek

@jcallum said in Heading Bug Broken:

I have been a Just Flight customer for some time and this is the first time I have visited the forum.

I think you have answered your own question.

Martino72

For me the heading bug also doesn't work. With the last version no problem. Unfortunately I deleted the last version and can't download it again.

Martyn

Our support team are sending a replacement WASM gauge to those of you who submitted support tickets for this issue. Once we've confirmed that fixes the issue, we'll update the installer.

Martino72

Hi, Martyn,

for me the replacement WASM gauge file works for the Arrow III. Already answered in the ticket. As the same problem occurs with the Turbo Arrow, the same change should help.

Regards,
Martin

jcallum

@martino72 Hi Martin. The replacement wasm gauge works better for me now too. However, I still don't seem able to adjust the heading bug as I can with other aircraft and as I was able to do with the PA28 before the last update. Are you using the msfs variable AUTOPILOT HEADING HOLD DIR to adjust the heading bug?
John

Martyn

@jcallum We have custom logic for the heading mode and bug so you will need to use the SET HEADING BUG event to set the heading bug value (in degrees). You can also use SELECT HEADING BUG (with PLUS/MINUS) and INCREASE/DECREASE HEADING BUG events to move it incrementally.

jcallum

@martyn Thanks Martyn. I will try the INCREASE/DECREASE HEADING BUG and see how that works.
John.

jcallum

@martyn Thanks Martyn. That worked. I used the simconnect events HEADING_BUG_INC and HEADING_BUG_DEC.
John.

Martino72

Hi John,
sorry, came home from work a few minutes ago.

In Spad.neXt I'm using "AUTOPILOT HEADING LOCK DIR by 1 (Increment/Decrement for my GoFlight MCP-Pro and this works without problems. For the GF MCP-Pro Display I use "AUTOPILOT HEADING LOCK DIR:2"

Martin

Tailhook

Bumping this because it is still broken. This issue only affects the Arrow and Turbo Arrow(s), the Warrior works normally. AUTOPILOT HEADING LOCK DIR is no longer referenced/changed with the heading bug.