Warthog Script and Key
-
Hi,
I am brand new to the Warthog and scripting. I downloaded Mud’s profile and key. I was wondering what is the relationship between the key that goes in BMS and the script? Do I need to change the key if I am using a different profile such as Morphine’s?Thanks!
-
Hi,
congrats on your new Stick!
The .tmc file (for the TARGET script software) configures what key or button press will get sent to an application when you press a button or toogle a switch or whatnot on your warthog.
The .key (for BMS) configures which event in BMS gets triggered when a specific key or button press gets send to it.
For example:
The .tmc specifies that key ‘x’ gets send when you rock the china hat on the throttle forward.
So BMS receives a ‘x’ keypress an by the .key file translates that to the event ‘SimNextWaypoint’.So when you change to a different Warthog TARGET profile you will need a corresponding keyfile for BMS.
I had some trouble understanding all that jazz with the different files for the programming of the stick and how that ties in with BMS myself.
Looking at and trying to understand the profiles by Mud, Morphine and DonLduk really helped.Just start with the provided files (by Mud or someone else); check that all works as intended.
Then try somebody else’s profile to see what’s more to your liking and/or start tinkering to customize to your needs. -
Thanks, MudMover! I notices the joy stick axis in the profile. If I get a third party rudder pedal I assume I would not put it in the profile.
Thanks, Again!
-
Exactly, you just assign your rudder pedal’s axis in the BMS setup (Setup - Controllers - Advanced - Flight Control).
By the way (and if that wasn’t clear already): you have to assign your combined Warthog’s axis in the BMS Setup too.
-
It took me a while to figure this out. My previous system died as I was beginning to play around in the sim. I had a CH rudder pedal and a Warthog set up. I noticed that there were times when the stick worked but not the throttle, or vice a versa. I had similar issues with the rudder pedal, which I subsequently returned. I wasn’t able to quite figure it out.
I recently built a brand new system and noticed I had some of the same issues. I watched a tutorial on YouTube regarding Warthog set up in BMS. The guy mentioned that I should mark two config files as read only as the sim doesn’t alway save HOTAS preferences. I did this but still noticed issues - including the fact that the throttle and stick were listed as two separate devices. The set up screen in the YouTube video listed Thrustmaster Combined in BMS set up. I ended up loading Mud’s thrusmaster script first, then going into controller setup in BMS. At that point Thrustmaster Combined appear. I was able to get both throttle and stick to function in BMS.
I just decided to order a Thrustmaster rudder pedal. I assume I would set the toe brakes in the script. Do I also set the Z rotation in the script also?
Thanks again,
Blain -
for the warthog to work as a combined device you need to run target software!
-
I watched a tutorial on YouTube regarding Warthog set up in BMS. The guy mentioned that I should mark two config files as read only as the sim doesn’t alway save HOTAS preferences. I did this but still noticed issues - including the fact that the throttle and stick were listed as two separate devices.
When you connect your Warthog stick and your Warthog throttle to your PC, Windows detects two devices.
If you then just start BMS, two separate devices will show up in the BMS setup.As sub101 says, you first run the TARGET software (with the provoded .tmc script file).
This will then combine your two Warthog devices into one giant virtual controller.
If you start BMS now, the setup will show one device: ‘Thrustmaster Combined’.The reason for marking config files as read-only is that the config of all the axis assignments can get mixed up,
when you first configure all your ‘Thrustmaster Combined’ device’s several axis, then quit and
then forget to start your TARGET script before the next start of BMS.Then interesting things will happen to the assignments. Even if you then start the TARGET script and restart BMS
your old ‘combined’ assignments will be lost.
Hence the read-only for the config file after the initial configuration.
According to the 4.33U1 change log this shouldn’t happen anymore.Anyways: you want to make sure that your TARGET script is running, before you start BMS.
I just put that into my pre-pre-flight list.The set up screen in the YouTube video listed Thrustmaster Combined in BMS set up. I ended up loading Mud’s thrusmaster script first, then going into controller setup in BMS. At that point Thrustmaster Combined appear. I was able to get both throttle and stick to function in BMS.
I just decided to order a Thrustmaster rudder pedal. I assume I would set the toe brakes in the script. Do I also set the Z rotation in the script also?
BlainYou assign the rotation and the brakes of the rudder pedal directly in the BMS setup.
The TARGET software is only for sticks and the Thrustmaster MFD (as far as i know).
A tip for when you get your pedals: after you have configured them in BMS, it is best practice to always plug them into
the exact same USB ports afterwards, so that the ordering of Windows game controller IDs stays the same.When I got me my Warthog last year, I had quite a few head-scratching moments.
With DonLduk profile comes a pdf which was quite helpful to me. -
Hey Mud Mover,
I am trying my hand at using the TARGET GUI to program the HOTAS and rudder setup. When I had an F-22 stick and throttle there was a three way button on, I think the throttle, where you could create three different configs for the buttons on the throttle and stick. So I would set one group to Nav, one to A/A, and one to A/G. Is there something similar in the Warthog?Thanks,
Blain -
Ok, I just found the info regarding what I was describing. It is called, I think, the shifted state which can be assigned to any button. Back, Middle, and Forward. So now the question is, how do I assign that function to the CH button on the throttle.
-
I found out how to assign the U, D, and M function. I am trying to use the GUI to configure a profile for my HOTAS. In the BMS Full key file the fire command for the canon is ALT /. It appears to be different on Morphine’s and Mud’s key file. I can’t find them.
-
I my opinion your going about this the wrong way. You don’t need any shifted states, its not a kids Joystick or game.
Don’t use Target to program the stick, Use the In-Game dx programing method.
Find the function you want in the key file left click on it once and it turns blue now activate the corresponding stick button/switch. Move on to the next.
All the Stick & Most of the throttle can be programed this way untill you hit the 32 button limit. You then finish off the throttle and its base panel using target.
To do this reference the Manual for R/L HOTAS usage. TO-BMS1F-16CM-1.pdf
-
I my opinion your going about this the wrong way. You don’t need any shifted states, its not a kids Joystick or game.
Don’t use Target to program the stick, Use the In-Game dx programing method.
Find the function you want in the key file left click on it once and it turns blue now activate the corresponding stick button/switch. Move on to the next.
All the Stick & Most of the throttle can be programed this way untill you hit the 32 button limit. You then finish off the throttle and its base panel using target.
To do this reference the Manual for R/L HOTAS usage. TO-BMS1F-16CM-1.pdf
I agree that is the best way to do it. I use the bsf,bsm,bsb switch, to switch from nav to A-A, A-G, the middle
being NAV. -
Ok, I just found the info regarding what I was describing. It is called, I think, the shifted state which can be assigned to any button. Back, Middle, and Forward. So now the question is, how do I assign that function to the CH button on the throttle.
The shifted state only lasts as long as you press your shift-button.
Also, there are only two states: shifted and unshifted. So that might different to what you where used to with the F-22 and what you’re after now.I found out how to assign the U, D, and M function.
I just learned about the ‘layers’ function of the TARGET software
I should have read the manual more thoroughly.I am trying to use the GUI to configure a profile for my HOTAS. In the BMS Full key file the fire command for the canon is ALT /. It appears to be different on Morphine’s and Mud’s key file. I can’t find them.
Morphine’s setup uses the second trigger detent as the command for the gun.
He left the button TG2 (‘Gun Trigger’ in the warthog manual) unconfigured in his tmc file:
//TG2 //keyflie controlled
When you press TG2 on your stick, this will then send DX button number 6 to BMS.
So Morphine bound this DX6 button to the SimTriggerSecondDetent function in his key file:# TG2 SimTriggerSecondDetent 5 -1 -2 0 0x0 0 ```(DX button numbering is one off in BMS: button 6 becomes 5 in the keyfile) As the 'ALT /' keyboard command is no longer needed, he unbound the keyboard command in the keyfile:
SimTriggerSecondDetent -1 0 0XFFFFFFFF 0 0 0 1 “HOTAS-Second Trigger Detent”
I guess that's why you couldn't find it.
-
MudMover,
That’s a lot to digest. I need to review the scripting manual again. I thought I would crank everything up since I just got my TFRP pedals. I found that I had the same problem when I had CH pedals.I used the GUI and added stick, throttle, and rudders to the profile. Then I ran the profile without any key commands to verify that all would work in BMS. It appeared as Thrustmaster combined - good. I could see movement on the screen when I moved the rudder pedals, throttle, and stick. Then I hit the advanced tab.
The stick was fine - x and y axis. But BMS has Throttle and Right Throttle. Right throttle I set to Z axis, throttle I set to Z rotation. If I choose throttle combined for one and keyboard for the other I get a drift to the left when I push the throttle forward. Then it was time to configure the rudders. X rotation and Y rotation were available to be selected, but no Z axis for the rudders.
I quit BMS and shut down the profile and launched BMS again. Stick, throttle, and rudder appeared with the correct options for settings - axis, rotation, etc. I exited BMS again and launched the Target GUI. I unchecked TFRP from the profile - keeping only stick and throttle. I launched BMS again. This time I was able to properly configure stick, throttle, and rudder in the advanced tab. All worked in the game with no issues. I did not check the toe brakes. Will it work without a keyboard command in Target?
Is there a bug in BMS or Target? Or am I doing something wrong?
-
The last solution seemed to work. I tested it tonight. I kept the Thrustmater rudders out of the TARGET profile. Thrustmaster combined - stick and throttle appears in the drop down menu in set up along with the rudder pedals. By keeping them separate I was able to access to the Z Axis for the rudder pedals and assign the X and Y Axis for the toe brakes. Rudders worked as well as toe brakes.
Now I can go about using the TARGET GUI to start on the buttons. This is definitely not a kid’s game.
-
Sorry to crash, but it’s related…
I’m brand new to the Warthog too (today) and am wondering - do I need to start a script every time I want to use it? or does the Warthog hold the last run script in memory, similar to how the Cougar would store its current assignments? I’d prefer not to have to start TARGET (bleh) or the Script Editor every time I restart the PC.
TIA
-
the Warthog pretty much works out of the box if you simply plug it in and use Kolbe’s excellent key file editor to create a key file suiting your setup. I didn’t even install any drivers, nor TARGET. Sure you probably won’t get any of that fancy led lighting functionality like mil / gate indication and so on, but OTOH you keep your system clean(er) and have one possibilty less for things breaking in-flight (like scripts ceasing to work and so on).
All the best, Uwe
-
yes you do need to start target before running BMS. If you start target, from there you can link bms exe to run when script starts. my advice would be to create a script or gui. many more configuration possibilities