Hawk T1/A Advanced Trainer

@derek Raised a ticket this morning, and a couple of different options were given. In the end it turned out to be Fuel Valve assignments that caused the issue as the fuel valves are used in the Hawk to switch from Idle to HP Off. If I don't switch the fuel valves on with my HOTAS and manually click on the levers instead, it all works. Thank you for your help. Thought I'd post this response incase any one in the future experiences the same issue.

Unfortunately it looks like that assignment got broken in a recent Sim Update so we'll need to find a solution for the next Hawk T1 update.

Thanks for reply. It does work as you say when tuned to an known ILS but I guess the TACAN I was using does not ident.

@martyn Thanks for the info and good to hear of the change in a future version.

@delta558 So glad the PIO (Pilot Induced Oscillation) has been sorted, I was starting to think it was me!

@baw24p Of course. The problem is that the volume in the Hawk appears out of step - i.e. significantly louder - than every other aircraft I have flown in MSFS. As a result it becomes necessary to change settings within the sim each time you change from another aircraft to the Hawk or back again: I tend to shift the master volume up or down by a significant amount to adapt. What would have been wrong with simply moderating the volume so it was in step with other aircraft rather than imposing this need to repeatedly adjust and readjust on customers? I note this appears not to have been fixed in v0.1.5, which seems a missed opportunity.

So I've got some answers, so posting in case it helps others... @katchaplin had the perfect answer, it was the mapping of mixture. There is freeware scenery for RAF Valley (EGOV) and there appear to be differences in the terrain levels. Once again a mapping conflict. I searched for the landing light and found a button mapping that was in conflict with and switch on the cockpit panel. Yet again a mapping conflict... starting to see a bit of a pattern here. I had the Autopilot Master mapped to a switch and that was stopping / conflicting with the EFB buttons.

@martyn thanks for the reply...you are correct, I misread the panel markings, I thought it was a 3 position switch, as you pointed out I was wrong, RTFM as we used to say in the military.

Confirmed, reverse sensing only works for right hand side of the course radial, it was not fixed in latest update, which I believe was today. example; if you fly on the "from side" of the Vor, flying away from the Vor, with your airplane heading and OBS heading matched, and fly to the right, the course deviation indicator moves to the left, which is correct, if you turn left and cross the OBS course radial, the course deviator only moves to the right as far as the center, then moves back to the left which is wrong.

@martyn Thanks Martyn. That's where I started and assumed was the default. I can confirm that in my setup, starting from the front, on the runway with all systems hot, my MSFS default, I'm not able to retract my front gear properly. Eventually I'll get Hydrolic 1 pressure failure. I'll be happy to help you diagnose this issue if you need any screen shots of my setup from me. Thanks, Terrance

@martyn Thank you: I'd not realised this was the same issue. The fix someone identified there works for me. Simply switching the engine ignition switch to "off" stops this problem arising.

Please check that you have Legacy Option selected under General Options - Accessibility - Cockpit Interaction System.

@derek You are right, Derek. I should've opened a support ticket. Now, i have repaired the installation with the installation file and everything is fine now. Thanks a lot!

@guenseli When this issue happened to me, but with another aircraft, it was another livery for that specific aircraft that caused the white screens. If you want to try this solution, move out of the community folder all the liveries for the Hawk temporarily and see if it helps. If not reinstalling the Hawk is the next step. A cfg file might have been overwritten. Hope this is of any help.

I just retested the Hawk with the garmin 750. It does appear that the ILS frequency on the 750 may override that in the Hawk GPS. I made sure the frequency in both GPSs were the same and this time it captured both the LOC and the glideslope very well.

@ben104 Hey Ben, I’m uncertain how exactly Just Flight models this, but my impression is that, since the Hawk doesn’t have a VOR receiver, all non-GPS navigation is done through the TACAN. Since MSFS was not modeling TACAN, JF works around this by having TACAN channels EQUATE to VOR frequencies. Now the Hawk does have an ILS receiver. But ILS frequencies are, by convention, in a lower frequency band. So, with the TACAN/ILS switch in ILS you should only get CDI sensing for an ILS frequency, if you had one dialed in. And dialing in a VOR frequency, should result in no response at all. Dialing in the TACAN equivalent as printed in the manual, however would. Unless something has changed recently in MSFS/the Hawk.