@AV8R:

Make sure youre getting what you expect…

They selling just the stick or throttle
…OR…
The stick and throttle

Both. I’m not buying, just pointing it out to any prospective UK buyers 🙂

EDIT: The OP is pointless now anyway. Price is back up to £292, but hey, at least now they have stock… typical!

@Terminator:

Good point of course, although I read some people on this forum telling they can use all switches on the Warthog throttle without Target. I never understood how that’s supposed to work. I use DX if possible and Target for the switches left over. Never had problems at my end. Still need to expand the DX bindings though, I’m not using any DX binding with release modifier yet. But like I said, everything works fine, so I am not in a big hurry to change it

.

There are threads here on this topic…

It’s tied to the facts that the WartHog has two POV hats (one on the stick and another on the throttle) and that in BMS only the “primary” controller we choose can which have the X-Y axes can also have the POV. While this is fine for the Cougar stick and throttle setup as DX devices, it does create problems for the WartHog controller setup. Hence why the workarounds are to use TARGET and its one virtual controller capability, or to use the WartHog’s POV as DX 4-way switch functions and not as a second X-Y POV hat.

1. CURSOR Enable just “pings” and does not switch the mode as in the MFD. I have it set-up as pulse
2. The speed breaks I have set up with DX and use the short-cut keys. What happens were is that the breaks are either fully open or fully closed, and I cannot set them where I want (even though it works fine when using the open/close keyboard strikes on the keyboard
3. I want the FOV switch as a dual function. Hold to act as shift and short press to act as FOV on FCR
Send from my Xperia X using Tapatalk

BMS code has programming for some of its controller functions that already have dual use and press/hold timing built in, like the TWS/RCS modes on the FSS TMS hat. So pre-programmed functions like these are not good choices to also assign user defined hold and/or delay parameters to within TARGET. Rather those that are regular toggles, switches and axes that are not already pre-programmed, are fine to add hold/delay parameters to.

BMS is not the only flight sim that automatically assigns axes and DX buttons to connected devices. Can lead to much angst, as you discovered. Glad you got it sorted.

@Shadow:

As clear as mud,

Hey, don’t talk about Mud, he’s my Squad Mate!!!

You Heathen!!! 😛

C9

It does work indeed!

Theres actually two BMS device files:

DEVICESORTING: reflects the devices as Windows assigns them to GUIDs and can be checked in then Windows controller panel. This is also what shows up in the BMS Controls device pulldown menu. DEVICEDEFAULTS: defines the flight axes for each controller as selected in the BMS Controls assignment pages, and maps the device name back to the Windows IDs.

The point of these files was to maintain the axes assignments within the BMS Controls pages even if the Usb ordering changes as devices are unplugged or moved to different ports. Sometimes it still gets out of sync and you either make the fixes manually in the files if you understand them, replace them from a backup, or delete them and they will be regenerated. In which case you have to reassign the axes again within BMS.

@KrazySwede:

I’m a little late to the party but did you find the latest version of the profile? I just got my Warthog working with 4.33 U2 using the files from here via reddit.

THANK YOU for this tip, it fixed my issue. I had the combined controller created by TARGET (I think that’s how it works) sorted last which was causing issues with assigments (DMS was showing assigned to OSB keys in BMS. After moving “Thrustmaster Virtual Game Controller (root)” to the top of DeviceSorting.txt, Morphine’s profile is working as intended with my Warthog in 4.33 U2. Thanks!

Hey I created that profile. It had some issue, so I created a new version. I also made a version of the script to account for the new version of the thrustmaster pedals. Tpedals was added to the script title to differante it from the original. It can be downloaded from the link below.

https://www.dropbox.com/sh/4l2j2sbbkkmwoaa/AAAMks8YYDvUsOQ6vr7bi5bia?dl=0

Okay here is a keyfile for HOTAS WARTHOG both Joystick&Throttle.
Copy them to the last line of any .key file in User/Config

Make sure in DeviceSorting.txt Joystick as 1st and throttle as 2nd device.
Also set “Enable Dogfight/Missile Override Self-Cancel” from Config(launcher).

SimTriggerFirstDetent 0 8 -2 0 0x0 0 SimPickle 1 8 -2 0 0x0 0 SimPinkySwitch 2 8 -2 0 0x0 0 SimAPOverride 3 8 -2 0 0x0 0 SimMissileStep 4 8 -2 0 0x0 0 SimTriggerSecondDetent 5 8 -2 0 0x0 0 SimTMSUp 6 8 -2 0 0x0 0 SimTMSRight 7 8 -2 0 0x0 0 SimTMSDown 8 8 -2 0 0x0 0 SimTMSLeft 9 8 -2 0 0x0 0 SimDMSUp 10 8 -2 0 0x0 0 SimDMSRight 11 8 -2 0 0x0 0 SimDMSDown 12 8 -2 0 0x0 0 SimDMSLeft 13 8 -2 0 0x0 0 SimCMSUp 14 8 -2 0 0x0 0 SimCMSRight 15 8 -2 0 0x0 0 SimCMSDown 16 8 -2 0 0x0 0 SimCmsLeft 17 8 -2 0 0x0 0 SimCursorEnable 18 8 -2 0 0x0 0 SimTransmitCom2 19 8 -2 0 0x0 0 SimTransmitCom1 20 8 -2 0 0x0 0 SimCommsSwitchRight 21 8 -2 0 0x0 0 SimCommsSwitchLeft 22 8 -2 0 0x0 0 SimToggleMissileCage 23 8 -2 0 0x0 0 SimSelectSRMOverride 24 8 -2 0 0x0 0 SimSelectMRMOverride 25 8 -2 0 0x0 0 AFBrakesOut 26 8 -2 0 0x0 0 AFBrakesIn 27 8 -2 0 0x0 0 SimCursorEnable 32 8 -2 0 0x0 -1 SimTransmitCom1 34 8 -2 0 0x0 -1 SimCommsSwitchLeft 35 8 -2 0 0x0 -1 SimTransmitCom2 36 8 -2 0 0x0 -1 SimCommsSwitchRight 37 8 -2 0 0x0 -1 AFBrakesIn 38 8 -2 0 0x0 -1 AFBrakesOut 39 8 -2 0 0x0 -1 SimSelectMRMOverride 40 8 -2 0 0x0 -1 SimSelectSRMOverride 41 8 -2 0 0x0 -1 SimRangeKnobUp 42 8 -2 0 0x0 -1 SimRangeKnobDown 43 8 -2 0 0x0 -1 SimToggleMissileCage 46 8 -2 0 0x0 -1 AFElevatorTrimUp 0 -1 -3 0 0x0 -1 AFAileronTrimRight 0 -1 -3 2 0x0 -1 AFElevatorTrimDown 0 -1 -3 4 0x0 -1 AFAileronTrimLeft 0 -1 -3 6 0x0 -1

FCF is created by the target GUI and the tmc script is the base code for assigning key functions to the joystick. The tmc can be created by the script editor or any other code editor like Notepad ++ or Sublime. The GUI will generate what is in essence a TMC along with some other files. The TMC is closer to programing bare metal. Both the GUI and script editor can generate profiles but the tmc files are typically smaller. Either approach is a perfectly valid means of creating a profile, use what you find most effective.

The syntax of the target script is as follows: lets look at an example from morphine’s script.

MapKey(&Throttle, BSF, PULSE+‘m’)

First we’re calling the map key function, (MapKey) then were mapping a key on our throttle (&Throttle), in this case when we hit boat switch forward (BSF) we are going to hit the m key once (Pulse+‘m’)

This syntax is the basis for all the functions in the script. Though we may have different functions ie MapAxis to change the proprieties of an physical joystick axis. More detail is provided in the target script manual, a link for which I will provide below. A good way to learn Target script and the BMS keyfile, is to edit the keys assigned to various buttons in the target script and then edit the key file to keep the function the same. I.E change the boat switch from M to say Z. Then edit the BMS key file so that Z is missile mode. You’ll want to spend some time with BMS key file manual, located in BMS docs folder, to learn that syntax.

You don’t necessarily have to learn target script to create a profile for BMS, as using the GUI is a perfectly acceptable means to do so. Though it is a good idea to learn the BMS key file, though a editor for that is included in you’re install, it’s a spreadsheet file that will generate a key file.

Link to target manual:
http://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/TARGET_Script_Editor_Basics_v1.5_ENG.pdf

It’s because the iddle cutoff position is not axis but it’s kinda button, you can program it in TARGET as “alt+I” for iddle off position, for iddle on position you have to set some delay (about 3 secs). This works fine for me.

You could use the GUI for most of your profile then just “write” the stuff that the GUI can’t sort out for you…. but as soon as you do that, you’ll see how “dirty” or messy the GUI “writes” the code and if you’re even a little OCD, you’d want to clean the code up yourself.

It’s not difficult to code… just read the manuals and just try to code what you want for now. Once you got that working, you can then just copy-paste it to your GUI-code and then pretend you’ve never noticed how messy the rest of your profile was… 😄

HI Weaklink,

You might be right yes. I Will check for sure. If I found something I will let you know. So far the good news is that the autopilot keeps working.

I have tried using the Thrustmaster TARGET software and have been somewhat successful in controlling the nozzle, but I can’t get full range and when I return the nozzle it doesn’t go all the way back. Will post a Youtube vid showing what I mean later …

Lawrence - This profile works well in 4.33U1. Been having some issues with other TARGET setups with a a .tmc extension. This has the .fcf extension and it’ll be much easier to modify, f needed. I’ve even got the Thrustmaster MFD’s tucked away in a closet somewhere - I’ll pull them out and use them as they are already in your profile. Great job, thanks for sharing.

Sorry, sorted this out. Never noticed there was a avionics tab.

@Macman:

Hoover - I tried yesterday to use the joystick independently and not use Target - Falcon did not recognize that I had a joystick connected. Everything was in keyboard mode only. I’ll check into it more this weekend as I feel like I’m taking a somewhat helter-skelter approach to my setup, you know, try this, try that, etc… Sub101 - if you could send me your profile and keyfile, that would be a much appreciated head start for me.

pm me with an e-mail address and I will send it straight away.

You have to set the controller in the main dropdown menu to your joystick which controls pitch and bank. This is mandatory. Try to choose anything and then go to the axis section and notice that you have no choice which controller is set to pitch and bank.

The fact that your device order is keyboard, Saitek Rudder Pedals, Thrustmaster means I know for a fact that your trigger on your joystick is Button #33. That is because that is the first button on the second controller. What you must do to get the Thrustmaster Combined controller as the first controller. Then trigger will be Button #1 and not Button #33 and everything will be fine.

Go into your devicesorting.txt and delete all lines that aren’t the rudder pedals and thrustmaster controllers. Edit the file so that the top line is the Thrustmaster and the second line is the Saitek pedals.

When that is done your drop down menu will be Keyboard, Thrustmaster, Saitek in that order.

B2Blain, have you tried using the Excel .key file editor found on the docs folder of th BMS install?
This is what I use all the time to map all of my buttons. I have the Saitek X52 and I do not use the software that came with the stick. I use the Excel editor to map all the buttons using DX.
On August 20th Saturday, my new Warthog Trustmaster will arrive. I intend to use the same .key file for two reasons, first I use a touch screen with the Helios software (I’ll tell you about that later) second because I don’t want to change my keyboard shortcuts. I already looked at the file and the Warthog set up seems prety stright forward. I can see I will be able to use shifted key conbinations practically doubling the amount of key available on the HOTAS.
As I understand, most people abandon the softaware that comes with their sticks and prefer to use DX assigment instead because the software tends to have unintended consequenses and the additional software needed to translate the callbacks to BMS.
With DX assigments is only Windows and BMS talking to each other.
I’ll let you know how it goes.
Pika

I’ve been using Mud’s profile but made subtle changes for my own requirements and I think it is an excellent profile.

But as you’ve used Morphine’s for a long time, you are probably most familiar with his (great) profile - there probably isn’t a compelling reason to change.

I’m pretty sure you can enable line numbers on all lines in the settings / options.