Hawk T1/A Advanced Trainer

@thefunkydunk Thanks for the feedback! The next update will introduce control assignments for toggling the different coloured smoke.

@voice-of-reason Will do thank you!

@harry_906 It looks like the hundreds digit is rolling over a lttle later than it really should... Submit a bug report to JF Support and see if they can do anything about it.

@chubster
Only advice I can give is to make small changes, create a bit of a dead zone on the sensitivity and then also make the sensitivity a bit lower.

Hope you get it sorted.

@darthmelbius Please see the TACAN limitations FAQ here: https://community.justflight.com/topic/2810/hawk-t1-faqs

Thanks Martyn, I had allocated a button on FSUIPC to APU STARTER. Moving the power to idle was causing the power to trip inflight when the switch was in the APU ON position. Switching this off has cured the problem! I tried this several times, APU OFF keeps the electrics online, APU ON and it trips out everytime. Also probably explains why this only happened in the air - there was no problem while taxying. Thanks for the support!

Thanks for the replies, just wanted to be sure I wasnt missing something. :anguished_face: Still be interested too know if they may be added as an options later etc. :crossed_fingers_light_skin_tone:

@martyn

Don’t know how I missed that! Thanks for the heads up. That’s made my day. 😁👍🙏🏻

@eker Thanks!!!!!
It is in the manual p 35 too .........

Yawdropping impressed over flight model. Now you can feel the touchdown. Is the head movement implemented?

And thanks for small details like tooltip frequency on Tacan.

@martyn aaaaah, there you go! I overlooked the rear cockpit - doh! Thanks

This is a must see video for anyone considering this aircraft... It shows what it can do in the hands of a good pilot!

https://youtu.be/EgS-JBlV_pw

@g0emf

The Hawk is now on sale but discount for the MSFS version is only on P3D and FSX owners. There is no cross-discount between FSX/P3D/MSFS and X-Plane as they are different development teams.

@captainsimms It did cause some issues yes and the fact we were unable to get our hands on the new SDK until today didn't help. We're making progress, a new build is now in test. Hard to judge right now whether or not it'll make it this week. We're hoping that's the case but no guarantees.