DCS World TARGET profile for TM Cougar and Warthog + MFDs

Home Fries · April 27, 2017

Wow! Hard to believe this script exceeded bandwidth; I guess it's gaining in popularity.

I should have version 1.69 released next week, so you may want to wait a few days and save yourself the re-configuration. In the meantime, I've uploaded draft versions of the 1.69 manuals (this is one of those rare cases the manuals are done before the rest of the build) to my Google Drive, so while you're out of town you can read up on how to setup the script, tweak it to your liking, and use the modules.

Setup Guide (Read First)

User Reference (How to use the script)

Advanced Configuration Guide (how to tweak the profile to your use, and appendices for manual entries)

Enjoy!

Edited April 27, 2017 by Home Fries

Rangoon · April 27, 2017

Thanks!

Ric0chet · May 1, 2017

Hello mate, thanks so much for your hard work. It makes a lot of sense to use the target software to set up one "profile" that can be switched across multiple aircraft.

I might be missing something though, I'm new to DCS and I'm having serious trouble seeing how this is set up? Your setup guide gives me instructions on where to put files (which I have followed) but I get seriously stuck when it comes to the TARGET software. The GUI seems to be completely different to the document described. I have a user interface which graphically allows me to assign "events" with a 3D model of the joystick and throttle. When I import the "DSC World" file into the TARGET software and import the events, and save the profile nothing actually works. I go to the event tester and none of the buttons trigger actions

Sorry for being a pain I'm sure one of you can help me out.

thanks - Ric0chet

Edited May 1, 2017 by Ric0chet

Home Fries · May 1, 2017

Ric0chet,

No problem at all. What you're likely loading is the TARGET GUI (the software that will create you a profile based on button assignments. Instead, you need to load the TARGET Script Editor, which is the blank slate that allows you direct access to the code. You can also use a text editor like Notepad++ to make your code edits, but it's just as easy to do it from the script editor and then press the "play" button from the tools menu to start the script.

Once you get comfortable with using TARGET, there is one use for the TARGET GUI executable. See Appendix B in the Setup Guide to see how to create a desktop shortcut that will run the script for you.

I deliberately avoid writing about how to use the TARGET software in my manuals (they're extensive enough as it is). However,since you're a set of fresh eyes, is there anything I can do to clarify things for newcomers in the Setup Guide?

Hope this helps,

HF

Moreno · May 1, 2017

I just checked if TrackIR is the problem. I unplugged it but it's still shaky. I would really appreciate if you could send me a quick tutorial how to map the antenna the way it is done with the F-15. So that Ant Elev is standard and FOV Zoom is on /I shifted mode (S3 pressed). Maybe it's a good idea to implement it into your profile, then it's consistent.

Best,
Moreno

Hi Home Fries, just wanted to ask if there is a possibility to describe in a few lines what code in which file I need to edit? Or is it a big thing to do it? I already tried to mess around with comparing the F-15.tmc file to the M2000 but didn't come to a solution...

Edited May 1, 2017 by Moreno

Home Fries · May 1, 2017

Hi Home Fries, just wanted to ask if there is a possibility to describe in a few lines what code in which file I need to edit? Or is it a big thing to do it?

Sorry, Moreno. I blew through your previous post and assumed that TrackIR was the issue. I'll look at the code and get back to you.

sobe · May 2, 2017

Homefries

I just updated Win10 to the creator edition and I am having issues with Target. It seems to work ok with Ice's target profile for BMS, but when I try your last two target profiles for any airplane, I get issues like the controllers do not combine, the device analyzer does not work, etc. I reinstalled Target, but to no avail. Am I the only one or are other users having issues with Target?

Home Fries · May 2, 2017

I have heard about this. Supposedly it's a known issue that TM is working on. I have no idea if there are any workarounds; I'm still using Windows 7 by choice.

Edited May 2, 2017 by Home Fries

Moreno · May 2, 2017

Sorry, Moreno. I blew through your previous post and assumed that TrackIR was the issue. I'll look at the code and get back to you.

Very much appreciated! :)

Ric0chet · May 2, 2017

Thanks again Home Fries,

That is a lot clearer now you mention the TARGET Script Editor Rather than the TARGET Gui. I understand all the "tick 1 for x" instructions now.

EDIT *** Following Page 16*** Modifiers were screwing me up i've rectified this issue. I should be good to fly now! I'll let you know

EDIT 2 *** MODIFIERS *** Why is it that the TARGET GUI doesnt run the modifiers like the TARGET Script applications?

Edited May 2, 2017 by Ric0chet

Moreno · May 2, 2017

EDIT 2 *** MODIFIERS *** Why is it that the TARGET GUI doesnt run the modifiers like the TARGET Script applications?

Have you made a shortcut running the correct script as Home Fries outlined in Appendix B?

sobe · May 2, 2017

The response from TM Support-

We thank you for your reply.We like to inform you that we have received your message and that we have forwarded the info to our R&D department.

As mentioned previously we have received similar reports and we are investigating this problem resulted from the latest update package released by Microsoft. Your info will be of great value to our colleagues.

If any additional details will be needed from you we will contact you immediately.

This might take at least a couple of weeks from now on. We will get back to you as soon as we will have some definitive solutions.

If you have any other inquiries do not hesitate contacting us back by simply replying to this email.

Rangoon · May 5, 2017

Home Fries - I can't thank you enough for these profiles. I installed 1.68 and have everything up and running for the Ka-50. Fantastic work!

I have a question (possibly a bug?) about the Ka-50 fuel shutoff valve switches. I think I understand the basic switch states and how to adjust if things aren't synchronized (such as the Automatic Tracking switch, for example - hold down S3 and switch to match, then release for actual use), but it seems the Left and Right fuel shutoff switches are backwards. The APU switch is correct, but the main engines are opposite. The documentation shows it the way I think it should be: aft position is fuel off, sim switch on wall panel down; middle position is fuel on, sim switch up; fore position toggles large fuel cut-off lever on left side). Is this something I'm misinterpreting? Or misunderstanding initial states for a cold/dark aircraft?

Thanks!

EDIT: I wonder if the logic is that the "shutoff" valve is "on" when it's in the "cutoff" position (down on the aircraft wall switch but middle on the Warthog Throttle) and the valve is "off" when in the aircraft switch up position... Is that it?

Edited May 5, 2017 by Rangoon

Home Fries · May 6, 2017

Thanks, Rangoon. I'll give it a look.

Sorry everybody. I was hoping to get 1.69 out this week, but real life had other plans. I'm shooting for next week, but no promises.

Rangoon · May 7, 2017

I have a few questions about PTT Common. Browsing through a few profiles, for example, A-10C and Ka-50, I see PTT common in more than one place. A-10C has it as Mic press as well as Mic up (Warthog). Ka-50 has it as S2 and Mic switch press.

1) These are redundant, then, right?

2) If I want to add another "comm" function, precisely a Voice Attack "listen to me" button, would it make sense to use one of these redundant PTT Common slots? Or will that get me into trouble with other profiles down the road? Is that a consistent situation for there to be more than one PTT Common?

3) would this simply involve making a single edit to the tmc? And then whenever there are updates, just remember to make that same edit again?

Or am I thinking about this wrong? I want to have Voice Attack control over my AI wingmen, ATC, etc but not lose the ability to use TeamSpeak etc for multiplayer. If I only played SP, then I could obviously just assign DX21 to Voice Attack and be done with it.

cichlidfan · May 7, 2017

Sorry everybody. I was hoping to get 1.69 out this week, but real life had other plans. I'm shooting for next week, but no promises.

No need to apologize for RL having priorities over this project.

I also wanted to take the opportunity to say kudos on an impressive piece of work. I have been using Target for a long time, and I also remember when ivanwfr was posting some interesting Target stuff. I haven't actually used your profile yet, I am just going through it to see how you did things and I am very impressed. Your documentation has to be some of the best, and most thorough, that I have seen for any 'mod' or freeware project.

Thank you very much for all of the effort you have put into this.

Rangoon · May 10, 2017

Hi Home Fries - getting into the Huey now. Really like how you handled the throttle control. And in general, again, absolutely love the profile and appreciate the work you put into this.

I think there might be a bug/inconsistency in the master weapon switch and the master caution switch. In the documentation, it says the far bottom (aft) left switch on the throttle base is weapon select, which it is, and the one to the right of that is the master arm switch, which it is (between off and arm, skipping "safe"). It says H2 up and down are also weapon select switch, which they are. However, it says with shift those two should be master caution switch up and down (which I believe should be the "reset" and "test" options on that switch) but they control the master arm switch (so that you can hit all three positions instead of skipping "safe", which is nice but I'm not sure it's intended or if that is even useful in practice). It also says the LDGH button should be master caution, but I'm not yet sure it does anything at all, FWIW.

Just throwing that out there in case you're delving into details like this for 1.69.

Thanks again!

Cravgar · May 14, 2017

warning to people running windows 10. I'm pretty new to using these profiles but i put the creators update on my system and now things dont seem to work. I get a vitrual device showing in game but none of the buttons are being recognised.

out of the game, script comes up and says 'm2k' for the module. s3+LOSB1 does not enable anything for me to switch profile. Event tester isnt picking anything up either.

Home Fries · May 17, 2017

warning to people running windows 10. I'm pretty new to using these profiles but i put the creators update on my system and now things dont seem to work. I get a vitrual device showing in game but none of the buttons are being recognised.

Here's what TM said about the Win10 issue:

The response from TM Support-

We thank you for your reply.We like to inform you that we have received your message and that we have forwarded the info to our R&D department.
As mentioned previously we have received similar reports and we are investigating this problem resulted from the latest update package released by Microsoft. Your info will be of great value to our colleagues.
If any additional details will be needed from you we will contact you immediately.
This might take at least a couple of weeks from now on. We will get back to you as soon as we will have some definitive solutions.
If you have any other inquiries do not hesitate contacting us back by simply replying to this email.

out of the game, script comes up and says 'm2k' for the module. s3+LOSB1 does not enable anything for me to switch profile. Event tester isnt picking anything up either.

The inability to change profiles is likely due to the Win10 issue, though without Win10 I cannot test this.

EDIT: Looks like you deleted your post while I was responding.

sobe · May 17, 2017

Today's response from TM:

We thank you for your reply.

Under these circumstances then the problem is caused by the latest update you have installed for the OS, the "Creators Update".

We are currently investigating this problem ourselves, analyzing the updates this patch brought to the actual OS and the modifications it made to various sub-systems so that we can determine what might be interfering with the TARGET's normal performance.

For the moment we do not have any additional details to provide you with.

Rangoon · May 18, 2017

Huey searchlight:

Am I understanding correctly that when the searchlight (not landing light) is on (Boat Switch forward), then H1 should aim the light, right? I can see in the keybinds that one of the three modifiers (forget which one) plus POV 1 does indeed aim the searchlight, but I haven't gotten it to work yet. It's as if turning on the searchlight isn't communicating its state and activating the modifier. I get the basic, unmodified H1 behavior. Any ideas?

EDIT: looking through the script code, I found that the searchlight is controlled with the Coolie Switch, not H1. I just can't find that in the documentation anywhere, and assumed POV 1 was H1, and/or that "Station/Sling" for some reason might have jived with searchlight control (not the same thing, obviously).

Home Fries, you mentioned that the micro stick doesn't work well for controlling the searchlight, however I've not had much trouble with it controlling the Shkval as long as I have my axis tuning in DCS set appropriately. When I tried to assign the micro stick to searchlight control in DCS, the axis just isn't available (doesn't register). Is this because you have that axis disabled in the controller? Or is it not a valid axis for that function in DCS?

In my use, I've also seen that the gunner doors seem to be reversed. Pressing MS right opens the left door, pressing MS left opens the right door.

Another kind of buggy thing I've seen in both the Ka-50 and UH-1H is that when I pause TrackIR and then use H1 to pan the view, it sometimes unpauses TrackIR. I then end up cycling TrackIR pause/unpause to correct it, and then I can re-pause TrackIR and get the H1 pan back (until/unless it glitches again). Not sure if this is buggy from TARGET or something in the script.

Thanks again!!

Edited May 18, 2017 by Rangoon

Cravgar · May 19, 2017

Today's response from TM:
We thank you for your reply.

Under these circumstances then the problem is caused by the latest update you have installed for the OS, the "Creators Update".

We are currently investigating this problem ourselves, analyzing the updates this patch brought to the actual OS and the modifications it made to various sub-systems so that we can determine what might be interfering with the TARGET's normal performance.

For the moment we do not have any additional details to provide you with.

Thanks for the update Sobe.....really wish they would hurry up.

Cravgar · May 19, 2017

Today's response from TM:
We thank you for your reply.

Under these circumstances then the problem is caused by the latest update you have installed for the OS, the "Creators Update".

We are currently investigating this problem ourselves, analyzing the updates this patch brought to the actual OS and the modifications it made to various sub-systems so that we can determine what might be interfering with the TARGET's normal performance.

For the moment we do not have any additional details to provide you with.

Ive just got this working again but reverting the creators update:

To uninstall the Creators Update, go to Start > Settings and click on 'Update & security'. Click the Recovery link and then click on 'Get started' under 'Go back to the previous version of Windows 10.

GL

sobe · May 19, 2017

Cravgar

What problems were you having with the Creator update? It is too late for me to go back so I am stuck with it.

sobe · May 19, 2017

It seems that the only current problem I have with Creator is that it keeps loosing the connection to my TM rudders. This is not so bad as Homefries excludes the rudders from his profiles so it seems to work (the same for BMS). The problem occurs when the rudder is included in the profile.

Sign In

DCS World TARGET profile for TM Cougar and Warthog + MFDs