SGT Coyle

Haven't posted in the Training Section in a while. Just wanted to say that the syllabus style of training missions is outstanding. The TPOD status apart, these are the best missions for getting to know the Harriers capabilities and the quality of the missions themselves is of the highest quality.

This is what I have for the Left and Right Idle cutoffs MapKey(&Throttle[color=#ffffff],[/color]IDLEROFF, PULSE + Throttle_Right_IDLE); MapKey(&Throttle[color=#ffffff],[/color]IDLERON, PULSE + Throttle_Right_OFF); MapKey(&Throttle[color=#ffffff],[/color]IDLELOFF, PULSE + Throttle_Left_IDLE); MapKey(&Throttle[color=#ffffff],[/color]IDLELON, PULSE + Throttle_Left_OFF); Of course you'll have to replace the Throttle bits with actual commands.

Try this: Paste this into your script. It is just the APDIS command. MapKey(&Throttle, APDIS, TEMPO( CHAIN( EXEC("Throttle[VBI]=1; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);"), LED(&Throttle,LED_ONOFF,LED_CURRENT+LED1), D(3000), EXEC("Throttle[VBI]=0; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);"), LED(&Throttle,LED_ONOFF,LED_CURRENT-LED1) ), SEQ( CHAIN( EXEC("Throttle[VBI]=1; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);"), LED(&Throttle,LED_ONOFF,LED_CURRENT+LED1) ), CHAIN( EXEC("Throttle[VBI]=0; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);"), LED(&Throttle,LED_ONOFF,LED_CURRENT-LED1) ) ), 500) );

Try this: MapKey (&Throttle, APDIS, TEMPO( CHAIN( EXEC("Throttle[VBI]=1; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);"), D(3000), EXEC("Throttle[VBI]=0; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);") ), SEQ( EXEC("Throttle[VBI]=1; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);"), EXEC("Throttle[VBI]=0; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);"), 500) ) ); It helps to format your code. Easier to see mistakes and keeps it readable. Did your code give an error or just not work?

No problem. It makes my day when people use TARGET to solve interesting problems.

OK. First things first. Everything in the code section is credited to Drakoz. Particularly the code below, that was originally posted in 3984086. Copy-n-Paste the code below into a NEW .tmc in the editor. It will do as you ask. A 3 sec toggle attached to the APDIS button on the throttle base. Test it with the Event Tester and first stage trigger [TG1]. Out state = 1 In state = 2 for 3 secs Good Hunting! include "target.tmh" // Define virtual buttons for IO Shift and UMD mode for Warthog JoystickF18 define VBI 40 // Mode I virtual button define VBU 41 // Mode U virtual button define VBD 42 // Mode D virtual button int main() { if(Init(&EventHandle)) return 1; SetShiftButton(&Throttle, VBI, &JoystickF18, VBU, VBD, 0); // IO Shift and UMD Setup (%DEV1, I button, $DEV, U, D, Toggle settings) // The line directly below is an edit to original code to provide a 3 sec delay to the Middle In Shift State. MapKey(&Throttle, APDIS, CHAIN( EXEC("Throttle[VBI]=1; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);"), D(3000), EXEC("Throttle[VBI]=0; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);") ) ); //MapKey(&Throttle, APDIS, EXEC("Throttle[VBI]=1; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);")); //MapKey(&Throttle, S2, EXEC("Throttle[VBI]=0; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);")); //MapKey(&JoystickF18, H1U, EXEC("JoystickF18[VBU]=1; DefEventHandler(EV_HID_INPUT_DATA, &JoystickF18, VBU);")); //MapKey(&JoystickF18, H1D, EXEC("JoystickF18[VBU]=0; DefEventHandler(EV_HID_INPUT_DATA, &JoystickF18, VBU);")); //MapKey(&JoystickF18, H1L, EXEC("JoystickF18[VBD]=0; DefEventHandler(EV_HID_INPUT_DATA, &JoystickF18, VBD);")); //MapKey(&JoystickF18, H1R, EXEC("JoystickF18[VBD]=1; DefEventHandler(EV_HID_INPUT_DATA, &JoystickF18, VBD);")); MapKey(&Throttle, APDIS, CHAIN( EXEC("Throttle[VBI]=1; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);"), D(3000), EXEC("Throttle[VBI]=0; DefEventHandler(EV_HID_INPUT_DATA, &Throttle, VBI);") ) ); // Test the result MapKeyIOUMD(&JoystickF18, TG1, '4', // IU '3', // OU '2', // IM '1', // OM '6', // ID '5' // OD ); } int EventHandle(int type, alias o, int x) { DefaultMapping(&o, x); }

What Module are you flying?

Can you be more specific? What do you want to do? What buttons do you have in mind? I have a couple of thoughts, but I have to look at some scripts before I go any further.

TARGET Editor layout //Trigger MapKey(&JoystickF18,TG1,); MapKey(&JoystickF18,TG2,); //Buttons MapKey(&JoystickF18,S1,); // Recce Button MapKey(&JoystickF18,S2,); // Weapon Pickle MapKey(&JoystickF18,S3,); // Pinky Button MapKey(&JoystickF18,S4,); // Pinky Lever //VR Rocker |:| MapKey(&JoystickF18,H3U,); Forward MapKey(&JoystickF18,H3D,); Aft MapKey(&JoystickF18,H3P,); Push //Seneor Select Switch :: MapKey(&JoystickF18,H2U,); MapKey(&JoystickF18,H2D,); MapKey(&JoystickF18,H2R,); MapKey(&JoystickF18,H2L,); MapKey(&JoystickF18,H2P,); // SSS Push //Weapon Select Switch = MapKey(&JoystickF18,H4U,); MapKey(&JoystickF18,H4D,); MapKey(&JoystickF18,H4R,); MapKey(&JoystickF18,H4L,); MapKey(&JoystickF18,H4P,); // Push //Trim MapKeyIO(&JoystickF18,H1U,); MapKeyIO(&JoystickF18,H1D,); MapKeyIO(&JoystickF18,H1R,); MapKeyIO(&JoystickF18,H1L,);

Check, in the Hardware Manger, the HID devices for Power management setting. I have found several controller devices with power managment active.

Can we get this moved to Thrustmaster Section?

I have Throttle , Stick, and 2 MFDs and use a custom .tmh for 120 DX buttons. Not mention the keyboard mapping that can be applied. Use this link to see how. https://forums.eagle.ru/showthread.php?t=171098

Discord is not looking for a "Button 4"(DX4) push form TMWH Throttle. It's looking for a DX4 from Windows. Discord does not differentiate controllers like DCS does. If you use TARGET, your controllers will be combined into one virtual controller and only DX4 button push could be assigned.

As Shadow_1stVFW said, it could be a setup or a desire. In my case, it's a disability. I also use Oculus, but some switches and knobs are way down low and to the back. Due to a helo crash I'm left with a limitation on how far I can articulate my neck to be able to put the cursor on a switch or knob. I really need to have a keyboard command to be able to map it to controller.

Close Thrustmaster "Fast service" from the task manager. That should close everything TARGET related. You may have to re-enable to run TARGET. Then make sure you run TARGET as admin.

After spending some time with Tech support on the phone, nicest gal I've ever had an issue with, I got the stick Drivers to update and the firmware to update. Ya! Maybe not a piece of shit!.... WTF! TPR Rudder drivers messed up. No properties window available. Firmware install fails.

There is a limit of 8 axis per controller. That's a windows thing. The good part is that the limit is for each controller. The Stick, Throttle, Rudders, MFDs (Left & Right respectfully), are all individual controllers. They are seen as individual controllers in DCS and none of these controllers have more than 8 axis by themselves. If you use TARGET software, the controllers are combined to makeup the virtual controller. DCS will see this as one controller and you will be limited to 8 axis. If you use Stick(X and Y axis), Throttle (witch has 5 axis available for mapping), and Rudder with toe brakes(X,Y and Z axis), you could run out of axis pretty quick. For the A10C a complete setup has more axis than are availible with the windows limitation. Stick 2 axis (X,Y) Throttle 5 axis (Z and RZ- Left and Right Throttles, X and Y for Slew, Slider for zoom control ) Rudder 3 axis (Z for rudder and X,Y for toe brakes) ___________________ 10 axis But all is not lost. You can modify the TARGET .tmh file to eliminate the Rudder Pedals from the virtual controller and still have them seen by DCS as an individual controller. That will leave you plenty of axis to map to stick and throttle. I think this is the trhread you were looking for: https://forums.eagle.ru/showthread.php?t=219716&page=2

It doesn't work with the TARGET Script Editor. There's no way to assign keyboard presses to buttons. Very disappointed in this release.

Just got mine and there's no TARGET button mapping. Unless I'm missing something. I tested with a simple profile and it just gives the native DX button presses. What a piece of shit.

:):):):):)This is my favorite thread.:):):):):)

Using TARGET, I assigned several views to the Trim Hat and the Button 1. For the Trim Hat I use it for all the trim functions Nose up, down, left, and right. Shifted-In layer I assign a sequence of F1, F2, F4. On a shifted-In layer I assign a sequence of F1 and F10, on Button 1. //Trim + MapKeyIO(&Joystick,H1U, SEQ( F2_Aircraft_view, F4_Chase_view, F1_Cockpit_view), Trim_Nose_Down); MapKeyIO(&Joystick,H1D, SEQ( F10_Theater_map_view, F1_Cockpit_view), Trim_Nose_Up); MapKeyIOUMD(&Joystick,H1R, Trim_Rudder_Right, Trim_Right_Wing_Down); MapKeyIOUMD(&Joystick,H1L, Trim_Rudder_Left, Trim_Left_Wing_Down); There's an example of the TARGET .tmc code I use for the Trim Hat.

Try adding a little dead zone to the center and see if it helps. There's so much stuff hanging off that aircraft I'm amazed it will trim at all.

I don't know why it was closed, but at least it was reported. Frustrated that it only took 6 months. I hope it doesn't take another six moths to get corrected.

Any more news on this OP?

Thanks for the reply. I got the axis assignments to work. The issue was not the axis assignments but some confusion as to the trigger switch operation. I'll take that to a different thread.