SGT Coyle

If you were willing to give TARGET Script Editor a try, this would solve the issue: https://forums.eagle.ru/showthread.php?t=171098

Awesome, Thanks Catseye and =Panther=

What app did you use? Link, please.

I don't use the GUI, but I looked to see, and I don't see anything to map an 8-way hat either. I did a search of the manual for "8-way" and didn't find anything.

Maybe if you say please.

I have two and I liked them before I went VR. Useless for VR, but with TrakIR, totally worth it.

I made my own controller for VR pit. Map it to the UI layer. Works like a charm.

Layers! WTF! TARGET SE gives us three layers: UP MIDDLE DOWN and two sub-layers for each: IN OUT You have to tell TARGET what layers/sub-layers you want to use and if the those layers are going to be momentary or toggled. You also need to tell TARGET what buttons or switch is going to activate witch layer/sub-layer. You do this with the "SetShiftButton" function. SetShiftButton(Device for Sub-Layer, Button Name for Sub-Layer, Device for Layer, Button Name for UP, Button Name for DOWN, Toggle Indicator); As with "MapKey", you need to tell "SetShiftButton" what device your going to map an activating button to, and what button it is going to be. Example: SetShiftButton(&Joystick, S4, &Throttle, PSF, PSB); Sub-layer is Pinky Lever on the Stick. Pinky Switch Forward is UP layer and Pinky Switch Back is the DOWN layer, on the Throttle. All the these activations are momentary since we didn't declare any Toggle instructions. Look at pages 21 and 22 in the manual for more examples. To make a "MapKey" assignment you need to tell "MapKey" that you want to access the Layers and/or Sub-Layers. You don't have to use layers or sub-layers in your "MapKey". Any instructions in "MapKey" will default to the MIDDLE / OUT layer, if you don't tell it otherwise. So here's a scenario where I use the Trim Hat to trim the A/C. I assign all six trim functions to the four way hat using the Sub-Layer of the default MIDDLE layer. MapKey(&Joystick,H1U, Nose_Down); MapKey(&Joystick,H1D, Nose_Up); MapKeyIO(&Joystick,H1R, Rudder_Right, Right_Wing_Down); MapKeyIO(&Joystick,H1L, Rudder_Left, Left_Wing_Down); IO added to the end of the "MapKey" function tells TARGET the TRIM Hat Left/Right buttons have Sub-Layer assignments available, but the TRIM Hat Up/Down buttons do not. Furthermore the Sub-Layer functions are only active while I hold the Pinky lever on the stick in, since I didn't give any toggle instructions. Momentary by default. Now for a more complicated scenario also using the TRIM Hat button. First the example then the explanation. MapKeyUMD(&Joystick,H1U, F1_Cockpit_view, Nose_Down, Cockpit_Camera_Move_Up); MapKeyUMD(&Joystick, H1D, 0, Nose_Up, Cockpit_Camera_Move_Down); MapKeyIOUMD(&Joystick,H1R, 0, F4_Chase_view, Rudder_Right, Right_Wing_Down, 0, F3_Fly_By_view); MapKey(&Joystick,H1L, Left_Wing_Down); First line "MapKeyUMD(&Joystick,H1U, Up layer Cockpit View, Middle layer Nose_Down, Down layer Cockpit_Camera_Move_Up);" MapKeyUMD tells the MapKey function that there is are UP, MIDDLE, and DOWN layer assignments in the function. Second line is the same with exception of 0 in the UP layer position. A 0(zero) in a variable position will result in nothing. Nothing will be passed when in the UP layer and press H1 down. Third line "MapKeyIOUMD(&Joystick,H1R, UP layer with sub-layer active, UP layer no sub-layer, MIDDLE layer sub-layer active, Middle layer no sub-layer, DOWN layer sub-layer active, DOWN layer no sub-layer active);" As you can probably tell. When using Layers, the code can get rather messy and hard to read. Adding a little formatting to the text can make things much more clear: MapKeyIOUMD(&Joystick,H1R, UP layer IN, UP layer OUT, MIDDLE layer IN, MIDDLE layer OUT, DOWN layer IN, DOWN layer OUT); Fourth line is a standard single button assignment. No layers or sub-layers assignment in the function. As you can see there are number of ways to interact with layers to multiple functions in a single button. I hope this made sense.

It's a nine+ year old product. I don't think there's going to be a redesign any time soon. I find the stiction problem is nonexistent with a 19" extension installed. My stick base is bolted to floor. The mini stick issue ,IMO, is blown out of proportion, but I replaced it with the mod and I do see an improved product. I kept my mini stick to add to a controller project I'm thinking about, and I expect it will work fine. I think both the stick and throttle are great products. I would love to see a new stick WH base with the Ball being replaced by a mechanical cam, but I don't see it happening. I don't even know if there making any new WHs. I think one of the most impressive features, if not controversial, is the TARGET Script Editor. There is a lot of things you can do with it, but it takes time to learn. I hope this helps. I do think it's a great product, not perfect, but TM definitely saw a market not being served nearly a decade ago and served it.

If your using TARGET Script Editor: In the TSE add the bold text to your .tmc just after the EventHandle line. [color=#1e90ff][b]if[/b][/color][color=#ffffff]([/color]Init(&EventHandle)) [color=#1e90ff][b]return[/b][/color] [color=#ffffff]1[/color]; [color=#32cd32]// declare the event handler, return on error[/color] [b]Configure(&Joystick, MODE_EXCLUDED);[/b]

Especially when 90% of the threads about key bindings have ready baked solution in the thread. Low hanging fruit is so easy to pick. Not as if a major overhaul is in order.

Glad you got it sorted. I'll pass on crashing editor. LOL!

Check to see if TmWinService and tmAInstall are in services tab in Task Manager

Peedee, never use windows to calibrate stick or throttle. You can use it to see if buttons are working, but do not calibrate with windows. It breaks things. Welcome to the club.

Post your script.

You need to install drivers and I think the software is automatic, but you don't need to use it.

Thanks.

Once you learn TARGET you never go back Thanks

Let's get scripting. A couple Rules to remember: MapKey(&Joystick, S1, Expand_FOV_Button_Depress); "MapKey" is a function to make a button do something. There are other functions, but "MapKey" is the topic today. Every function has variables between "( )". For every one of these "(", you need one of these ")". Variables are separated by",". Every function line needs ";" at the end. Making buttons do things on the stick. To map keyboard presses, DirectX Commands, or other functions to the buttons on the joystick, you use the "MapKey" function. What you need for a MapKey function: Function Name ( Device Name, Button Name, Key or Command to be passed); Function Name = MapKey Device Name = TSE designation for the TM Device you want to map proceded by "&". i.e. &Joystick = Standard TMWH Joystick Grip. Button Name = Name of the button or switch you want to map. Button names can be found on the Device diagram located in documents folder in the TMSE directory Key to be mapped = keyboard key to mapped between " ' ' " (single quotes). The template in the OP breaks down the joystick mapping options by button name (Triggers, Buttons, TMS Hat, DMS Hat, TRIM Hat, and CMS Hat). The individual sections are further broken down into commented out MapKey functions for the each button in the section. Example: //TMS // Hat Name on the Stick //MapKey(&Joystick,H2U, 0); // Device Name //MapKey(&Joystick,H2D, 0); // Actual button on the Hat to be mapped //MapKey(&Joystick,H2R, 0); // Zero passed w/ no quotation to produce "nothing" //MapKey(&Joystick,H2L, 'c'); //C in single quotes to passed to DCS as key press[ This is what it looks like with my macros form the Macro.ttm //TMS MapKey(&Joystick,H2U, Target_Management_Switch_Up); MapKey(&Joystick,H2D, Target_Management_Switch_Down); MapKey(&Joystick,H2R, Target_Management_Switch_Right); MapKey(&Joystick,H2L, Target_Management_Switch_Left); Macros don't need single quotes and are easier to read. Go read pgs 15 and 16 in the manual. Hope this helps.

Could you post the TM part#s for us.

Your looking for Clockwise (CW) and Counter Clockwise (CCW) keyboard support for encoders and rotary switches, aren't you? Put it in a bug report, if it isn't already reported.

If you can get the keycap off. try compressed air. Or, take the top plate off. 4 screws at top of switch.

Are you saying that it is physically sticks in the right position? Or that even though it returns to the center it continues to command right camera slew?

That is correct. I added that line and the one below for the F18 Grip. If you don't need the throttle just copy the line and replace &Joystick with &Throttle.

I totally agree. I would also say that a timely response, not resolution, to bug reports would be greatly appreciated. Along with a tag on the title that it's been [REPORTED], or other appropriate status, would go a long way.