Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum
  1. Home
  2. Just Flight
  3. MSFS Products
  4. Hawk T1/A Advanced Trainer
  5. Glideslope inactive?

Glideslope inactive?

Scheduled Pinned Locked Moved Hawk T1/A Advanced Trainer
5 Posts 2 Posters 551 Views 2 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.
  • A Offline
    A Offline
    Adamski_NZ
    wrote on last edited by
    #1

    First of all - congratulations on your release for MSFS - I'm thoroughly enjoying it!!

    Try as I might (and at various airports) I can't get the glideslope to activate. The localiser works fine and the HSI knob works, the DME works - but the [red] flag for the glideslope remains showing and the g/s indicator never moves.

    This is with and without the A/P engaged - and with and without approach mode being selected.

    Also - I'm finding that to engage the A/P en-route in GPS mode, I have to de-tune then re-tune the frequency for it to "take". This appears similar to a bug with the PMDG DC-6, where you have to toggle between VOR and GPS on the GTN to kick things off. Could it be a simliar (Asobo-related) problem?

    Adam.

    A 1 Reply Last reply
    0
    • A Adamski_NZ

      First of all - congratulations on your release for MSFS - I'm thoroughly enjoying it!!

      Try as I might (and at various airports) I can't get the glideslope to activate. The localiser works fine and the HSI knob works, the DME works - but the [red] flag for the glideslope remains showing and the g/s indicator never moves.

      This is with and without the A/P engaged - and with and without approach mode being selected.

      Also - I'm finding that to engage the A/P en-route in GPS mode, I have to de-tune then re-tune the frequency for it to "take". This appears similar to a bug with the PMDG DC-6, where you have to toggle between VOR and GPS on the GTN to kick things off. Could it be a simliar (Asobo-related) problem?

      Adam.

      A Offline
      A Offline
      Adamski_NZ
      wrote on last edited by
      #2

      ARRRGH!!! My mistake!!!! I've been having the Navigation MODE selector set to "TACAN"the whole time. It should be toggled to ILS. OMG I feel so stupid!!!!

      Sorry .........

      b3lt3rB 1 Reply Last reply
      2
      • A Adamski_NZ

        ARRRGH!!! My mistake!!!! I've been having the Navigation MODE selector set to "TACAN"the whole time. It should be toggled to ILS. OMG I feel so stupid!!!!

        Sorry .........

        b3lt3rB Offline
        b3lt3rB Offline
        b3lt3r
        wrote on last edited by
        #3

        @adamski_nz Don't!

        I spent an hour last night trying to get it to work and did what you did, plus I'd moved the UHF Ariel switch up instead of down when I was trying to sot both ILS and VOR nav...

        A 1 Reply Last reply
        0
        • b3lt3rB b3lt3r

          @adamski_nz Don't!

          I spent an hour last night trying to get it to work and did what you did, plus I'd moved the UHF Ariel switch up instead of down when I was trying to sot both ILS and VOR nav...

          A Offline
          A Offline
          Adamski_NZ
          wrote on last edited by Adamski_NZ
          #4

          Here's the culprit!

          alt text

          The problem occurred because I was following the manual slavishly/literally - and I don't think switching the selector from default/TACAN to ILS on approach was mentioned (though I'll check).

          A 1 Reply Last reply
          0
          • A Adamski_NZ

            Here's the culprit!

            alt text

            The problem occurred because I was following the manual slavishly/literally - and I don't think switching the selector from default/TACAN to ILS on approach was mentioned (though I'll check).

            A Offline
            A Offline
            Adamski_NZ
            wrote on last edited by
            #5

            @adamski_nz said in Glideslope inactive?:

            The problem occurred because I was following the manual slavishly/literally - and I don't think switching the selector from default/TACAN to ILS on approach was mentioned (though I'll check).

            The manual is 100% correct. A case of 100% user error!

            Now I can get back to enjoying this wonderful JF offering - inside the cockpit and outside (such detail!!).

            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