SGT Coyle

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.

Truth brother. I would imagine that there is a fear of the flight sim community is not growing, and no one wants to manufacture for stagnation. A rebuild of the WH Throttle in an F18 or F16 realism theme, is probably not seeming like a product that will fly off the shelves at a profitable price. If there was an F16 style Throttle base of the same quality, that combined with my other TM devices, I would consider it.

How to set this thing up? Use the "Create New File" (CTRL + N) option in the TARGET Script Editor (TSE), and select .tmc from the file types presented. This will then open the TSE text editor with default code. We will overwrite this. Copy and paste the Template.tmc from the OP into your text editor, overwriting all the default text present, and save as "TEMPLATE.tmc". Now you have a template in the .tmc format to use over and over again. Place the Macro file(.ttm) in the same directory as your previously saved .tmc. It may be useful to mention that setting up a profile directory for your scripts and macros would be a good idea. TSE will use the default directory created on install for all saves. C:\Program Files (x86)\Thrustmaster\TARGET\scripts. I'll cover organizing files later. OK, almost there. In the text editor, open the TEMPLATE.tmc, if not already open. First edit, is to change line 3: //include "DCS_XXXSim_Macro.ttm" // Place holder for macro fileto: include "Place Name of Macro File.ttm"The name of the file, including the .ttm extension goes between quotes the "xxx.ttm". Save it! Save the .tmc as "What ever you want.tmc". Now you've preserved your TEMPLATE.tmc for future modules and have a usable script to edit in. Now TEST it! At top of text editor click "Compile". At the bottom of the text edtor is an output window. Script errors will be listed there. If all goes well "Compile Succeeded" is there If compiling is successful, then Run It! Next to compile button is the Run button. Click it an watch the output window for errors. You don't need to to have your devices connected to run a test. Were only looking for errors in the files. If you did every thing right your ready to start editing. If you get errors post them here. As always I hope this helps.

Started a thread for TARGET SE with my script template and a link to a power-shell app I use for making TARGET Macro files. https://forums.eagle.ru/showthread.php?t=251972 As for making your own script, you'll be flying and enjoying the A/C faster than if you DL'd a ready made profile. You still need to learn the profile and that takes time. At least by doing it yourself you already know how you planned it, wrote it, and why it does what it does. HomeFrie's CTS is awesome, but Holy Handgrenades Batman! That is one involved diagram. I prefer to keep it simple stupid, or is that stupid simple.

No. But fixing that made no difference. Neither did fixing the spelling of "CAP F14" to "CAP F14b" like it should be.

First! Make a Macro File (.ttm) of the module you want to map with TARGET. Use this fantastic tool by Carlton2001 for that purpose. Macro Generator This tool converts the Keyboard Controls HTML, you create with DCS, to a Macro File you can use in TARGET. It contains every keyboard command that exists in the module. Next, Make a Script Template. It should include all Thrustmaster devices you intend to use. This is the one I use for every module I own: The above file has all the mapping commands for every button on Left and Right MFDs, Throttle, and Stick, commented out. All that needs to be done is copy and paste the DCS command from the macro into the MapKey function you want and un-comment the line(To un-comment, remove the // from the beginning). Page 15 of the Fast Scripts Basics explains the MapKey function and page 20 explains Macro File. That's quick and dirty. Not complete, but the manual is really good and not very difficult to follow. I will add more to concerning more multiple functions per controller button soon. Followup Posts: Setting up files Working with Macro files Template Explained Mapping a single key Layers If you have questions or comments about what is presented please PM me. I'd like to keep the thread from bulging from individual one on one conversations. If something needs further explanation or clarification, I will edit appropriate post.

Very stumped. Can't figure out why this isn't working. Using AI_A2A_DISPATCHING and the latest dev version Moose.lua 3-10-19 has a errorin the A2ADispatcher:SetSqudron function. This is the script: Here's the log: Mission attached Any thoughts appreciated. CTF_Protection_Ops.miz

After spawning a E2D for a AWACS patrol via wapoints. How can I repeat the spawn once he starts to RTB? I have him in the ME as a template, starting on carrier parking hot. I want to do the same for a tanker.

Using the latest Moose.lua (3-10-19) and ai_a2a_dispatch, I assign my squadron (group of 2 F14)to takeoff form runway (Stennis), but I get one hooked up and ready to launch and one not. The one not hooked up to the cat, tries to launch anyway.

I was thinking of posting a simple tutorial. Look for it tomorrow. No way to go from GUI to SE AFAIK. Same for SE to GUI.

I know I saw some where that there's a security concern preventing direct JADAM coordinate entry. Of course, now I can't find it anywhere.

dtdionne, What was it in your OP that wasn't working? It worked for me. I assumed it was the MapKey function, but looking at the example on pg 38, it seems logical. I never used MapKey in an exec. I don't think.

Awesome!

What? If PSB, then H4U will produce DX28, is that what you want? Post your script, I'll try to fix it. Look at the layers section in the book. You need to declare what your In, Out, Up, Middle, Down, buttons are. SetShiftButton(&Joystick, [b]S4[/b], &Throttle, [b]PSF[/b], [b]PSB[/b]); //Assigns the pinky Lever on the stick (S4) as momentary In/Out Layer. Assigns PSF as UP layer and PSB as DOWN LayerThen you write your MapKey function call like this: MapKeyIOUMD(&Throttle,H4U, 0, //IN Layer Use zero for no action. 0, //OUT Layer 0, //UP Layer 0, //MIDDLE Layer [b]DX28[/b], //DOWN Layer [b]UD[/b]TOGGLE); //Sets UP and DOWN layers to TOGGLECheck out the section on "Layers" in the TARGET Script Editor. Post you script If you still need help. Good luck.

How long were you without the grip?

Excellent!