Warthog Stick - Cougar throttle
-
Hey guys, I am trying to set my game up to use the Warthog Stick Cougar throttle. I know the Cougar stick will sit unused behind the desk and I am OK with that… My question is how do I make it all work? When I go into controllers at the main menu, all of the parts and pieces show up and are select-able but when I enter the game nothing works.
-
Hey guys, I am trying to set my game up to use the Warthog Stick Cougar throttle. I know the Cougar stick will sit unused behind the desk and I am OK with that… My question is how do I make it all work? When I go into controllers at the main menu, all of the parts and pieces show up and are select-able but when I enter the game nothing works.
So, the controller you select through the drop down menu is the only one that BMS uses, by default. Two options for dealing with that.
One, I understand TARGET is capable of combining together the two joysticks into a single virtual stick that BMS sees instead of the two actual sticks.
I have little idea of how to achieve this, as I dont use TARGET (or a warthog).
Option two, if you click the Advanced button in the controllers window, a pop up window will appear which allows you to set various axes to specific things in game. The cool part is that you can assign any axis to any role, on any stick!
So to set this up, you would select the Warthog in the drop down menu, and then click Advanced, and then click the second tab at the top of the pop up window. From there, you’d assign the cougars throttle to be the throttle in game, and you would also set the avionics on the next tab over in the same way.
finally you would close that window and then click OK in the controllers page.
Should be all set up!
EDIT: found an old set of images I made to show the steps visually:
Hope that helps!
I know the Cougar stick will sit unused behind the desk and I am OK with that…
I did that for a while, but it looked so forlorn and unused…
-
Can also buy a TUSBA from Realsimulator.com which will allow you to plug the TQS into an USB port without needing the Cougar FSS anymore. Thus you can use the WartHog FSS and Cougar TQS together, minus the Cougar FSS. You then pick the TUSBA TQS Throttle in the menus as Blu has shown.
-
I too like the idea of combining Cougar throttle with Warthog stick, but my Cougar throttle and it’s faulty microstick was one of the reasons I got me a Warthog to replace my so so working Cougar. This and the fact that Warthog doesn’t have pots. And it looked a better choice over FSS since I am really not confident doing some technical surgery.
Unfortunately I used to fly a lot with Cougar and the muscle memory makes flying with Warthog almost a pain. It is much easier to be a smooth pilot with digital controls, but flying alone in BMS just doesn’t do the trick in campaing.
A bit off topic, just a small rant over my low self esteem.:nosep::roll:
-
I too like the idea of combining Cougar throttle with Warthog stick, but my Cougar throttle and it’s faulty microstick was one of the reasons I got me a Warthog to replace my so so working Cougar. This and the fact that Warthog doesn’t have pots. And it looked a better choice over FSS since I am really not confident doing some technical surgery.:
Interested in selling your defective Cougar throttle? If so, PM me.
-
Hello! I have a problem with my hotas… I use a Warthog stick and the Cougar TQS with the TUSBA of RS. By the first time I made the set-up, everything were great! At the second time I run BMS 4.32, i saw that the profile was gone (…) and that the Warthog, even it was calibrated, cannot be chosen in the Advanced Options of FLIGHT CONTROL set up. You can see the picture to figure it out… I loaded the profile again, made all the lost assignments but the problem still remains…
So when I’m airborne, the movement of the bird is taking place by the…cursor of the TQS!!! The Warthog has fully functional all of it’s buttons, but NO ACTION in any movement! I repeat: Calibration has already been done!
Please I need your help guys! Thanks in advance!
-
First try changing them to keyboard. Then for joystick X/Y axes choose Warthog joystick X/Y axes.
(0) means first controller, it doesn’t mean off. (1) is second controller etc. It looks fine to me. -
You see, that’s the problem! I cannot select the Y,X Axes of Warthog! It’s like a dead option! That’s why I uploaded the photo…
Is there a chance to cause the problem the thing that I didn’t update the firmware of the TUSBA R2?? -
No, TUSBA has nothing to do with the Warthog. Did you choose and set keyboard first then try to choose Warthog?
try setting Warthog axes to keyboard and set cursor to TUSBA cursor option. Then try choose Warthog X/Y axes.
-
Problem solved! Thank you guys!
-
Hello guys. I’ve just bougth Warthog stick to replace my cougar stick and combine it with TUSBA. My question is, if I want get real assignments, I must to do Foxy or TARGET actions ? What profile are you using for this combination ? I’m a little bit losed about Foxy and TARGET. Foxy is for cougar and TARGET for Warthog? But I have both now… How I should combine them?
Thanks for advance
-
Hello guys. I’ve just bougth Warthog stick to replace my cougar stick and combine it with TUSBA. My question is, if I want get real assignments, I must to do Foxy or TARGET actions ? What profile are you using for this combination ? I’m a little bit losed about Foxy and TARGET. Foxy is for cougar and TARGET for Warthog? But I have both now… How I should combine them?
Thanks for advance
Or use neither software and make a DirectX keyfile. That is what I did.
-
Hello Icarus, thanks for your reply! What are you mean with DirectX keyfile ? How can I do that? I’m a beginner in this world.
Thanks
-
HI Icarus … I too would be interested if you could share your process for directx keyfile… and the file itself
I have warthog joustick via normal USB and cougar TQS via TUSBA though not been able to get it to function properly … used muds profile and warthog plus RO the joystick and xis keyfiel seems to have stabilised things but no TQS
-
DirectX keyfile allows you to use software or skip software entirely if you wish and use DirectX alone to program your buttons. DX also avoids conflicts with keystrokes and is much more reliable.
I just replaced all the keystrokes in my 4.32 keyfile with the new ones from 4.33. Then added the DX commands below. You can use the DX Setup Guide in the 4.33 docs folder or Kolbe’s BMS Keyfile Manual in the 4.32 joysticks folder in 4.32 for explanations on how it works. You can also use Dunc’s DX setup too, but he uses Foxy (I used his for years before I did my own).
I have my Cougar, TUSBA, MFP’s, MFD’s, and switches all programmed with DirectX only and no software. Its a bit of work, but well worth it in the long run.
My entire file is useless to you unless you have all the same switches and controls as I do.
Here is what I have in my keyfile for the Cougar stick and the TUSBA for a reference. Your button numbers (the first number) will be different.#===================================================================================
#################################################################Full real TM HOTAS Couger DX button mapping,
this is the UNSHIFTED (without holding Pinky/S3) layer.
Notes:
Windows counts the buttons from DX 1 to 32,
BMS counts the buttons from DX 0 to 31.
For the DX to work properly, you HAVE to make sure that
the Falcon BMS config file includes the following setting:
set g_bHotasDgftSelfCancel 1
(this is set to 0 by default, so please change it)
#################################################################
The 1st number after the function name is the DX button number,
the rest of the line is always the same and irrelevant for us.
TG1 (Win DX1 = BMS DX0)
SimTriggerFirstDetent 0 -1 -2 0 0x0 0
Pickle/S2 (Win DX2 = BMS DX1)
SimPickle 1 -1 -2 0 0x0 0
Pinky/S3 (Win DX3 = BMS DX2)
SimHotasPinkyShift 2 -1 -2 0 0x0 0
Paddle/S4 (…and so on…)
SimAPOverride 3 -1 -2 0 0x0 0
MslStep/S1
SimMissileStep 4 -1 -2 0 0x0 0
TG2
SimTriggerSecondDetent 5 -1 -2 0 0x0 0
TMS/H2
SimTMSUp 6 -1 -2 0 0x0 0
SimTMSRight 7 -1 -2 0 0x0 0
SimTMSDown 8 -1 -2 0 0x0 0
SimTMSLeft 9 -1 -2 0 0x0 0DMS/H3
SimDMSUp 10 -1 -2 0 0x0 0
SimDMSRight 11 -1 -2 0 0x0 0
SimDMSDown 12 -1 -2 0 0x0 0
SimDMSLeft 13 -1 -2 0 0x0 0CMS/H4
SimCMSUp 14 -1 -2 0 0x0 0
SimCMSRight 15 -1 -2 0 0x0 0
SimCMSDown 16 -1 -2 0 0x0 0
SimCMSLeft 17 -1 -2 0 0x0 0The TRIM hat/H1 will NOT be mapped here, hence it will
default to POV changes. We will use the SHIFTED layer
on the POV for TRIM later.
#####################################################################
This is the SHIFTED (with holding Pinky/S3) layer.
Pressing PINKY/S3 + some button will result in a DX
number which is “original DX button number + 256”.
So e.g. the Uncage button - which is Win DX24 / BMS DX23
by default - will become BMS DX23+256 = DX279 here.
Shifted buttons that should do THE SAME as the unshifted ones
do NOT need to be mapped at all.
Shifted buttons that should do NOTHING at all (hence only work
as unshifted buttons) need to be mapped to “SimDoNothing”.
NOTE: for the DX shifting to work properly, you HAVE to make sure
that the Falcon BMS config file includes the following setting:
set g_nHotasPinkyShiftMagnitude 256
(this should be there by default, please just crosscheck)
#####################################################################
TG1 (Win DX1 = BMS DX0+256 = BMS DX256)
SimDoNothing 256 -1 -2 0 0x0 0
Pickle/S2 (Win DX2 = BMS DX1+256 = BMS DX257)
AFResetTrim 257 -1 -2 0 0x0 0
Pinky/S3 (Win DX3 = BMS DX2+256 = BMS DX258 ) *******had t make a space between 8 and ) to stop smiley face emoticon.
SimHotasPinkyShift 258 -1 -2 0 0x0 0
Paddle/S4 (…and so on…)
SimEject 259 -1 -2 0 0x0 0
MslStep/S1
SimDoNothing 260 -1 -2 0 0x0 0
TG2
SimDoNothing 261 -1 -2 0 0x0 0
TMS/H2
OTWSelect3DCockpitMode 262 -1 -2 0 0x0 0
OTWSelectF3PadlockModeAG 263 -1 -2 0 0x0 0
SimRadarSnowplow 264 -1 -2 0 0x0 0
OTWSelectF3PadlockModeAG 265 -1 -2 0 0x0 0DMS/H3
FOVToggle 266 -1 -2 0 0x0 0
OTWToggleScales 267 -1 -2 0 0x0 0
ToggleNVGMode 268 -1 -2 0 0x0 0
RecenterTrackIR 269 -1 -2 0 0x0 0CMS/H4
SimEWSPGMInc 270 -1 -2 0 0x0 0
SimEWSProgInc 271 -1 -2 0 0x0 0
SimEWSPGMDec 272 -1 -2 0 0x0 0
SimEWSProgDec 273 -1 -2 0 0x0 0The TRIM hat/H1 has its own syntax.
(Please just believe me that this section is ok, a full explaination
is available in the “DX Shifting” docu).
We map TRIM for the SHIFTED layer here. There is no need to map
the UNSHIFTED stuff (POV change), because BMS will automatically
use POV for ALL unmapped/unused layers by default.
AFElevatorTrimUp 0 -1 -3 0 0x0 0
SimDoNothing 0 -1 -3 1 0x0 0
AFAileronTrimRight 0 -1 -3 2 0x0 0
SimDoNothing 0 -1 -3 3 0x0 0
AFElevatorTrimDown 0 -1 -3 4 0x0 0
SimDoNothing 0 -1 -3 5 0x0 0
AFAileronTrimLeft 0 -1 -3 6 0x0 0
SimDoNothing 0 -1 -3 7 0x0 0
OTWViewUp 2 -1 -3 0 0x0 0
SimDoNothing 2 -1 -3 1 0x0 0
OTWViewRight 2 -1 -3 2 0x0 0
SimDoNothing 2 -1 -3 3 0x0 0
OTWViewDown 2 -1 -3 4 0x0 0
SimDoNothing 2 -1 -3 5 0x0 0
OTWViewLeft 2 -1 -3 6 0x0 0
SimDoNothing 2 -1 -3 7 0x0 0#################################################################
TUSBA DX button mapping,
#################################################################
Cursor Enable/T1
SimCursorEnable 236 -1 -2 0 0x0 0
Radio Switch/T2-T5
SimTransmitCom2 225 -1 -2 0 0x0 0
SimTransmitCom1 226 -1 -2 0 0x0 0
SimCommsSwitchRight 227 -1 -2 0 0x0 0
SimCommsSwitchLeft 228 -1 -2 0 0x0 0Uncage/T6
SimToggleMissileCage 235 -1 -2 0 0x0 0
Dogfight/T7-8
SimSelectSRMOverride 230 -1 -2 0 0x0 0
SimSelectMRMOverride 231 -1 -2 0 0x0 0Speedbrakes/T9-10
AFBrakesOut 233 -1 -2 0 0x0 0
AFBrakesIn 234 -1 -2 0 0x0 0#################################################################
TUSBA SHIFTED DX button mapping,
#################################################################
Cursor Enable/T1
SimEmergencyJettison 492 -1 -2 0 0x0 0
Radio Switch/T2-5
AWACSDeclare 481 -1 -2 0 0x0 0
TankerDoneRefueling 482 -1 -2 0 0x0 0
TankerReadyForGas 483 -1 -2 0 0x0 0
TankerRequestFuel 484 -1 -2 0 0x0 0Uncage/T6
SimSlapSwitch 491 -1 -2 0 0x0 0
Dogfight/T7-8 unmapped, they should ALWAYS use unshifted functionality,
just listed here for reference.
SimDoNothing 486 -1 -2 0 0x0 0
SimDoNothing 487 -1 -2 0 0x0 0
Speedbrakes/T9-10 unmapped, they should ALWAYS use unshifted functionality,
just listed here for reference.
SimDoNothing 488 -1 -2 0 0x0 0
SimDoNothing 489 -1 -2 0 0x0 0
-
Listen to Icarus. he helped me get mine set up. thanks Icarus