T.A.R.S, is hard to recognize my directx input programmed in my warthog profile

[Pegaso69]

I've problem during the recognition by TARS about the directx buttons that I have assigned to my Warthog in the Mic switch, up, forward and back.

I've programmed, all possibile 32 directx input, because it is preferable to use the directx rather than keyboard input (fewer conflicts, fewer problems with directx). For example, I 've use DX 14, 15 and 16 - AM, UHF, FM.

I and others pilots of my squadron, we prefer not to use voice activation, (We think it is unrealistic, use the voice activation) therefore, we must keep the button pressed, and in this case it is preferable to use directX input.

But when I launch my profile to my warthog and I try to recognize these the directx input about the Mic Switch, the TARS has some problems in recognizing these directx. The profile work better, i've test it on the with appropriate utility of the TARGET GUI management.

but the TARS configuration panel recognizes well two of directx, but the third is difficult to recognize (at the end, I can do it recognize but it's really hard and boring).

The problem is that I would share my profile with other users (around the world) and I dont want that this users have this issue about recognition.

If instead it will use the default keyboard input (eg: CTRL + 1, + 2 or + 3), the recognition is immediate, but I would like to use the buttons directx

(fewer conflicts), although these are held down.

 

I could work around this problem by send my config file of the TARS, to the other users, who want use my warthog profile with diretcx

(I go crazy once for all, and they will have the profile TARS, using my configuration file TARS, that I will send them)

 

In which file is written to the TARS commands programmed?

 

Can i share my TARS config file with the other users, and prevent their go mad to configure the TARS. They can use my TARS config file preprogrammed from me?

 

Thank you

[july865]

imo i believe the WH needs to have all switches in their neutral positions. so when you program the stick, it will recognize the button you are assigning.

i am not at my computer to find out what switches need to be set, but you can check your stick in windows "device" setting to find out where they need to be.

i had not issues setting up my WH with TARS. but i did have to use a modifier when i wanted to use the in-game comms.

[nomdeplume]

I could be wrong here (edit: I am wrong here, skip this post!) since I've yet to actually participate in a flight that uses it, but from the configuration setup I got the impression that there are two separate activities here:

 

1- TARS needs hotkeys or buttons to tell it which radio is in use;

2- A press-to-talk button in TeamSpeak is used to talk, if you don't use voice activation.

 

The TARS buttons are therefore just things you press once. In my case, I've configured it to use the HOTAS Mic switch in the appropriate directions, and modified the game's configuration to require a modifier (the "pinky switch" on the stick) in order to use the in-game radio. My PTT button in TS3 is the "Mic switch in", which is otherwise unused.

 

So my belief of how this will work is that I'll need to first press the appropriate mic switch once in order to tell TARS which radio I'm now transmitting on.

 

Then, when I want to speak, I'll need to press the Mic switch in so as to activate the TS3 push-to-talk. TARS will then magically add some information about the frequency I'm on, and then other TARS-users will only hear me if they happen to have a radio tuned to that same frequency.

 

I won't need to press the Mic switch again until I want to communicate using a different radio. And, pressing/holding the Mic switch in the forward/back/down position won't let me speak on TeamSpeak - it only tells TARS which radio is now active.

 

That's my understanding, but please enlighten me if I'm wrong about any of this.

Edited March 14, 2012 by nomdeplume

[airdog]

I could be wrong here since I've yet to actually participate in a flight that uses it, but from the configuration setup I got the impression that there are two separate activities here:

 

1- TARS needs hotkeys or buttons to tell it which radio is in use;

2- A press-to-talk button in TeamSpeak is used to talk, if you don't use voice activation.

 

The TARS buttons are therefore just things you press once. In my case, I've configured it to use the HOTAS Mic switch in the appropriate directions, and modified the game's configuration to require a modifier (the "pinky switch" on the stick) in order to use the in-game radio. My PTT button in TS3 is the "Mic switch in", which is otherwise unused.

 

So my belief of how this will work is that I'll need to first press the appropriate mic switch once in order to tell TARS which radio I'm now transmitting on.

 

Then, when I want to speak, I'll need to press the Mic switch in so as to activate the TS3 push-to-talk. TARS will then magically add some information about the frequency I'm on, and then other TARS-users will only hear me if they happen to have a radio tuned to that same frequency.

 

I won't need to press the Mic switch again until I want to communicate using a different radio. And, pressing/holding the Mic switch in the forward/back/down position won't let me speak on TeamSpeak - it only tells TARS which radio is now active.

 

That's my understanding, but please enlighten me if I'm wrong about any of this.

Nope....TARS will transmit over the correct radio in TS3 by holding the button, provided you mapped it correctly in the TARS control panel. If i hold mic switch forward it xmits over VHF am...mic switch down xmits over UHF...mic switch aft xmits over VHF FM. I also use the pinky switch as a modifier to get to the ingame menus but this is mapped within DCS. I cleared all the mic switch commands within DCS so that TARS/TS3 is priority on my WH Hotas mic switch and like I said above ingame menus now require the pinky switch as the modifier and then the mic switch to select the correct radio.

I love TARS...its about as realistic as you can get.. Thank You Headspace for an awesome program!!!!

[nomdeplume]

Nope....TARS will transmit over the correct radio in TS3 by holding the button, provided you mapped it correctly in the TARS control panel.

Oh, that's interesting. So TARS itself also provides a push-to-talk function on whatever buttons you configured in TARS? Does that mean if you're not using "regular" TeamSpeak, you don't need a PTT button mapped within TeamSpeak at all? (Not that I'll do that, but just theoretically speaking.)

[july865]

@nom

that is correct.

since he is using a WH. all buttons need to be off to program it in TS also. not sure if it has to be that way in TARS

[ralfidude]

Has anyone noticed that TARS will not work if you switch the common VHF FM frequency? For example, i we can set some random AM frequency for all flight leads to be on, and have custom UHF freq to use between wingman, but the second you flip the FM to some other channel to let's say talk to JTAC, TARS no longer works, you will not be able to hear or transmit to anyone over the AM and UHF frequencies. It's the oddest thing...

[Eddie]

Has anyone noticed that TARS will not work if you switch the common VHF FM frequency? For example, i we can set some random AM frequency for all flight leads to be on, and have custom UHF freq to use between wingman, but the second you flip the FM to some other channel to let's say talk to JTAC, TARS no longer works, you will not be able to hear or transmit to anyone over the AM and UHF frequencies. It's the oddest thing...

 

Nope, never had any such issue.

[Eddie]

Oh, that's interesting. So TARS itself also provides a push-to-talk function on whatever buttons you configured in TARS?

 

Yes.

 

Does that mean if you're not using "regular" TeamSpeak, you don't need a PTT button mapped within TeamSpeak at all? (Not that I'll do that, but just theoretically speaking.)

 

It does.

[Pegaso69]

Thank you to all for the reply but probably because of my poor English have not understood what I mean ... anyway ... i try again, sorry for this long post but i need to explain me better.

 

First, I'm not new im an old programmer, with the Cougar (from about 9 years) I always planned my own profiles with Foxy and macro, now I use the Warthog and the TARGET Scrypt

The problem is NOT created from the warthog profile, the profile work very fine I've teste it with the appropriate procedure (Device Analyzer and event Tester including in the TARGET software).

The problem is in the configuration panel of TARS, in the recognition phase of the buttons.

In my squadron we use the TARS for several months, we are not new for this and we do NOT use the voice activation because we believe that this is unreal, we use the PUSH TO TALK mode.

 

I programmed the Mic's Warthog in this way:

 

With S4 In (pinky switch lever pressed) =

S4 In + Mic forward = Virtual VHF AM radio menu (single player)

S4 In + Mic down = Virtual UHF radio menu (single player)

S4 In + Mic back = Virtual VHF FM radio menu (single player)

 

With S4 Out (pinky switch lever not pressed)

Mic Switch forward = Directx 14 (Hold)

Mic swithc down = Directx 15 (Hold)

Mic Switch back = Directx 16 (Hold)

 

HOLD, Because We use PUSH to TALK in TS, we DONT use voice activation.

We think that voice activation it is real for STAR WARS only at the moment :-D

And this is the reason why I used the commands directx, rather than keyboard commands (like Ctrl + 1, etc. or other), because sending a continuous input directx does not conflict with Windows, whereas a continuous sending of keyboard commands could create problems in windows. And we need to keep the button pressed as long as we want to talk.

 

The problem is in the configuration panel of TARS, when I try to recognize the various buttons to talk the various radio, even if this is an operation that is done only once (una tantum) is still a tedious and time step, and since I would like share my profile with other pilots on the web, I would not want these pilots have problems at this stage, and why I wanted to know where TARS save the configuration of the keys, so I can attach the file button configuration of TARS together with the profile file of the Warthog.

I swear once for all, in the setting phase of the buttons.

 

The problem it's in the config panel TARS, eg: when I click the SET button at the UHF and appears gray window that should recognize the button or input that is pressed or sent, the TARS has a difficult to recognize the directx input that I've programmed in my profile in Mic Switch (forward, down and back), recognizes two buttons with great difficulty and the third does not even recognize, only after swearing in various languages at the end will recognize also the third directx.

But, as I said before I would share my profile with other drivers and I do not want to have these problems at this stage of setting (although this is done only once, una tantum), I want everything to go smoothly, then I would send them also my configuration about the file buttons of the TARS.... but I do not know which is the file where TARS writes these blessed parameters.

I've try to open the file TARS.ini (in the DEPLOY directory) but I dont think that it's the correct file, because I try to set other parameters and keys but the file never change.

 

In this jpg you can see better my prob

 

Now... after all this talk... a simple question:

Anyone know what is the file where the TARS writes the parameters of the settings of the buttons?

 

Thanx

Edited March 14, 2012 by Pegaso69

[Pegaso69]

Ok... In partially i've solved my problem.

i've find the file where TARS write his button configuration.

Tars write in the file named TARS.ini, but exist two files with this name.

1 - One it's on the main directory of TARS (not correct)

(Programs Files x86 \ TARS \ deploy)

2 - the other TARS.ini file it's in the configuration directory of TeamSpeak

TARS write the configuration in the TARS.ini on the directory about TeamSpeak... this is the correct file where the TARS writes the buttons