SGT Coyle

For the Hornet: Controls Gear_Handle_UP, Launch_Bar_Control_Switch_EXTEND_RETRACT, Gear_Handle_DOWN, Arresting_Hook_Handle_Up, and Arresting_Hook_Handle_Down. Also set up Catapult_Hook_Up to be activated by the L/G Warning Silence Button when the Launch Bar is in the down position. .tmc code f/ F18: F18 function .tmh Mapping for Catapult_Hook_Up //Landing Gear Button MapKeyIO(&Throttle,LDGH, EXEC("Cat_Hookup();"), FCS_BIT_Switch);For the F5E-3: Controls Landing_Gear_Lever_LG_UP, Landing_Gear_Lever_LG_DOWN, and Drag_Chute_T_Handle_PULL_PUSH. .tmc code for F5E F5E Functions

Welcome to the jungle. Life will not be the same. I assume that the cable is "Hard Wired". That being the case, I would start by opening it up to see whats under the hood. That, I also assume, will destroy your warranty. If you go under the hood route, I would look at wiring a longer cable to controller and splicing it to the other, for starters. See if it works. Maybe look into a set of connectors that will allow you to do a more permanent job. I would also think about soldering skills. Most of these wire in the cables are very thin for wire nuts. But, actually I think you bought the wrong controller. The fact that you here tells me your ready to go a step further with a better setup. I don't know your financial situation, but maybe save up for it. This sort of thing can get expensive. Good luck. If you do go the under the hood route. Post photos. We might have use full suggestions.

Here: https://forums.eagle.ru/showthread.php?t=171098

If your using the TARGET Script Editor, the following code section works perfectly for Flaps: //Flap MapKey(&Throttle,FLAPU, PULSE + FLAP_Switch_Up); MapKey(&Throttle,FLAPM, PULSE + FLAP_Switch_HALF); MapKey(&Throttle,FLAPD, PULSE + FLAP_Switch_FULL); If your having issues with setting up a script I've attached a script template I use as a first step when setting up controls for a new mod. All the physical buttons are listed in the form of a "MapKey" command. Every line is commented out and missing a "keyboard" command, but once you provide that "keyboard" command, all that's necessary is for you to uncomment the line. The axis are already set to work. I all so provided a Macro file that that has all the default Keyboard commands in game. So setting up a MapKey command is no harder than cut and paste the maco into you MapKey command. I can't disagree stronger, that the GUI is easier than the Script Editor. With a template .tmc and a macro built with https://www.digitalcombatsimulator.com/en/files/1730806/, you can be up and flying in an hour, and have a better understanding of how things are setup. I gotta go to work. If you have issues using TARGET, post here or PM me. Good luck hope to count you as a TARGET user.

The targetdx128.tmh that I use is his. Version 1.0. A classic.

e22et, So the definesdx128.tmh you sent me was named definesdx128.tmh.txt. That won't work. lose the .txt off the end. Your .tmc is incomplete. you don't have any axis assignments, but the profile launches. So you don't need to do anything to your game files. If you have, fix it. Attached is a new .tmc, a macrofile, and the "targetdx128.tmh" that I use. I only mapped the "Electric Power Switch" to the "APU START" switch on the WH. If you want to use the .tnc, you'll have to map the rest. One thing I noticed in your script is the lack of "PULSE" commands. You should use "PULSE+" for all toggle type switches on the WH. That way you can flip a switch to a position and it will pulse the command instead of holding it. Another thing. I haven't messed with the Flamming Cliff planes much. There may be an issue with TM Virtual Controller. In the setting panel both Throttle and Stick controllers are present as well as the Virtual controller. Maybe someone else can shed light on that. I hope this helps. Su33.zip

The .zip didn't include your definesdx128.tmh file.

They'll do that until you articulate the axis'. Even then you may have a degree of shakiness around the center. That's easily remedied with addition of a small dead zone.

Post your .tmc file.

I tend to follow the simulated HOTAS layout as close as possible for starters. I guess it follows, what controllers are you using? I'm using the TMWH with Left and Right MFDs, TPR rudders, and F18 attachment.

Me too. This is awesome!

What VR headset you got? What version of game, Release or OB ?

You can paste these into an TARGET Editor script //Trigger MapKey(&JoystickF18,TG1, ); MapKey(&JoystickF18,TG2, ); //Buttons MapKey(&JoystickF18, S1, ); //Recce Button MapKey(&JoystickF18, S2, ); MapKey(&JoystickF18,S3, ); MapKey(&JoystickF18,S4, ); //VR |:| Black Rocker and Push MapKey(&JoystickF18,H3U, ); MapKey(&JoystickF18,H3D, ); MapKey(&JoystickF18,H3P, ); //SSS :: Sensor Select Switch MapKey(&JoystickF18,H2U, ); MapKey(&JoystickF18,H2D, ); MapKey(&JoystickF18,H2R, ); MapKey(&JoystickF18,H2L, ); MapKey(&JoystickF18,H2P, ); //WSS = Weapon Select Switch MapKey(&JoystickF18,H4U, ); MapKey(&JoystickF18,H4D, ); MapKey(&JoystickF18,H4R, ); MapKey(&JoystickF18,H4L, ); MapKey(&JoystickF18,H4P, ); //Trim MapKeyIO(&JoystickF18,H1U, ); MapKeyIO(&JoystickF18,H1D, ); MapKeyIO(&JoystickF18,H1R, ); MapKeyIO(&JoystickF18,H1L, );

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