SGT Coyle

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.

It might be worth putting little instructions like these in the "tool tips".

It's always been Left Click and drag for encoders. At least since A10C. I find it funny how these things find their way to getting released.

GIUK Line. Gotta keep those russkies bottled up. No offense.

Thanks, I was expecting some long combination name, i.e. Man_Rng_Knob_Uncage or some thing like that. Lol!

No Manual Range Knob Depress present in controls page. Clockwise and Counter Clockwise, but no depress.

Course and Heading work for me. I have them mapped to DirectX buttons on TM combined controller.

It's all the component links in the OP.

I PM'd =Decoy=, Zues67, Prowler111, and Cpt Smiley, about posting a thread describing the state of the module. Not a discussion thread, but an informational thread. What's implemented, yet to be implemented, and WIP. Who knows, it might cut down on the stupid "My T-POD not working" threads that popup every week. And if they do, we as a community can jump their ass and point them to the information. There's still no reply to that PM by the way. I'm not asking for personal service. I'm asking for some common courtesy for the folks that generously participated in this early access project. Don't tell me to get on spam-cord or subscribe to your YT channel... In the style of Bernie Sanders. "I'm tired of hearing about the damn videos!" Get to posting some info we can use and refer to when posting bug reports. If any of this sounds harsh, equate it to the frustration that many feel, that only action will alleviate. p.s. Please stop moving threads to "Resolved Bug Reports". Just close the thread once it's been reported. That is a supposed to be a known process, as described to me by Nineline.

What does pushing the Heading knob do?

Thanks. Had to set the KB rate to 75,75.

Sorry guys and gals. Got a RW deadline that's kicking my ass. hope to get back to this next week.

You'll notice the menu burger in the upper left corner. All the sections can be found there.

https://flightcontrol-master.github.io/MOOSE_DOCS_DEVELOP/Documentation/AI.AI_A2A_Dispatcher.html

What is the status of this? Reported last December I can see that it was finally "Reported", 6 months after the OP, but still broke and fast approaching a year without resolution. There was even a solution posted. What could possibly so difficult with adding a few lines of code to this low hanging fruit?

So can anybody tell me why this doesn't work in TARGET SE? //Autopilot Select Switch ************************* MapKey(&Throttle,APPAT, PULSE + Autopilot_PITCH_Switch_ALT_HOLD); MapKeyR(&Throttle,APPAT, PULSE + Autopilot_PITCH_Switch_A_P_OFF); MapKeyR(&Throttle,APALT, PULSE + Autopilot_PITCH_Switch_A_P_OFF); MapKey(&Throttle,APALT, PULSE + Autopilot_PITCH_Switch_ATT_HOLD);But this does does? //Flap ************************* MapKey(&Throttle,FLAPU, PULSE + Autopilot_ROLL_Switch_HDG_SEL); MapKeyR(&Throttle,FLAPU, PULSE + Autopilot_ROLL_Switch_ATT_HOLD); MapKeyR(&Throttle,FLAPD, PULSE + Autopilot_ROLL_Switch_ATT_HOLD); MapKey(&Throttle,FLAPD, PULSE + Autopilot_ROLL_Switch_STRG_SEL); I'm using DirectX commands in the macros, but AP control switch will only twitch when activated. The Roll selection works fine. As you can see it's the same setup just on the Flap switch.