[Target] How to bind DX_THROTTLE_AXIS to CS/CH/ or MS
-
Working on my profile now – this got me stuck. I want to make one of these my range knob, but I have no idea how to bind DX_THROTTLE_AXIS in target.
Thanks!
-
You can assign it “virtually” to two buttons.
The “Mic Switch” (ie : 4 way switch on the side of the throttle, just next to the speedbrakes switch) is, for me, both the antenna elevation knob and the range knob.
For the range knob, as the callbacks emulating it does not work properly, I did it this way :
MapKey(&Throttle, MSR, REXEC(0,50,"TrimDXAxis(DX_THROTTLE_AXIS, -64);")); //Range Knob up MapKey(&Throttle, MSL, REXEC(0,50,"TrimDXAxis(DX_THROTTLE_AXIS, 64);")); // Range Knob down
As long as you hold pressed the button (in this case, mic switch forward or back), the range axis will move forward or back.
[ BTW : this kind of “virtual” axis can be used for a lot of axis. I dont use DX axis for the cursors, for example (instead, I used DX buttons - long story).
With the 2 axis I freed, I set up differential braking : I press a button, and if my stick is on the left, I will brake more with the left brake, for example. ]
EDIT : this obviously assumes you are using a TARGET script (ie: a .tmc file, like Morphine’s). Otherwise, I am not sure you can use this DX axis.
-
I didn’t use script had no idea how to operate it and ended up doing by mapping it out with the GUI. The thing is, the GUI doesn’t let me input DX_THROTTLE_AXIS as a key so it’s been a nightmare. I’ve been following morphines and using it as a blueprint, but I need to use my keyfile so…yeah. Not sure if i can combine TARGET script + GUI?
-
I dont think so… its either one or the other.
How about starting from a .tmc profile like morphine’s, and adapt the button pressed in the file to your needs ?
If you do so, all you have to do is replace the key used in the tmc file by yours.
…
Now, after that, you feel confortable with doing some more scripting, you will need this :
http://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/TARGET_Script_Editor_Basics_v1.5_ENG.pdf -
I think that’s what I’ll have to do. Man, so much work to get to this point to start over. I still have like a good 12-15 keys I have no idea what to bind to either =/
Thanks for the help
-
That’s a little unusual code for button-axis I think? This is mine and it doesn’t use TRIM command.
//Range Knob MapKey(&Throttle, MSU, AXIS(DX_YROT_AXIS,-200,10)); MapKey(&Throttle, MSD, AXIS(DX_YROT_AXIS, 200,10));
-
That’s a little unusual code for button-axis I think? This is mine and it doesn’t use TRIM command.
//Range Knob MapKey(&Throttle, MSU, AXIS(DX_YROT_AXIS,-200,10)); MapKey(&Throttle, MSD, AXIS(DX_YROT_AXIS, 200,10));
Yep, I used exec & trim but axis works better indeed.
-
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.