Whenever I try TGM activities such as basic take off it always fails at the point I need to engage afterburner. I bring the throttle to max. Finally I used the F3 key to advance the Throttle full AB and I was able to continue. I checked controls and the axis goes full left/right (up/down). ANy thoughts maybe a better throttle calibration. define MIl, define AB.
Do you mean you want to engage the afterburner by moving past the detent? If the afterburner is not part of the full throttle axis (THROTTLE 1/2 AXIS 0-100%) then I think you need to use programming software so that you can trigger a key press to engage the afterburner when you move past the detent and another one to turn it off when you return it. AAO does have that functionality, I can’t recall if Thrustmaster’s TARGET programming suite had it.
1 Like
Throttle does have the detent for AB. Well I should say it is optional you do can do either method. I can see it in the gages the my 0 to 100 does not even go full MIL. I will look and see if you can program a button in FS for AB.
There’s a “Toggle Afterburner” keybindings option in the MSFS settings. I bind it to one of the momentary switches on my warthog HOTAS throttle.
Basically, advance throttle to full, then push and hold toggle switch for afterburner. Release to stop afterburner.
1 Like
Ok, I investigated the issue a bit. I had not previously hopped into Asobo’s F-18.
Firstly it seems that all Asobo’s throttle assignments will stop at the 80% virtual detent.
And secondly the way Asobo coded the afterburner toggle is so that if you move the throttle at all after toggling the afterburner the throttles will revert to the 80% position.
This latter point meant my recommended button method didn’t quite work. Rather what I had to do was to put a virtual button (for the afterburner toggle) on contant repeat that would be activated at the end of the throttle’s range. Then moving the throttle to full forward position into the button’s set operating range caused the throttles on the Hornet to move past their detents to 100% position and stay there until returned below the button’s operating range. I did this with payware program called Axis and Ohs, but I recall the TARGET suite being reasonably well featured so it might be possible with it as well.
If TARGET does not support then another method I found was this: move the Hornet’s throttles to the virtual detent at 80%, then hold mouse left click and press right click on each throttle to disable the virtual detent. This allows the throttles to be moved freely within their entire range. The catch is that if you bring the throttles to idle the virtual detents will toggle back on and you are restricted to 80% max again.
2 Likes
Thank you, I have it fixed. First I missed the filter to display all . Changed that to ALL and immediately found Afterburner. Assigned a button and all is well. Though I do find it odd that it is in engine instruments.
Sounds like I misunderstood what the issue was then. I thought you wanted to make the Hornet’s afterburner work on your Warthog throttle without having to push a button for it (since the Thrustmaster Warthog throttle, similar to the virtual throttle on the Hornet, has an actual afterburner detent).
So for clarity’s sake, that’s what the advice I gave was intended for. The first method binds a virtual button to certain range within the controller’s throttle axis (which is not possible in MSFS natively, must use programming software like Thrustmaster’s own T.A.R.G.E.T or third party AAO) while the second method simply disables the virtual afterburner detents in semi-persistent manner on the Hornet so you can move your throttle past them.