SRS with TARGET script file in VR

[Dooker]

Hey All,

 

So I'm sort of new to using SRS within DCS in VR. I use a custom target script modified off of the Big LCZ F18 file. I'm confused as to how the PTT and Comm 1 and 2 functions work. I have not altered the Comm 1 "Ralt + " and Comm 2 "Rctrl+" in the script file. How do I get this to work? Is that what the Comm 1 modifier in SRS is for? Along with the Comm 2 modifier? As in for the modifier I put the Ralt and Rctrl and then "" for the applicable Comm 1 and 2 slots? What about PTT? Are the prior just for switching freqs back and forth and PTT once you've done that? I can't seem to make it work and in VR it's extremely frustrating since my mic is in the headset and on top of that having to take it off and on to troubleshoot. I hope I'm being specific and clear. Any help is appreciated.

 

DT

[Lange_666]

Your question is a bit messy for me. Comm 1 and Comm 2 is that in DCS or SRS? Because in SRS controls they are called Radio 1 and Radio 2.

So i assume it's SRS comms.

I would not use keyboard (or the equivilent on your HOTAS) to control SRS radios mainly because when talking, the keyboard function locks out doing other stuff (other controls) at the same time as long as you keep that radio button pressed.

You should set it up with a DX button so it won't interfere with other controls.

PTT (Push To Talk) should only used if you don't have enough buttons on your HOTAS and need to use the keyboard instead for selecting the proper radio. You then have to set up just 1 HOTAS button for PTT and the radio selection is through the keyboard.

If you setup the radio selection on the HOTAS, you don't need that extra PTT button since the selecting the radio will PTT that selected radio at the same time with the same button.

 

Tip: set everything up in 2D before going VR, it makes things a lot easier and prevents you from lifting that headset each time.

[Lange_666]

You can also set the F-18's Comms 1 and 2 switched in a chain command together with the SRS radio's 1 and 2. Then you always have the correct radio selected.

[Frederf]

Since you are using TARGET I recommend a setup like I'm using. There are 4 useful actions when using DCS and SRS on two radios: DCS text menu activate for radio 1, SRS push to talk for radio 1, DCS text menu activate for radio 2, and SRS push to talk for radio 2. As such I make each radio button spit out either a pulse of one button to activate DCS or a long press of another button to speak on SRS.

 

MapKey(&Throttle, CSU, TEMPO(DX1, DX2, 250) );

MapKey(&Throttle, CSD, TEMPO(DX3, DX4, 250) );

 

Then I bind DX1 and DX3 to DCS radios 1 and 2.

Then I bind DX2 and DX4 to SRS radios 1 and 2.

 

I make sure that SRS is configured to not use DCS input to activate radios because I have direct control instead. When in DCS I tap the button less than 250ms to bring up the in-game text-based radio menu or I press and hold greater than 250ms to speak in voice over SRS.

[Dooker]

Since you are using TARGET I recommend a setup like I'm using. There are 4 useful actions when using DCS and SRS on two radios: DCS text menu activate for radio 1, SRS push to talk for radio 1, DCS text menu activate for radio 2, and SRS push to talk for radio 2. As such I make each radio button spit out either a pulse of one button to activate DCS or a long press of another button to speak on SRS.

 

MapKey(&Throttle, CSU, TEMPO(DX1, DX2, 250) );

MapKey(&Throttle, CSD, TEMPO(DX3, DX4, 250) );

 

Then I bind DX1 and DX3 to DCS radios 1 and 2.

Then I bind DX2 and DX4 to SRS radios 1 and 2.

 

I make sure that SRS is configured to not use DCS input to activate radios because I have direct control instead. When in DCS I tap the button less than 250ms to bring up the in-game text-based radio menu or I press and hold greater than 250ms to speak in voice over SRS.

 

Ok, this is along the lines of my question. Sorry to all, I know the way I wrote it is messy. Sort of hard to convey. I am unfamiliar with the DX codes though. How do I assign that in DCS? From my research DX1 and 2 are the slew control button and MSU. I also understand that the Directx functions for controllers is there for instant plug and play without having to assign stuff.

 

https://simhq.com/forum/ubbthreads.p...e_TARGET_.html

 

Your target code I understand, but how DX1-4 (I know it at least goes to 32) etc work I am unclear to. For example do I go into SRS and controls in DCS and just type "DX1" for comm 1 and the same for the others? Or it seems I need to run the script after adding your code to my script file, and then press CSU, CSD (I am going to bind them to MSR and MSL) in the DCS and SRS controls field?

 

 

 

 

 

[Lange_666]

Let's say in the controller setup of the aircraft is an action called Radio_1.

In the macrofile, you can assign a DX button to a macro, like define....Radio_1.....DX10

Then in the script you can write MapKey(&Throttle, MSR, Radio_1);

If you run the script, pressing MSR will output DX10 (instead of a keyboard combo).

In game you setup your controller, look up Radio_1 and bind DX10 to it, click assign and in the HOTAS part and select the correct DX button.

 

 

 

PS: The DX nr can go up to 120 with if you use a modified target.tmh.

You can download that here (rightclick - save as): http://users.telenet.be/lange/download/targetdx128.tmh

[Frederf]

How do I assign that in DCS?

Same as any other controller.

 

From my research DX1 and 2 are the slew control button and MSU.

I only used DX1-4 as an example. Of course it can be anything you want. I don't know what numbers you have in use and which are open to use. Maybe you want TARGET output to be joystick button, keyboard keystroke, or even mouse button. I don't know what your plan is.

I also understand that the Directx functions for controllers is there for instant plug and play without having to assign stuff.

There are default button assignments in DCS, only a few, but I have never made my TARGET script with the goal of not changing DCS settings. First thing, select all, clear category. Start joystick from blank page. It's not worth it to care about maybe 10-20 default assignments.

 

Your target code I understand, but how DX1-4 (I know it at least goes to 32) etc work I am unclear to.

It works the same as when you are not running TARGET or using a controller which doesn't have programming at all. You press plastic button, some number is output from the device. DCS sees this number and says "Ah, when I see this number I must do this action!" If you don't like the association then it is changeable.

 

For example do I go into SRS and controls in DCS and just type "DX1" for comm 1 and the same for the others?

Primary method to set custom controls for DCS and SRS is to put the program into a receptive state. Then the program will take the next input from the controller as the assignment for that action. DCS you double click the rectangle which is the row of the command you want and the column of the controller you want. Then it is receptive to the next input from that controller. SRS is slightly different, there is a "set" button. When "set" and "clear" are gray then it is awaiting input.

 

Or it seems I need to run the script after adding your code to my script file, and then press CSU, CSD (I am going to bind them to MSR and MSL) in the DCS and SRS controls field?

Exactly. Remember MSR and MSL can output four different outputs for only two buttons. Each button is going to output a different command based on hold long you press the button. Make sure to bind DCS to the taps and SRS to the long holds.