SGT Coyle

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.

All's fine with mine, but I might need a little more info. Are you running a script?

"Straight DX Controller"? No mapping software between the controller and the DCS. Just a straight plug-n-play.

If you just use the WH as a straight DX controller, yes. As long as you don't adversely change your settings in DCS. Yes. You can edit these files with any text editor, but you need TARGET SE to compile and run the scripts. I often have the Macro file open in NP++ and the Script file open in TSE. My war cry.

Yes. If Display_Management_Switch_Up is mapped to L_Alt + D in DCS, and TARGET is programed to send L_ALT + 'd' when DMT UP is pushed: you will get the Short and Long presses. That's DCS doing that. Now just to be clear. There is no DMS long press in the F16. There is one long press on the TMS. Checkout pg 38 in the Viper manual. I hope that's clear

How does the GUI handle 3 position switches. I'm using the Flap switch and the Auto Pilot Select switch for the 2 AP control switches. AP Pitch Control: //Autopilot Select Switch ************************* MapKey(&Throttle[color=#ffffff],[/color]APPAT, PULSE + Autopilot_PITCH_Switch_ALT_HOLD); MapKeyR(&Throttle[color=#ffffff],[/color]APPAT, PULSE + Autopilot_PITCH_Switch_A_P_OFF); MapKeyR(&Throttle[color=#ffffff],[/color]APALT, PULSE + Autopilot_PITCH_Switch_A_P_OFF); MapKey(&Throttle[color=#ffffff],[/color]APALT, PULSE + Autopilot_PITCH_Switch_ATT_HOLD);and AP Roll Control: [color=#32cd32]//Flap *************************[/color] MapKey(&Throttle[color=#ffffff],[/color]FLAPU, PULSE + Autopilot_ROLL_Switch_HDG_SEL); MapKeyR(&Throttle[color=#ffffff],[/color]FLAPU, Autopilot_ROLL_Switch_ATT_HOLD); MapKeyR(&Throttle[color=#ffffff],[/color]FLAPD, PULSE + Autopilot_ROLL_Switch_ATT_HOLD); MapKey(&Throttle[color=#ffffff],[/color]FLAPD, PULSE + Autopilot_ROLL_Switch_STRG_SEL);Using the MapKeyR (R for release) command for pulsing the middle switch position, when either the up or down positions are released. Works like a charm. You have to use "PULSE +" in front of macro, or the command will be continuously keyed until moved out of position.

The Macro, as I use it, only defines keyboard/usb codes/ DirectX commands to a keyword. F16C.tmc Example ( Macro Keyword in red): [color=#32cd32]//DMS[/color] MapKey(&Joystick[color=#ffffff],[/color]H3U, [color=red]Display_Management_Switch_Up[/color]); MapKey(&Joystick[color=#ffffff],[/color]H3D, [color=red]Display_Management_Switch_Down[/color]); MapKey(&Joystick[color=#ffffff],[/color]H3R, [color=red]Display_Management_Switch_Right[/color]); MapKey(&Joystick[color=#ffffff],[/color]H3L, [color=red]Display_Management_Switch_Left[/color]); Associated Macro file Commands to be mapped in DCS in purple: [color=#1e90ff][/color] [color=#1e90ff][b]define[/b][/color] Display_Management_Switch_Down [color=purple]DX14[/color] [color=#32cd32]//[/color] [color=#1e90ff][b]define[/b][/color] Display_Management_Switch_Left [color=purple]DX15[/color] [color=#32cd32]//[/color] [color=#1e90ff][b]define[/b][/color] Display_Management_Switch_Right [color=purple]DX16[/color] [color=#32cd32]//[/color] [color=#1e90ff][b]define[/b][/color] Display_Management_Switch_Up [color=purple]DX17[/color] [color=#32cd32]//[/color] As with the A10C, you only have to map the DMS "UP" button to DMS UP in DCS. DCS will handle the long and short for you. I'm using DirectX commands here, but those can easily be replace with keyboard characters.

So whats with the Template? The Script Template in the OP is setup to make it faster to get up and flying with a new script. With a generous use of comments I divided the Script into sections. Axis controls LED lighting Stick controls Throttle (Hand)controls Throttle Base controls Left MFD Right MFD Each section has a line of code for every button and switch position(Some are 2 pos, some are 3 pos). All lines that have a control associated, have been commented out like so: Left Throttle Button ************************* This is Sub-Section [b]//[/b][color=Red]MapKey[/color](&Throttle,LTB, 0); // This minimum mapping code required You only need to un-comment the lines you want to map. To un-comment, just delete the slashes at the beginning of every line in front of "MapKey". With in every section there's a few lines commented out as notes on how to do certain things. //---//MapKey(&Throttle, [color=Red]Button to be mapped[/color], [color=Blue]Macro[/color]); //---//MapKeyIO(&Throttle,,[color=SeaGreen]in layer[/color], [color=Cyan]out layer[/color]); //---//MapKey(&JoystickF18,, TEMPO( [color=Red]short[/color], [color=Purple]long[/color], [color=Blue]time[/color]));These notes also make it easier to cut and paste if necessary. I'll cover what these mean later.

As for setting up F16 specific controls; one of the first things I do is look at the Stick diagram in the manual. Try to figure out what controls there are to map and try to match them with the buttons on the WH Stick. Same with the throttle. As for the stick, it's pretty easy. It's the same stick as the WH.

Cut and Paste is the rule! How to use the Macro file within the Script. Open the your previously saved "what ever you want.tmc" in the script editor. Compile it. To the left you'll see a file list containing all the files required to make the script work. You can open them in the editor by clicking on them. We are only concerning ourselves with the .tmc and the Macro you made earlier. Looking at the macro in the TSE, you see a long list of "Defines" conveniently divided by section as they appear in the DCS controls page. The define for any command begins with "define" followed by a space or tab. Next is the actual command we want to map followed by space or tab (All one word, NO SPACES. Use underscores). Last is the Keyboard command or USB Code that is mapped in DCS. Below is and example of the Macro I made for the F16C. The Macro Generator translates the keyboard commands into Modifiers and USB code. It also gives readable translation in the form of a comment, at the end of every define. // Stick; HOTAS; Flight Control *************************************************************************************************************************** define TRIM_Button_LEFT_WING_DOWN R_CTL+USB[0x36] // "RCtrl - ," define TRIM_Button_NOSE_DOWN R_CTL+USB[0x33] // "RCtrl - ;" define TRIM_Button_NOSE_UP R_CTL+USB[0x37] // "RCtrl - ." define TRIM_Button_RIGHT_WING_DOWN R_CTL+USB[0x38] // "RCtrl - /"To illustrate the utilitarian nature of the macro file, I rewrote the example to show how you can use USB code, DirectX commands, and straight keyboard keys. // Stick; HOTAS; Flight Control *************************************************************************************************************************** define TRIM_Button_LEFT_WING_DOWN[b] R_CTL+USB[0x36][/b] // Right Control modifier plus the USB code for comma define TRIM_Button_NOSE_DOWN[b] R_CTL+';'[/b] // Same as above except Modifier plus straight keyboard text always between apostrophe for semi-colon define TRIM_Button_NOSE_UP[b] DX1[/b] // DirectX command. Explained later define TRIM_Button_RIGHT_WING_DOWN [b]RARROW[/b] // Right Arrow key. No modifierOK, so how does this help? Cut and paste is your friend. If you cut TRIM_Button_LEFT_WING_DOWN and paste it into the command for the trim hat up in the .tmc file you made, you will get a Right Control + Comma command sent to DCS when you push the trim hat forward. The command looks like this //Trim MapKey(&Joystick,H1U, TRIM_Button_NOSE_DOWN); MapKey(&Joystick,H1D, TRIM_Button_NOSE_UP); MapKey(&Joystick,H1R, TRIM_Button_RIGHT_WING_DOWN); MapKey(&Joystick,H1L, TRIM_Button_LEFT_WING_DOWN); This makes reading the .tmc file much easier than having to read "R_CTL+USB[0x36]" and wondering WTF? As always I hope this helps.

Exactly. How many TM WH throttles have sold? How many production runs were there to date? After all the time and expense of setting up one line, how profitable would it be to add a competing line of comparable cost/price only to split the limited market. Offering up the F18 Grip shouldn't have effected the market for the WH Joystick. You need to buy the WH Stick and the F18 Grip to use the grip. I don't blame them for that. Who wants to stuck with a boat load of old grips.