We re talking about the Warthog throttle. This piece of code is to be added to a TARGET (thrustmaster’s software) script.

@Bertuz:

I also use a base Dunc_DX profile, but changed the trim function. Now i don’t have to use the pinkyswitch, because I use TrackIR to look arround. I find trimming much more usable when i don’t have to pinky-shift.

Check this post for switching trim/look around. https://www.benchmarksims.org/forum/showthread.php?8301-Dunc-s-cougar-profile-Changing-the-default-POV-settings-to-Trim&highlight=dunc+trim

Thanks Bertuz, I’ll give it a go!

Uwe

That’s not the range knob.

The callbacks are SimRangeKnobDown, SimRangeKnobUp. What keys do or don’t trigger those callbacks are between you and your .key file. If you’re struggling to get those complex key combinations to work, try making them different keys without modifiers.

My range knob is a key-driven axis (up and down on the MIC hat). Example below:
//Range Knob
MapKey(&Throttle, MSU, AXIS(DX_YROT_AXIS,-200,10));
MapKey(&Throttle, MSD, AXIS(DX_YROT_AXIS, 200,10));

No doubt. I never considered them that similar and I knew I was in for a treat on the BMS F16 after watching a few videos. I just have to stay on my toes since I’m still spending a lot of time with several aircraft in DCS while also trying to learn this one.

@Gearbox:

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.

Most likely but……

Every thing else is mechanical

Find the cables that originate at the pots and use a multimeter to test the changing impedance as you move the throttle. They are most likely HALL sensors and you may not have the equipment or experience to determine their performance, but as you did say you lost both left and right at the same time I would hazard a guess their OK.

Good luck you will need it.

Hello,
I got my own, pretty deep Warthog profile, with functions and all. Found in the threads below.

I am now thinking of restructuring my programming to have abstract F-16 (and for the throttle McBoeing (F-18)) function definitions, and define the actual Falcon4 (or other sim) dependency through a Thrustmaster .TTM Macro definition file. If unfamiliar: TTM file includes a command name, and the actual inputs to produce the functionality. The mapping and programming is elsewhere (in the TARGET script files).

This way you could inject your own Falcon4 or other sim keyfile dependencies just by going through the TTM. Also possible DirectX adaptation of the profiles would be much easier.
It is quite a big task to go through all the input devices and function tricks I use. It would help enormously to have a file to start from.

HAS ANYONE ANY KIND OF THRUSTMASTER COUGAR OR WARTHOG OR COUGAR PACK TTM FILES READY? I could start expanding it for generic Thrustmaster F-16 gaming definition, and integrate it with my scripts.
By modifying the .TTM you could use your own keyfile, and use most any TARGET profile based on that template.

EDIT: Tip ShivArcs work is probably the closest, but I still need to look into it more.

@l3crusader:

As for the DX19 (CMS “pressed”), I use it to silence Betty whenever I’m being talked at. The VMS Inhibit switch is not far from the stick in the F-16 pit.

SimVMSOn 18 -2 -2 0x42 0x0 0 "Stick Warthog : VMS On" SimVMSOff 18 -2 -2 0 0x0 0 "Stick Warthog : VMS Off"

genius. doing this.

The other thing to consider is how bms handles key presses too. For example does it poll per game loop checking which keys are down or is it event driven generating an event on either up or down. My money would be on polling per game loop. My thought is that using keys combos involving shift,ctrl, or alt might lead to confusing key combos if two are active at once. I unmapped all key presses involving master arm and I am no longer having my weapons go to safe in the middle of a knife fight. I think it best to simply map anything that uses multiple keys to a dx button to avoid getting your buttons crossed up. Now if I can learn to have better sa and stay above ir SAMs, I will avoid a lot of embarrassing sky diving trips.

If you use the WH circuit board, will the joystick still be force sensitive or does it go back to beginning a regular WH? I assume the former as otherwise there would be no need to buy a second joystick.

Also, what are the following files used for (especially the BMS file) that are listed on the RS website?

New Firmware & HID DEV TOOLs available
MJF.FW.1.05.0 Available
LCJ.FW.1.01.0 Available
BMS.FW.1.02.0 Available

Sry for the late reply. At least for once i wanted to reply with a succes instead of a new question.
I can’t thank you guys enough for your help. Everything’s as it should now:headb:
With your permission i’d like to post it in the forum.

Regards D_Fens

Okay, the controllers are working again. Stubbies was probably right. I reloaded Morphine’s profile, restarted the sim and, voila’, everything was working. Thanks a lot to all those of you who helped. I appreciate you and this forum.

Great news! Anyone else who hits the same issue: in the GUI there is a button to view the script – if you click it you can copy and paste that into the script editor and it works perfect. Going to be adding in the new lines of codes for my range knob and will post results.

you can see in the track ir screen if there is any interference, instead of the three reflective tags (or 3 LEDs if using the pro clip), any blobs you see on the screen represent additional light interference.

ve only seen it once, when i had a highly reflective frame behind me and several lights blaring on it.

@pingp:

Hello, all masters:

I’m a newbie and have following questions:

1. I run the Morphine’s script using TARGET editor before I launch the game and load the keymap in the control configuration. Must I do it every time I start the game?
2. BMS recognize the throttle as …… rudder! help

Thank you and good hunting

Hi !

For TARGET yes, for the keymap loading no.

You need to manually assign the axis in the control page.
I used Morphine’s profile, so IIRC, its Z for throttle and Zrot for right throttle.
In the avionics tab, its Xrot and Yrot for cursors.

Be sure to see where this axis are used by default and deassign them first, otherwise you wont see it in the list.

Now : if you always plug the Warthog and launch TARGET, you wont have to reassign the axis.
BUT : if sometimes you dont do it, you will have to reassign.

To avoid that, you can go to your install folder -> User -> Config, and open “DeviceDefault.txt”
In this file, the default configuration for every device are stored. You can modify it though, and thats what we will do.

locate in the file these two adjacent lines : Thustmaster Combined ( or more or less this)

#GUID = { whatever}

Remove the # next to GUID (and this one only). If these lines are present several times, only do this once.

Then add lines under the GUID line, corresponding to your device assignations :
AXIS_PITCH = Y
AXIS_ROLL = X
Etc. Use the instructions at the top of the file.

Save, and you are done !

Hope this helps.

I would like to rotate the X/Y axis onmy stick 12 degrees outboard. I was pointed to the page 14 in this document:

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

Now, I have never used TARGET and have not intention to use it for other than maybe rotating the axis. I’m happy with the plug&play DirectX functionality and don’t want to alter that.

Can I do it? Rotate the axis but keep all the DirectX functionality? Is it difficult for someone who knows nothing about TARGET?

Can someone provide a quick “how to”? :p:roll:

Thanks!!

Tulkas

Yes, I got it from your file. I used keyboard actions though for the two callbacks, and my “activation zones” are smaller : I used LIST(0,5,95,100) instead of 3 in the first AXMAP2 argument.

Now I have a DX axis and dont know what to do with it, though :mrgreen:

Glad you got it sorted! 🙂

I’m brand new was finally able to find and install falcon 4.0 along with BMS. I also just finally figured out that T.A.R.G.E.T. is free hahaha. So I’m curious what to do with the files and run them with TARGET in order to work. I got a different profile to work, however, I really would like to try this one too! Thanks for the help!