Hawk T1/A Advanced Trainer

@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.

@retiredman93231 Thanks for the info.

@martyn I have my warthog throttle ‘APU start’ button set to start/relight .Also another button which is a one way spring loaded switch set for ‘engine master’ (although that’s not responding as an engine master switch, prob not configured the correct command for that function). Also my throttle indent function is set to ‘toggle engine 1 fuel valve’.
All now unassigned, no more idle engine issues.
Why would these conflict with the running of the engine mid flight?

@katchaplin This appears to be another bug caused by SU7... JF is aware of it.

@martyn Hi, I still think this is broken as I flew yesterday to test this after an update with an RPM of 110+ and no indication... It's almost as if the engine temp stops just before reaching the limit but the RPM continues.
I will say I was flying like a D1ck... And in reality, the jet would not be operated as I flew it during that flight.

@bisinchi I agree, I feel like it does not bleed energy as it used to... Perhaps a real hawk pilot can shed some light?
During a run and break 360kts air brake out it does not seem to bleed energy too well either. As I understand you idle, air brake pull to the buffet which in this case seems to be 6/7G personally I would imagine in reality this is 3.5-4.5G.

@captain744 Since I fly both the Hawk and the Warrior, I unmapped the control for the Hawk, since part of my shutdown on the Warrior is to set the mixture to cutoff. Most people don't seem to want to have separate control schemes for different aircraft, but I find it much easier than trying to remember what the different buttons and sliders are mapped to, as the Warrior and Hawk are just 'slightly' different aircraft.

@jander I'd very much like this feature to be included too, especially as you are learning the systems.

@guenseli Thanks for the suggestion! We've made this and another change which should hopefully address this issue.

@martyn Thanks for fixing this so fast!