Hawk T1/A Advanced Trainer

@martyn interesting thanks, I actually bound them both to my Trimmer switch. Maybe they did that just to differentiate it easily.

I've managed to map almost everything in the Cockpit thanks to the easily accessible LVARs. The only LVAR that doesn't seem to work is the barometric setting on the standby altimeter, assuming it has some other code that moves the digits and needle simultaneously.

@timw

Have you tried flying without the various controls attached? "old CH Fighterstick converted to USB with a Leo Bodnar board" does sound like it could be an issue?

This is worth a watch: https://www.youtube.com/watch?v=nlq2FuW0UhI

@mattaf1990 said in Crash To Desktop:

Hello. I've just purchased the Hawk T1 and unfortunately, I am unable to load a flight with it as the game crashes to desktop at around the 75% loading mark. This only happens with the Hawk, all other planes seem to work fine. Has anyone else experienced the same issue?

Your best bet would probably be to contact Just Flight support. There is a link on the Just Flight website www.justflight.com

https://support.justflight.com/support/home

@gabe777

Panic over.

Feel stupid... but it may happen to someone else.

There was a conflict with Auto Copilot ... pressing a button was activating the damn thing and it was overriding the AP.

All sorted.

Make sure built in Copilot is all OFF.

quick update on this - i ended up changing out my controls from the honeycomb alpha and bravo and went back to an old stick and throttle i used for dcs. i mapped the trim (nose up / nose down) to one of the switches on the stick. things seem to be working quite a bit better. the plane definitely won't go into a nice stable trim but it's far more docile and controllable compared to what i was trying to deal with on the hc bravo and the trim wheel. and what shouldn't come as any surprise, it's nicer flying the hawk with a proper stick versus the yoke that i use for all my other planes.

anyhow, unless anyone has any other ideas, i am considering this case closed for me, at least.

Although I can't provide a timescale at this stage, we are looking to add new effects following the release of the default F/A-18 which introduced some suitable effects.

@racerzeroone This will be fixed in the next update (aiming for release early next week)

@martyn turns out it was a FS2020 issue so all solved now! Cheers :)

@bradbrad It was probably the left throttle being all the back into the detent, which shuts off the fuel on some joysticks.

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