Warthog HOTAS Set-Up Help Please?
-
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.
-
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.
Update: The files to set as read-only are /Falcon BMS 4.32/User/Config/axismapping.dat and joystick.cal. Remember to uncheck read-only on them if you want to make changes in the future.
-