Warthog HOTAS Set-Up Help Please?
-
Apologies gents for being a little frustrated, but I spent a couple of hours getting no where earlier. :neutral: Many thanks for your help.
I will give your suggestions a try tomorrow now as it is late.
Regards
malcolmt16 -
Success! Thanks everyone for your help and patience.
-
Good to know
Did you use Morphineâs file ?
If yes, dont hesitate to get used to TARGET script functions, this way, you can fine tune your script to your needs.
Hereâs the guide for TARGET scripting, everything is explained here :
http://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/TARGET_Script_Editor_Basics_v1.5_ENG.pdf -
Great!
Happy hunting!
-
Hi,
I also have so much problems to configure BMS with the Warthog.
In BMS, if I use the BMS.key, I canât program the datalink, and if I use Keystroke.key, I canât program the NWS ! In the both cases, I canât program the MRM/DF Override Cancel function.
Yes, it is so ****ing complicated. I donât know know how many hours I spend trying to program correctly my Warthog already;
Thanks to Morphine for the profile, but some functions show on the BMS Dash-1 pages 26-27 and pages 51-52 are not on the profile (IFF instead of Datalink on the throttle for example). And I have no idea how to program the Warthod with a script (I tried already, but I donât understand anything about it).
Anyone has a profile corresponding to the BMS Dash-1 book ?
Thanks,
Vincent -
What the mic switch is labeled as doesnât matter, itâs left and right instead of IFF in and out (or the reverse, I forget)
I was recently going through exactly what you are, here is what got me working 100%.
You have to use the Warthog_DX.key file or whatever it is called that comes with Morphineâs profile, or adjust your own keyfile to match its assignments.
You have to verify your DX assignments. The stick has to be device 1 and the throttle has to be device 2. Pedals can be whatever but I have them as device 3.
You can use the JoyIDs utility to view dx number assignments and re-assign them. I have the utility in a stack of icons on my desktop that serve as my falcon launch checklist.
So to get working:
-
Use JoyIDs to fix your assignments first. Stick 1, Throttle 2, Pedals 3.
-
Run the target script in the target script editor. You should hear some usb device plugging and unplugging sounds, and in JoyIDs the stick and throttle will vanish and Thrustmaster Combined should appear as #1
-
Launch falcon and go the controls section. Set it to use the warthog_dx keyfile.
-
Go to the avionics and flight controls pages and set them to match the screen shots supplied with the profile
-
Test everything. If itâs all working to your satisfaction, there are a couple of files in the config folder that should be set to read-only to prevent the axis assignments from getting busted if you open falcon without having run the target script. I donât remember their names offhand though, I can add them later.
-
-
Oops, you can download JoyIDs here: http://theairtacticalassaultgroup.com/forum/showthread.php?t=13009
-
Hi,
I also have so much problems to configure BMS with the Warthog.
In BMS, if I use the BMS.key, I canât program the datalink, and if I use Keystroke.key, I canât program the NWS ! In the both cases, I canât program the MRM/DF Override Cancel function.
Yes, it is so ****ing complicated. I donât know know how many hours I spend trying to program correctly my Warthog already;
Thanks to Morphine for the profile, but some functions show on the BMS Dash-1 pages 26-27 and pages 51-52 are not on the profile (IFF instead of Datalink on the throttle for example). And I have no idea how to program the Warthod with a script (I tried already, but I donât understand anything about it).
Anyone has a profile corresponding to the BMS Dash-1 book ?
Thanks,
VincentYou need to program some/many of the functions using a direct in game method not the Target âvirtual keyboardâ it just wont work.
These will be controls like Missile step/NWS com sw & TMS, anything that has advanced functionality.
I use a modified keystroke I carried over from AF, and have continued to move much over to DX utilization. -
Hi,
I also have so much problems to configure BMS with the Warthog.
In BMS, if I use the BMS.key, I canât program the datalink, and if I use Keystroke.key, I canât program the NWS ! In the both cases, I canât program the MRM/DF Override Cancel function.
Yes, it is so ****ing complicated. I donât know know how many hours I spend trying to program correctly my Warthog already;
Thanks to Morphine for the profile, but some functions show on the BMS Dash-1 pages 26-27 and pages 51-52 are not on the profile (IFF instead of Datalink on the throttle for example). And I have no idea how to program the Warthod with a script (I tried already, but I donât understand anything about it).
Anyone has a profile corresponding to the BMS Dash-1 book ?
Thanks,
VincentFirst thing I notice is using BMS.key or keystroke.key. What you really want is Vctpil.key. The default .key files are like huge reference books like a dictionary or encyclopedia. In the end you want a personal diary, a key file that belongs to you and only you. It wonât have to be the 1000+ lines (mine is <150 lines) of the reference .key files and you can label commands to your preference. Second is that .key files are as personal as the people who wrote them and BMS.key and keystroke.key are no exceptions. The exact same callback will have different text labels in different key files. âIFF Outâ and âComm Switch Leftâ are both the exact same function with different names. âMissile stepâ and âNose wheel steeringâ are the same thing too. To even further complicate matters there are even callbacks which are functional duplicates of each other due to the development history of BMS.
Youâre not going to find a TARGET script that does the default keyboard keystrokes emulated or if you do find one, you wonât like it. The default keyboard commands use all manner of shift this and ctrl that which would easily conflict. With TARGET scripting being so powerful that itâs a shame to throw away that amazing potential to make the control link between the physical controls and the game engine as direct, robust, and natural as it can be. What you want out of a TARGET script is the best outputs possible as if you had the perfect joystick controller before you make the first control setting.
My suggested arrangement is to run the Throttle controller through TARGET and leave the Joystick controller as a ânakedâ device. The reason is due to the 8-axis, 32-button limit for DirectX so you can get the maximum out of the throttle controller. When you enter the BMS setup screen, the controller you select from the drop down menu is the primary controller. This must be the controller that has your pitch-bank axes on it. The other functions like throttle and rudder wonât work at this stage. Donât worry about it! They will work in this summary display after they are configured in the advanced tab. Do not change the controller in this drop down menu in an attempt to get the rudder and throttle working.
Before you begin binding anything, load up BMS.key and then save it as a new filename, Vctpil.key for example. From now on only work on Vctpil.key. Let BMS.key be a backup reference file. Feel free to open Vctpil.key in Notepad.exe and delete entire lines and rename text labels (between quote marks). Itâs your key file and butcher, edit, screw up, repair it all you want. I recommend deleting lines you know youâll never do anything but click on in the 3D cockpit. Be brutal, you can always add them back in later if you make a mistake. Itâs a lot easier to work on a .key file thatâs shorter. Another tip is every time you save your .key file, increment the number at the end Vctpil2 Vctpil3 Vctpil4, etc. This way if you screw up you can revert to the last version that worked. It also helps you verify that youâre using the latest edit.
OK, so bind the joystick. Find the line entry for trigger first detent, highlight to blue, and then press the trigger slightly to bind it. Repeat for fire gun, weapon pickle, missile step, CMS left-right-up-down, etc. You can test each function by pressing the button and the text label for that command will appear at the bottom.
-
First thing I notice is using BMS.key or keystroke.key. What you really want is Vctpil.key. The default .key files are like huge reference books like a dictionary or encyclopedia. In the end you want a personal diary, a key file that belongs to you and only you. It wonât have to be the 1000+ lines (mine is <150 lines) of the reference .key files and you can label commands to your preference. Second is that .key files are as personal as the people who wrote them and BMS.key and keystroke.key are no exceptions. The exact same callback will have different text labels in different key files. âIFF Outâ and âComm Switch Leftâ are both the exact same function with different names. âMissile stepâ and âNose wheel steeringâ are the same thing too. To even further complicate matters there are even callbacks which are functional duplicates of each other due to the development history of BMS.
Youâre not going to find a TARGET script that does the default keyboard keystrokes emulated or if you do find one, you wonât like it. The default keyboard commands use all manner of shift this and ctrl that which would easily conflict. With TARGET scripting being so powerful that itâs a shame to throw away that amazing potential to make the control link between the physical controls and the game engine as direct, robust, and natural as it can be. What you want out of a TARGET script is the best outputs possible as if you had the perfect joystick controller before you make the first control setting.
My suggested arrangement is to run the Throttle controller through TARGET and leave the Joystick controller as a ânakedâ device. The reason is due to the 8-axis, 32-button limit for DirectX so you can get the maximum out of the throttle controller. When you enter the BMS setup screen, the controller you select from the drop down menu is the primary controller. This must be the controller that has your pitch-bank axes on it. The other functions like throttle and rudder wonât work at this stage. Donât worry about it! They will work in this summary display after they are configured in the advanced tab. Do not change the controller in this drop down menu in an attempt to get the rudder and throttle working.
Before you begin binding anything, load up BMS.key and then save it as a new filename, Vctpil.key for example. From now on only work on Vctpil.key. Let BMS.key be a backup reference file. Feel free to open Vctpil.key in Notepad.exe and delete entire lines and rename text labels (between quote marks). Itâs your key file and butcher, edit, screw up, repair it all you want. I recommend deleting lines you know youâll never do anything but click on in the 3D cockpit. Be brutal, you can always add them back in later if you make a mistake. Itâs a lot easier to work on a .key file thatâs shorter. Another tip is every time you save your .key file, increment the number at the end Vctpil2 Vctpil3 Vctpil4, etc. This way if you screw up you can revert to the last version that worked. It also helps you verify that youâre using the latest edit.
OK, so bind the joystick. Find the line entry for trigger first detent, highlight to blue, and then press the trigger slightly to bind it. Repeat for fire gun, weapon pickle, missile step, CMS left-right-up-down, etc. You can test each function by pressing the button and the text label for that command will appear at the bottom.
I think the reason Morphineâs profile combines the stick and throttle into a virtual controller is so that you can pinkie-shift items that are on the throttle. Can you still do that if they are two separate devices?
-
Pinky shift using TARGET or SimHotasPinkyShift? I honestly donât know if you can use the naked controllerâs input into your TARGET script or not so Iâll say no with a question mark for the first one. For SimHotasPinkyShift, absolutely.
But honestly a TM WH has more buttonâs than Allah has beard. What in Vishnuâs name would anyone be doing adding a shift layer to a TM WH in the first place?
-
I think the reason Morphineâs profile combines the stick and throttle into a virtual controller is so that you can pinkie-shift items that are on the throttle. Can you still do that if they are two separate devices?
Yes you can still use the Pinky Shift to a second device if you set them up as separate controllers. Itâs all controlled in the key file.
The reason I combined them on the original version was that I thought I might need to use some of the deadzone and curve control capabilities that TARGET has. Also, since I was using Duncâs profile as a starting point it made it easier to make the conversion as the Cougar was also seen as one device by Windows as well.
However, Iâve also now converted my profile and keep the devices separate by only using TARGET to control the Throttle (for my Idle Cutoff code, etc.) and leave the Joystick as a pure DX device controlled by the key file.
-
You can use the âhardware deadzoneâ features or simply calibrate the the deadzones using DirectX (I used DXTweak2.exe as a poweruser type calibration editor).
-
However, Iâve also now converted my profile and keep the devices separate by only using TARGET to control the Throttle (for my Idle Cutoff code, etc.) and leave the Joystick as a pure DX device controlled by the key file.
Interesting. What is the advantages to the new profile and would you mind sharing?
-
I can think of one advantage, it will work with the FCC base for the stick that Iâve been eyeingâŚ
-
Interesting. What is the advantages to the new profile and would you mind sharing?
I made it because I was making a Helios profile and I decided to try an all DX profile (for the reasons many have described) and I wanted to try and develop something using Kolbeâs key file. Iâve attached a zip file with the TARGET .tmc file and BMS .key file. Since I was using Helios, the Thrustmaster MFDâs are not mapped to DX buttons as they are in my other profile. If you use the TM MFDâs you could copy and paste the other code out of Warthog-DX.key but you will have to adjust the DX numbers depending on how Windows orders your joysticks. In fact, this profile has the Throttle (called Thrustmaster Combined once the script is running) as Device #1 and the Joystick is numbered Device #2 so you may also have to adjust the DX numbers in the key file if your version of Windows doesnât order them that way as well.
I donât have any other pictures or documentation to share but it is very similar to my other profile with one difference is that TrackIR center (shift F12) is on the Throttle (push the Mic switch). If you can read the key file everything else will be obvious.
I canât really offer a lot of support right now as Iâm on a flying hiatus with the birth of our child.
Good luck.
EDIT: One other tip is that you must make the Joystick, and not the Thrustmaster Combined (throttle), your primary controller in BMS.
-
Thanks Morphine. No worries about support, Iâll work through it and since I have your earlier profile working well I can use that until I figure it out.
Congratulations on your baby.
Regards
-
where in the heck do i find the TARGET script editor?
-
Mine is default at C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETScriptEditor.exe
-
Should be buried in the start menu somewhere after installing target, which you can download from thrustmasters website.