I've recently bought the Thrustmaster Warthog system and would like to know how to assign certain functions to certain switches and axes in FSUIPC (registered), if it be possible.  I have never tinkered with FSUIPC before, and it seems a bit daunting at first glance.  I would like to assign the red and gray rocker switches on the right hand throttle grip to control wing sweep.  I would like to use the red one to control forward and aft sweep movement, and the gray one to control the Bomb and Auto Modes.  I would like to use the Flap switch to control the flaps, and the throttles' slider axis to control emergency wing sweep.  I'd also like to be able to use either the 8-way + button hat switch or the mouse control as a cursor for working the radar.

Oh, and what settings should I use to adjust the throttles so that MIL power in the sim corresponds with the position of the afterburner stop on the throttle?

I know that's a lot (and there's even more I'd like to do), but any help would be appreciated.

Hello there, I think you'll really enjoy the Warthog, it's remarkably close to the F-14 stick and throttle setup.

The right-side (thumb) hat switch on the throttle duplicates the sweep rocker as it was implemented in the real F-14. UP assigns AUTO mode, DOWN assigns BOMB Mode, BACK sets MAN AFT Sweep, and FWD sets MAN FWD Sweep. With that said, you can of course setup the controller however suits you best.

A complete list of instructions can be found in Volume 3 of the flight manuals; go to page 3-4 for the list of standard commands, and page 23-36 for a complete list of the custom (lua) commands. If you have any trouble after reading through those pages, just give a holler and we'll get you squared away.

I'll have a look at that in the next few days, although the BIG hurdle right now is that the two throttle axes and the slider axis don't register at all in FSX:Acceleration, possibly because I have the two controllers going into a USB hub.  I don't think FSUIPC detected them, either.

Maybe I can use one of the other hat switches and buttons for a radar cursor.

Hmm, that's an odd problem. I have a Warthog + Saitek Rudder pedals, and those all feed into a hub, and haven't had any issues with device recognition.

Are they being detected by the operating system as expected? E.g. Can you Thrustmasters' calibration menu through the device menu in Windows control panel?

Also using a hub for TM Warthog, CH pedals, etc. A couple of tutorials on 'Tube for FSUIPC, but as jcagle mentioned, I have the same settings for the big ticket "flying buttons" I need. Those include the sweep, speedbrakes, man. flaps and DLC, don't forget trim (at least pitch). Split throttles have to be calibrated separately within FSUIPC.

Just took the F-14 tooling around Oceana, and the throttles now seem to work.  Any recommendations for how to set the throttles to coincide with the Idle/AB detents on this bird only (and also on my VRS Superbug)?

This from the VRS forums, but I used it to set up FSUIPC. Of course, also flipped over the throttle detent on the TM Warthog throttles, to go over the AB gate from MIL power. As heavy as the throttles are, I still seem to lift them off my desk!

http://forums.vrsimulations.com/forums/phpBB3/viewtopic.php?f=94&t=5785&start=15#p104196

 

This from the VRS forums, but I used it to set up FSUIPC. Of course, also flipped over the throttle detent on the TM Warthog throttles, to go over the AB gate from MIL power. As heavy as the throttles are, I still seem to lift them off my desk!

http://forums.vrsimulations.com/forums/phpBB3/viewtopic.php?f=94&t=5785&start=15#p104196

 

That's why I have mine screwed to some wooden platforms that I made and attached to an office chair that I bought.  BTW, which switch controls the landing gear?

I don't have the gear linked to the throttle, like the real jet, one has to take your hand off to move the gear lever.

My first attempt at programming the controls with FSUIPC has been a complete bloody disaster.  I now have no control at all over the ailerons, elevators, or rudder.  WTF?  How do I undo this?!

Restarting the flight seems to have cleared it.  PS, My wingsweep switch isn't currently functioning.

Uhhh, can you elaborate a little more? How can we help? When you say that your wingsweep switch isn't working, do you mean via FSUIPC commands or via 2D panel?

Well, I finally got around to reading the manual and tinkering with FSUIPC, and I've managed to get the wing sweep switch, the manual sweep mode, and a few other commands set up in FSUIPC, but I'm a bit fuzzy on how to set the engines to shut off using the Idle detent.  The manual says to select the LUA and set certain parameters, but I'm not sure how to select that section of the throttle axis in order to do that.  Maybe I won't bother.  Oh, and BTW, I did finally manage to get the throttle to match the AB detent.

Try following these steps:

 

1) When you're in then main FS-UIPC menu, go to the "Buttons + Switches" tab

2) make sure the "Profile Specific?" is checked. (Please see the figure in the Manuals, Vol.3, page 23 for a visual reference).

3) Then move the Left throttle to the OFF position.

* You should notice that Joy# [blank]  [blank] Btn#   turns into  Joy# [NUMBER]  [NUMBER] Btn#

* E.g., on my machine it's Joy# [1]  [29] Btn#

4) Check the box "Select for FS Control"

 

5) In the section "Control sent when button pressed", select "Lua Aerosoft F14AB"

6) Now enter the parameter number "10"

 

7) In the section "Control sent when button released", select "Lua Aerosoft F14AB"

8) Now enter the parameter number "11"

* The screen should now look exactly like the example on Vol.3, page 23, except that "3" and "5" are replaced with "10" and "11"

 

9) Next, move the Right throttle to the OFF position.

10) Repeat steps 4-8, but select parameters "12" and "13"

 

Do I need to do that for both throttles even if I'm only using a single programmed throttle?

Yes, because even though you might be using a single axis, the buttons are specific to each throttle lever. (I'm assuming you're still using a Warthog HOTAS)

 

Plus, I don't think you'd want a single action for both levers since a hot-start would be unavoidable (e.g. you can only crank one engine at a time, and you have to time the OFF->IDLE action); plus a single action wind up would shutting down both engines if there was only a compressor stall in one.

I tried it like you said, and FSUIPC didn't seem to notice when I moved the throttles.

Going into the IDLE/OFF stop on the Warthog HOTAS requires (slightly) lifting the throttle and then pulling back. I would do that in the (Windows) hardware control menu to make sure that the button is actually sending a signal. I can't imagine that FSUIPC would miss a button press that was successfully transmitted to the Operating System.

Windows shows no button press when I pull the throttles into the cutoff position.  Yes, up and over the detent, not just pulled to idle.

This is what I get on my machine with both throttles in the OFF position.

 

If you're not seeing buttons 29 & 30 light up, then you might have a defective joystick.

Okay, buttons 29 and 30 light up, but not when using the virtual Thrustmaster combined setup.  If I don't turn the TARGET software on, will that affect anything?

That's interesting, buttons 29 and 30 seem to be assigned to two of the positions on the thumb hat switch on the right hand grip?  Oh, and which one should be the left engine and which one's the right?

I never use TARGET, so can't give much advice about it.

 

Don't use buttons 29 and 30 if they are not going to your iDLE/OFF detent, that's just what happens on my machine. What you need to identify is if any buttons light up when you go into the IDLE/OFF detent (from post #18, that sound like a no?).

 

If no buttons illuminate when you flip the IDLE/OFF detent in the same screen as what I've shown in post #19, then you should contact Thrustmaster, because you might have a defective throttle.

With TARGET off, Buttons 29 and 30 illuminate when I put the throttles into the cutoff detent, so they do work.  With TARGET on, buttons 29 and 30 become part of the Hat switch.  It's gotta be something in the FSX profile that TARGET uses to map all the buttons, not a physical defect.