DCS World TARGET profile for TM Cougar and Warthog + MFDs

Home Fries · December 21, 2016

Just got the profile installed today and absolutely love it so far. One thing I've noticed though (and I've only tried out the F-15 atm) is that the slew seems incredibly fast. Any way to slow it down?

Your best bet is to use the in-game axis tuning to apply an axis curve or decrease its maximum throw. I left it as a straight line so people could adjust based on personal preference. Note that if an axis is reversed, it must remain reversed.

sobe · December 22, 2016

Home Fries

It took me reading your responses several times, but after doing so, I realized that you satisfactorily did answer all of my questions. I just wish I understood things a little better than I do.

sobe · December 22, 2016

Home Fries

When I do re-code your profile to include an F10 key (it does appear simple to do), I need to re-code it as a Left Control + F10 so in the tempo command

TEMPO(USB_F1,USB_F6,DefTempo)

how do I insert the Left control modifier?

Edited December 24, 2016 by sobe
Left control question

pimp · December 27, 2016

Hi HF,

How do I deactivate the FOV Zoom command on the Antenna Knob of my cougar for the A10C & Huey? I'm getting these 2-3 second stutters in game and when I gain control back from the stutters my view is zoomed all the way in almost every time. I have to manually zoom out with the numpad"/". So I'm trying to narrow down if my TIR or Cougar goes out of wack after these stutters.

Thank you!

Home Fries · December 27, 2016

Home Fries
When I do re-code your profile to include an F10 key (it does appear simple to do), I need to re-code it as a Left Control + F10 so in the tempo command
TEMPO(USB_F1,USB_F6,DefTempo)
how do I insert the Left control modifier?

TEMPO(L_CTL+USB_F1,L_CTL+USB_F6,DefTempo)

For "normal' modifiers recognized by TARGET (CTL, SHIFT, ALT) you can just use the + to join the modifier with the command.

For other keys that are modifiers in DCS but not TARGET (e.g. USB_LEFTGUI for the Windows key), you need to chain the keys (e.g. CHAIN(USB_LEFTGUI,USB_F10)). You can still nest a CHAIN command within a TEMPO command, but at some point it makes sense to add macros to the ttm file. This might be too much work in your case, though.

Hi HF,

How do I deactivate the FOV Zoom command on the Antenna Knob of my cougar for the A10C & Huey? I'm getting these 2-3 second stutters in game and when I gain control back from the stutters my view is zoomed all the way in almost every time. I have to manually zoom out with the numpad"/". So I'm trying to narrow down if my TIR or Cougar goes out of wack after these stutters.

Thank you!

You can always go into the controls menu in the Options menu, select the Huey, select Assign Axis (bottom center of the screen), and then under the Thrustmaster Virtual Controller Column find the FOV Zoom row, select the cell (Slider_1 I think) and select "clear" at the bottom of the screen.

Home Fries · December 27, 2016

Folks,

After a busy bout with my term papers, I got some free time yesterday and I was able to add the Spitfire to the upcoming 1.66 profile. However, there is some room on the right MFD for commands, and my time in the Spit is minimal so I was hoping somebody had some recommendations of what to assign to buttons. I'm also trying to figure out how best to use the speed brake switches for both the Cougar and Warthog.

Any suggestions are greatly appreciated. Expect the new release to hit shortly after the new year.

Rudel_chw · December 27, 2016

I'm also trying to figure out how best to use the speed brake switches for both the Cougar and Warthog. Any suggestions are greatly appreciated.

Hi,

I cant say about the Warthog, but on my Cougar I've found that I can use this switch to control Airbrakes, Flaps, Landing Gear and Landing Parachute.

Since the forward position is a hold type switch, while the back position isnt; I chose to divide the functions on this way:

- Back : Extend/retract Flaps

- Back + S3 : Extend Retract Landing Gear.

- Back and hold for 1 second: Extend Flaps to fully extended

- Forward : Open Airbrake, and when I return the switch to neutral it closes the Airbrake.

- Forward + S3 : Deploy landing parachute.

Best regards :)

Home Fries · December 27, 2016

Sorry, Rudel. I should clarify that I'm looking for how best to use the speedbrake switch with the Spitfire (which has no speedbrake).

I already have gear and flaps mapped (S3+H3U/D for cougar, Flaps handle and S3+CHF for Warthog). I might be able to do something like the mixture switch for T9 and the RPM lock for T10 (which changes the ANT knob from RPM to zoom), but then I need a solution for the Warthog (which doesn't need the RPM lock with 2 throttle axes and already has the mixture and carb filter mapped to the throttle).

TWC_Alamo · January 7, 2017

Home Fries,

Thank you for all the excellent work on making Target profiles accessible for the rest of us. I received a TM HOTAS Warthog for my birthday and had been feeling overwhelmed in the amount of work required to build profiles for only a couple of planes, much less the whole fleet!!!!

I installed 1.65 last night and finally got it going after discovering I really needed to improve my reading skills. ;-)

One problem that I'm not sure I resolved correctly is making desktop shortcuts to start DCS without updating. Has DCS removed the "Launcher.exe" program from 1.5? I couldn't find it in the /Program Files/Eagle Dynamics/DCS directory. Instead of putting launcher.exe in the shortcut's target, I put "DCS.EXE". It doesn't seem to check for updates, but I'm not sure that is the best way to do it.

Before posting this question I did search this thread for "update", "updater", and "launcher" but found no hits. So I apologize if this has been asked before, but I missed it.

Home Fries · January 7, 2017

Alamo,

Thanks for the kind words. With respect to your question, you can load "dcs.exe" in order to bypass the updater (normally the shortcut maps to updater.exe, which passes off to dcs.exe if the latest version is installed).

However, just to clarify, when I wrote Appendix B (in the setup guide) about shortcuts, it was for creating an executable shortcut for the TARGET script itself. If you setup such a shortcut, you can run the TARGET script in one step (i.e. without having to load the script editor, load dcs world.tmc, and then run the script itself).

sobe · January 8, 2017

Home Fries

How is 1.66 doing?

"I don't recommend doing anything before I release 1.66 (which should be soon after the new year) because I have relocated many of the routines that deal with hat switch assignments. However, when it comes time to do so, here is the section for the MiG-21 (lines 385-394 in DCS_Mig21.tmc in the 1.66 working build):"

I tried to find the similar language in 1.65 to change the snapviews to outside cockpit views but I couldn't locate the similar language that you provided in 1.66.

Edited January 8, 2017 by sobe
quote

Home Fries · January 8, 2017

I've added the Spitfire to the profile, but have yet to test the Cougar portion of it. Once that's done I'll release it. Shooting for early next week.

Rudel_chw · January 8, 2017

Sorry, Rudel. I should clarify that I'm looking for how best to use the speedbrake switch with the Spitfire (which has no speedbrake).

ahh, ok, english isnt my native tongue, so I probably misunderstood your post :)

Kudos for your Target profile ... I tried it some months back but found Target much too complex and so I chose instead to stick with the old Foxy utility, which still Works well with my Cougar and Windows 2012r2 (similar to Windows 8.1; have to use it for work reasons))

Also, I prefer to have dedicated profiles for each plane, even tough I do try to keep common functions binded to the same Hats & Buttons.

Best regards.

TWC_Alamo · January 9, 2017

Home Fries,

Thanks for the speedy reply.

Alamo,

However, just to clarify, when I wrote Appendix B (in the setup guide) about shortcuts, it was for creating an executable shortcut for the TARGET script itself.

To better clarify my question, I was referring to Appendix C, page 22 where you show how to create a shortcut to run DCS without updating by replacing "DCS_upater.exe"with "Launcher.exe".

If you setup such a shortcut, you can run the TARGET script in one step (i.e. without having to load the script editor, load dcs world.tmc, and then run the script itself).

I did follow the instructions in a appendix B and create a shortcut to run the DCS World.tmc script. That does simplfy startup. Taking it one step farther, I know I can create a batch file to run the script and then start DCS. I admit that I haven't cracked manual on Target Programing, but is there a way to launch DCS from inside a Target script?

Also, it appears from the script editor that you can compile a script? Is there any advantage to compiling the DCS World.tmc and running the compiled script?

Again, thanks for this excellent capability.

TWC_Alamo · January 11, 2017

Home Fries,

I have been working my way through my fleet of DCS planes setting up the profiles for each. All has gone well. Every time I thought I have found a problem, it has turned out I did something wrong or should have read the instructions more carefully.:cry:

In setting up the Hawk, I have encountered a problem: I had entered a "1" on the line for Hawk T.1A in the Installed Module section of the DCS World.tmc, but the Hawk was not in the list of a/c in the hot selection process. So I made it the default module and when I launched the script and received the following error:

Runtime Error: Symbol not found: DCS_Hawk_Init in HOTAS_Cougar_Button_Init ( line 315 in DCS World.tmc )

Looking in my "E:\TM\TP\DCS\Modules" directory, I find no .tmc file for the Hawk or C101. Have I missed something?

I download the 1.65 files from the DROP BOX link.

Here is the output from the script startup for:

*** Allocated ProcInstances found from the previous run: use FreeProcInstance() ***

Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"

Physical USB HID devices managed by script!

Currently plugged USB HID devices[5]:

1: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100"

2: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100"

3: "T-Rudder" - "USB\VID_044F&PID_B679&REV_0110"

4: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"

5: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"

USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\8&5E69C2F&0&6) selected

USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\7&1B686353&0&1) selected

USB HID device "F16 MFD 1"(USB\VID_044F&PID_B351\7&1B686353&0&4) selected

USB HID device "F16 MFD 2"(USB\VID_044F&PID_B352\7&1B686353&0&3) selected

USB HID device with hardware id "VID_044F&PID_0400" cannot be found

Virtual HID devices managed by script!

Connecting virtual joystick...Done

Device name set to Thrustmaster Combined

Connecting virtual keyboard...Done

Connecting virtual mouse (absolute axes)...Done

DCS_Global() Start.

DCS_Global() Finish.

DCS_Init (Profile v1.65):

Script stopped!

Runtime Error: Symbol not found: DCS_Hawk_Init in HOTAS_Cougar_Button_Init ( line 315 in DCS World.tmc )

sobe · January 11, 2017

I couldn't have said this better:

"Every time I thought I have found a problem, it has turned out I did something wrong or should have read the instructions more carefully.:cry:"

Home Fries · January 11, 2017

Alamo,

Last time I touched the hawk profile, I was just mapping HOTAS and keyboard commands that work with the DX profile. There is no dedicated Hawk slot yet (which is why it defaults to 0); you need to set the DX profile accordingly to use the Hawk. The error message is still my fault: I wrote the code to load the DX profile if the Hawk Init is used, but I haven't properly tested it. Same with the C-101.

Last time I even touched it, the Hawk was using the SFM with no trim and the systems modelling still had the radio issues and very few key mappings. I got frustrated and put it on the back burner. I suppose it's time to revisit the profile, but the Hawk is queued behind updating the MiG-21, the Viggen that's coming out in a few weeks, etc.

The good news is that the DX profile is by default set up for a non-afterburning single engine jet like the Hawk or C-101. Instead of trying to load the Hawk, load the DX profile and go with that.

Edited January 11, 2017 by Home Fries

Home Fries · January 11, 2017

I couldn't have said this better:

"Every time I thought I have found a problem, it has turned out I did something wrong or should have read the instructions more carefully.:cry:"

The flip side of this is that I could write things more clearly. As an engineer by trade, I write technical documents with precision, but sometimes at the expense of clarity. Any suggestions you guys have for updating the text is greatly appreciated, as I'm too close to a problem to see it.

Home Fries · January 11, 2017

To better clarify my question, I was referring to Appendix C, page 22 where you show how to create a shortcut to run DCS without updating by replacing "DCS_upater.exe"with "Launcher.exe".

Oh, right, the JSGME tutorial :doh:. I'll be sure to update that.

I did follow the instructions in a appendix B and create a shortcut to run the DCS World.tmc script. That does simplfy startup. Taking it one step farther, I know I can create a batch file to run the script and then start DCS. I admit that I haven't cracked manual on Target Programing, but is there a way to launch DCS from inside a Target script?

There is a way to launch external programs (it's how I play the wav files that announce each profile selected), but it is very difficult to use and also very limited in its privileges. You could probably get it to work, but it's not worth the effort. Besides, you want to make sure your profile is completely loaded before you run DCS so that it will detect the proper controller. Even though DCS detects controllers dynamically now, it's still a lot better for DCS to start with the controllers it's going to use.

Also, it appears from the script editor that you can compile a script? Is there any advantage to compiling the DCS World.tmc and running the compiled script?

Compile is a misnomer, as the script is runtime only. Compiling is just checking the script for coding errors without actually running the script itself.

TWC_Alamo · January 12, 2017

Home Fries,

Alamo,
There is no dedicated Hawk slot yet (which is why it defaults to 0); you need to set the DX profile accordingly to use the Hawk.

The good news is that the DX profile is by default set up for a non-afterburning single engine jet like the Hawk or C-101. Instead of trying to load the Hawk, load the DX profile and go with that.

No problem. I'll try using the DX profile.

The flip side of this is that I could write things more clearly. As an engineer by trade, I write technical documents with precision, but sometimes at the expense of clarity. Any suggestions you guys have for updating the text is greatly appreciated, as I'm too close to a problem to see it.

I am an engineer too and too often do a fast read, jump to conclusions as to where I think you're going and when it doesn't work, come back, reread the manual but with precision. :smilewink: I'll pass along my notes of any areas where I went the wrong direction.

There is a way to launch external programs ... Compile is a misnomer, ....

Thanks for the explanations.

I have encountered a problem with the F-5E profile. Everything seems to work as shown on the Warthog graphic except for the Coolie Hat (CH) on the Throttle. CH (up) and CH (down) work fine to increase/decreases radar elevation, but CH(left) and CH(right) appears to do nothing. In the script event tester, I can see CH (up) and CH (down) generating the correct keyboard strings for the radar elevation, but nothing for CH left and CH right in either normal or shifted modes. Kb commands should be "0","9", "-" and "=".

I am a little confused about which button presses generate events observable on the event tester.

Line 180/181 in F5E.tmc, appears to assign DX22/DX23 to CH (left and right). Looking in the F5E sim control's profile for the radar mode and range functions, I don't see anything mapped in the Thrustmaster Virtual Controller column. Should this be DX22/DX23?

So, I don't know where there should be buttons assigned in the controller column or if the command is coming as a kb command. Where do I go from here to trouble shoot? :helpsmilie:

This is a good opportunity for me to understand how these profiles work, so any explanation or comments would be greatly appreciated. :megalol:

Thanks

TWC_Alamo · January 12, 2017

F-5E Profile: radar range and mode

Should have tried this before making the preceding post...I'll answer my own question. :joystick::joystick::joystick: I entered JOY_BTN30 + JOYBTN22 /JOY_BTN30 + JOYBTN23 for the CCW/CW radar mode and JOY_BYN22/JOY_BTN23 for radar range rows in the controller profile in DCS and it all works fine now.

So when we see a function being assigned to a DX yy button, then we should see that JOY_BTN yy button being assigned a function in the controller's profile column?

Now I need to figure where/how in the *.tmc script, you assign key presses to buttons.

I know, I know ---> I need to RTFM for Target! :book::book::book:

:doh:So much too learn, so little time to actually fly!:doh:

Home Fries · January 12, 2017

Should have tried this before making the preceding post...I'll answer my own question. :joystick::joystick::joystick: I entered JOY_BTN30 + JOYBTN22 /JOY_BTN30 + JOYBTN23 for the CCW/CW radar mode and JOY_BYN22/JOY_BTN23 for radar range rows in the controller profile in DCS and it all works fine now.

So when we see a function being assigned to a DX yy button, then we should see that JOY_BTN yy button being assigned a function in the controller's profile column?

Now I need to figure where/how in the *.tmc script, you assign key presses to buttons.

I try to keep things as much DX as possible so that keystrokes are minimized that might cause issues outside of the game. However, I find most throttle controls need to be keyboard just because there are too many switches and only 28 DX commands (29 is reserved for the wheelbrake, DX30-32 are modifiers allowing use of the S3 as a shift as well as the MFDs). You can probably tell by my stopping at 28 that this was originally a Cougar profile.

Anyway, if the button is a DX command, you should see it in the Device Analyzer, while keyboard commands can be seen in the Event Tester. Both are available from within the Script Editor.

for the F-5, the CS left and right should be for decreasing and increasing the radar range respectively (s3+CSL/CSR for radar mode cycle). If these aren't present, the icommands may have been changed in a recent update. Thanks for the report; I'll fix it and include it in 1.66.

TWC_Alamo · January 13, 2017

F-5E Profile Questions

Home Fries,

...the CS left and right should be for decreasing and increasing the radar range respectively (s3+CSL/CSR for radar mode cycle). If these aren't present, the icommands may have been changed in a recent update. Thanks for the report; I'll fix it and include it in 1.66.

Great. Also the "radar mode" cw/ccw" functions in the shifted mode of CH(Left/Right) appear to be missing in the F5E controller profile.

Just a couple of other questions about the F5E profile.

(1.) Is there any way to use the HOTAS to adjust the rudder trim? The JOY_BTN30+H1(left/right) are available in several of the other profiles, but not in the F5E profile?

(2.) I may be missing something in understanding the overall schema of the profiles, but what is the logic of having S3 activate the comms menu in the GSU mode, when the mic switch on the throttle works in either GSU/GSD? I have had trouble using the HOTAS to lower the landing gear. When the comms menu is up it seems to inhibit the function of the china hat.

I am amazed at the effort you must put in to keep up with all the different commands and controller profiles for soooo many planes. Great work!!!!:thumbup:

TWC_Alamo · January 13, 2017

VR Support

Home Fries,

When you consider future improvements, please consider implementing a couple of VR functions. These are located in the UI section of the profile and should apply across all profiles.

(1). VR

(2). VR Zoom

It would also be handy to have the option of mapping the mouse functions shown in the UI section to one of the hat switches for use in VR.

BTW---I just donated to your development work.

Home Fries · January 18, 2017

Alamo,

Thank you for the generous donation. Regarding your request, I don't have VR, so what are these functions and what do they do? I imagine I should reserve two buttons or hat switch directions for left/right mouse buttons in VR, but other than that, is there anything I should know about the functions? Could I piggy back them with a TEMPO command and make them a TEMPO Long, or do they need to be instant response? Does the button need to be held during an operation such as zoom?

Anything you can do to help me out would be great. Feel free to PM me.

Just putting the finishing touches on 1.66. It's been tested and some fixes and enhancements were added. I should have it out by the end of the week.

Sign In

DCS World TARGET profile for TM Cougar and Warthog + MFDs