TARS

[Peter22]

Hi guys is tars working with the last 1111 version?

Thanks

Peter

[Eddie]

Yes.

[Peter22]

Yes.

can you tell me what IP host should we use in the net location?

really appreciate any help :(

[Eddie]

?

 

Unless you are using running DCS and TS on separate systems, nothing at all. That setting is only used if you use a laptop for TS and Desktop for DCS, for example. if both are running on the same machine just install as per the instructions and away you go.

[Peter22]

so by default it should work fine? I am trying right now with two more players....once in Copit with pause release we dont her each others...then we power on batteries with APU ect ..UHF 225.00 on ....usin LFT ctrol to communicate but we cant hear at each others....? any suggestion?

[Peter22]

the TS should be installed in tn 32bit or 64?

[Peter22]

TARS version is 101 beta 11 and TS 302?

Need some help here?

[Eddie]

When you click on your name in TS, what frequncies does the TARS info say the radios are running? Try for each player to ensure you are all on the correct frequency.

 

By default the radio PTT buttons are LControl+1 for UHF, LControl+2 for VHF/AM and LControl+3 for VHF/FM. Make sure TS shows you transmitting as normal when you press either PTT.

[airdog]

Make sure that TARS and DCS are running in administrator privlege mode. After you use the LCTRL(whatever) to select your radio you will then use your regular PTT switch to speak to eachother. That is provided that you are both on the same frequency. Also make sure in the tars control click on the A10 picture make sure that standby is unchecked. Also make sure in Teamspeak that you have the TARS plugin selected in the settings>plugins window. Thats what I can think of right now. If its still not going after all that let us know whats up

[Eddie]

After you use the LCTRL(whatever) to select your radio you will then use your regular PTT switch to speak to eachother.

 

The above is a common misunderstanding, but is not actually the case. While it 'can' be used this way, the TARS key mappings are indeed individual PTTs for each radio and are the only PTTs you need while flying.

[Peter22]

The above is a common misunderstanding, but is not actually the case. While it 'can' be used this way, the TARS key mappings are indeed individual PTTs for each radio and are the only PTTs you need while flying.

 

i also have this tars_x64.dll in red on the plugins ..on the right side it says Plugin failed to load:

Api version is not compatible

 

any idea

[Peter22]

tars screen view

 

here is a screen shot of how I have the tars....

[airdog]

Peter I would download the TS3 x64 client from here and uninstall/reinstall TS3. I am thinking that you may have the 32bit version of TS3 installed. Your other choice is to install the tars_32.dll plugin in place of the 64 plugin and see if it works. One thing to remeber is when you check the Tars plugin in the TS3 menu close TS3 and reopen it then check to see if its active.

[Peter22]

Peter I would download the TS3 x64 client from here and uninstall/reinstall TS3. I am thinking that you may have the 32bit version of TS3 installed. Your other choice is to install the tars_32.dll plugin in place of the 64 plugin and see if it works. One thing to remeber is when you check the Tars plugin in the TS3 menu close TS3 and reopen it then check to see if its active.

 

 

""Your other choice is to install the tars_32.dll plugin in place of the 64 plugin and see if it works"" How I do this?...Once we release pause in multiplayer we are not able to hear each others which is normal, but then after setting and trying different frequency in UHF 255.00/ or 251.00 ( with APU and batteries power on) there is not communication at all ..we all have same version 3.0.2 TS and 1.0.1b11 of Tars..... doesnt wor...:cry:

Thanks

Peter

[airdog]

""Your other choice is to install the tars_32.dll plugin in place of the 64 plugin and see if it works"" How I do this?...Once we release pause in multiplayer we are not able to hear each others which is normal, but then after setting and trying different frequency in UHF 255.00/ or 251.00 ( with APU and batteries power on) there is not communication at all ..we all have same version 3.0.2 TS and 1.0.1b11 of Tars..... doesnt wor...:cry:

Thanks

Peter

I'm pretty sure its in the readme that came with TARS. I'm at work right now so its tough to give you exact direction on this. But I think if you look in your TARS folder there should be a plugin folder that has the tars_32.dll plugin, just copy and paste it to your TS3 plugin folder. Make sure to remove or rename the tars_64.dll that is in the TS3 plugin folder to make sure there is no conflicts. Make sure you do not have TS3 running when you do this. Now give it a try and see how it works. Would be a lot easier if you have someone that has a known working TARS/TS3 setup to test with also. I'll be home about 4 hours from now. Make a post here and we can hook up if you like. We'll work out the details then if this is what you want to do.

[Peter22]

I'm pretty sure its in the readme that came with TARS. I'm at work right now so its tough to give you exact direction on this. But I think if you look in your TARS folder there should be a plugin folder that has the tars_32.dll plugin, just copy and paste it to your TS3 plugin folder. Make sure to remove or rename the tars_64.dll that is in the TS3 plugin folder to make sure there is no conflicts. Make sure you do not have TS3 running when you do this. Now give it a try and see how it works. Would be a lot easier if you have someone that has a known working TARS/TS3 setup to test with also. I'll be home about 4 hours from now. Make a post here and we can hook up if you like. We'll work out the details then if this is what you want to do.

Sure ..I ll be back around 1 pm ET if that is convenient for you...we should get on TS so we can test better.....just let me know

Really appreciate that...

[airdog]

I'll PM you the team speak info when I get home

[Peter22]

Thanks

[airdog]

PM sent

[Headspace]

The API version error has absolutely nothing to do with the 32/64 bit assembly. Your version of Teamspeak 3 is quite likely older and incompatible with the current TARS. Upgrade to the latest version and try then.

[airdog]

I got him all straightened out this morning it was that he was not running Tars/TS3 and DCS in administrator mode.

And THANK YOU for TARS its an absolutely awesome program!

[Peter22]

The API version error has absolutely nothing to do with the 32/64 bit assembly. Your version of Teamspeak 3 is quite likely older and incompatible with the current TARS. Upgrade to the latest version and try then.

Oh Yea..Airdog just got me in to the right spot......it was administrator permissions for everything that have to do with A10 DCS....so in case that anyone is experiencing problems by not being able to communicate with tars...just right click to TS/TARS/and DCS exe....go to properties/compatibilities/ and check run as administrator.....that was all.....Tars is absolutely a very good program....

Thank you guys .

Peter

[Heli Shed]

The above is a common misunderstanding, but is not actually the case. While it 'can' be used this way, the TARS key mappings are indeed individual PTTs for each radio and are the only PTTs you need while flying.

 

er..........................no they're not ed, not in my experience anyway.

 

After selecting which radio becomes the 'working radio' by the use of LCtrl & 1,2 or 3, the PTT mapped to HOTAS for teamspeak remains extant for the chosen net. The LCTRL system is nothing more than a software version of a Remote Combining Unit (but not line) for 3 radios.

 

TARS works for us and interoperability with KA-50's is also fine. However, FM radio in the A-10c when tuned to the radio frequency presets of the R828 in the KA50, does not work for some reason, despite manual selection of the frequncy in Radio 3 and despite FM selection in the KA-50 and VHF 1 being selected on the SPU. However, VHF 1, when tuned, does work for internal comms between KA-50's on the same channel.

 

Thoughts?

[Eddie]

er..........................no they're not ed, not in my experience anyway.

 

After selecting which radio becomes the 'working radio' by the use of LCtrl & 1,2 or 3, the PTT mapped to HOTAS for teamspeak remains extant for the chosen net. The LCTRL system is nothing more than a software version of a Remote Combining Unit (but not line) for 3 radios.

 

TARS works for us and interoperability with KA-50's is also fine. However, FM radio in the A-10c when tuned to the radio frequency presets of the R828 in the KA50, does not work for some reason, despite manual selection of the frequncy in Radio 3 and despite FM selection in the KA-50 and VHF 1 being selected on the SPU. However, VHF 1, when tuned, does work for internal comms between KA-50's on the same channel.

 

Thoughts?

 

Tyger, I use it exactly as I described every day. The only time I use my 'normal' TS3 PTT is when not in the cockpit. Yes the normal TS3 PTT will still work, and as I said you can use the LCTRL+1 etc keys just to switch radios, however that is not the best way to use them.

 

As I and other have said in the past, if you map LCTRL+1,2,3 to the WH comm switch, you can use the proper comm switch press to transmit over the relevant radio.

 

Honestly, I can't see how those of you not doing this manage your radios when you're doing multi-flight ops. ;)

 

Not sure about the KA-50 comm issue. I've used the VHF-1 in the Hokum a few times to talk to the hogs while flying AFAC. Although I have customised the R-828 frequencies to match our standard presets in the Hog.

Edited January 23, 2012 by Eddie

[Headspace]

Tyger I can look into the KA-50 problem if you provide both TARS logs from each client. As for the multiple-PTT issue, it works both ways all of the time. It is set up that way so that people can use a single PTT button if they want.