Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum
  1. Home
  2. Just Flight
  3. MSFS Products
  4. PA-28R Turbo Arrow III/IV
  5. Heading bug change

Heading bug change

Scheduled Pinned Locked Moved PA-28R Turbo Arrow III/IV
7 Posts 3 Posters 604 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    jcallum
    wrote on last edited by
    #1

    Can you elaborate on what changed in the recent update with the heading bug. I am using Saitek panels and the heading bug was working fine for me using the simconnect variable autopilot heading lock. After the update I don't seem able to adjust the heading bug. Thanks.
    John.

    S 1 Reply Last reply
    1
    • J jcallum

      Can you elaborate on what changed in the recent update with the heading bug. I am using Saitek panels and the heading bug was working fine for me using the simconnect variable autopilot heading lock. After the update I don't seem able to adjust the heading bug. Thanks.
      John.

      S Offline
      S Offline
      skeptikantin
      wrote on last edited by
      #2

      @jcallum Hey, I have the same problem. Support told me it's HSI_HDG_BUG, despite me telling them explicitly that this variable does not move the heading bug via Spad.Next. The only thing that kind of "works" (i.e., give any kind of reaction) is HSI_HEADING_KNOB, which I don't think is how it is supposed to work (and it doesn't work properly for that matter).

      If any of the developers read this, it might be helpful to give a solid description of which variables work and perhaps why they are so wildly different to the Warrior II (which still works on the simconnect variable). This might be more efficient than each of us submitting tickets that aren't read properly.

      J 1 Reply Last reply
      0
      • MartynM Offline
        MartynM Offline
        Martyn
        JF Staff
        wrote on last edited by
        #3

        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.

        Martyn - Development Manager

        J 1 Reply Last reply
        0
        • MartynM 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.

          J Offline
          J Offline
          jcallum
          wrote on last edited by
          #4

          @martyn Hi Martyn. Does the new wasm gauge work for both the Arrow and the Turbo Arrow? i.e. same file?

          John.

          MartynM 1 Reply Last reply
          0
          • S skeptikantin

            @jcallum Hey, I have the same problem. Support told me it's HSI_HDG_BUG, despite me telling them explicitly that this variable does not move the heading bug via Spad.Next. The only thing that kind of "works" (i.e., give any kind of reaction) is HSI_HEADING_KNOB, which I don't think is how it is supposed to work (and it doesn't work properly for that matter).

            If any of the developers read this, it might be helpful to give a solid description of which variables work and perhaps why they are so wildly different to the Warrior II (which still works on the simconnect variable). This might be more efficient than each of us submitting tickets that aren't read properly.

            J Offline
            J Offline
            jcallum
            wrote on last edited by
            #5

            @skeptikantin Hi. Try the simconnect event HEADING_BUG_INC/DEC. This works for me to move the heading big using spad.next.
            John

            S 1 Reply Last reply
            0
            • J jcallum

              @skeptikantin Hi. Try the simconnect event HEADING_BUG_INC/DEC. This works for me to move the heading big using spad.next.
              John

              S Offline
              S Offline
              skeptikantin
              wrote on last edited by skeptikantin
              #6

              @jcallum Brilliant work around (for being a send event only), thanks!!

              1 Reply Last reply
              0
              • J jcallum

                @martyn Hi Martyn. Does the new wasm gauge work for both the Arrow and the Turbo Arrow? i.e. same file?

                John.

                MartynM Offline
                MartynM Offline
                Martyn
                JF Staff
                wrote on last edited by
                #7

                @jcallum You can now download the latest version of all the PA28s from your Just Flight account to fix this issue

                Martyn - Development Manager

                1 Reply Last reply
                1
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Users