WIP DCS A-10C and Teamspeak 3 Integration

[WarriorX]

Just reported a bug.

 

I changed the default Radio and Key Settings in the TARS Control Panel. I changed them to Arrow Down, Arrow Right, and Arrow Left.

 

Upon restarting TARS, the previous key assignments are now, Down +1, Right +2, and Left +3.

 

I have to keep changing them back whenever I start TARS.

 

I am running Beta 2 and running TARS as Admin.

[Headspace]

Just reported a bug.

 

I changed the default Radio and Key Settings in the TARS Control Panel. I changed them to Arrow Down, Arrow Right, and Arrow Left.

 

Upon restarting TARS, the previous key assignments are now, Down +1, Right +2, and Left +3.

 

I have to keep changing them back whenever I start TARS.

 

I am running Beta 2 and running TARS as Admin.

Thanks, every time someone uses the correct reporting procedures, TARS gets better. Got the report and it will be fixed in the next beta release. In the meantime, go to the tars.ini file in your Teamspeak 3 folder and clear the second key setting out for each key--that should fix the issue.

[Headspace]

Part of the next beta changelog, should be out this week at some point:

1.0.0b5
- Plugin: Radio keys function as push-to-talk buttons for A-10C.
- Plugin: Fixed an issue that would cause Teamspeak 3 to lock up when it tried to mute players.
- Plugin: Radio frequency display set to rounded Mhz values.
- Control Panel: Key bindings will be properly cleared out if the user selects less than the default number of 
keys.

[Sharkster64]

Just tested out tars with some friends this evening and we all loved it. Really adds to the immersion. The radio effect to our voices sounds awesome too. Sounds just like an actual aviation radio headset.

 

There was one issue I was having. Every now and then, the pluggin stopped working. It was working fine for a while, and then all of a sudden, every ones voices sounded normal again, and they could not hear me. I alt tabbed and saw that teamspeak was not responding. I exited out of teamspeak and restarted teamspeak, and it worked again. This happened a couple of times. Other than that, it worked awesome

[Headspace]

Every now and then, the pluggin stopped working. It was working fine for a while, and then all of a sudden, every ones voices sounded normal again, and they could not hear me. I alt tabbed and saw that teamspeak was not responding.

I believe I've found and nailed this particular issue over the weekend. Please test the new beta when it comes out and let me know if it comes back.

[Steel Jaw]

Which radio has the fartherest range and so would be best for the Guard freq?

[WarriorX]

I have been using the UHF with good results in the range dept. 243.0 to be exact.

[Headspace]

Mower:

 

I had this huge post that either 1) I screwed up and misposted elsewhere or 2) The forum ate.

 

Here's the tl;dr version: Right now, the FM model is still being tuned and will be better tuned once I can get better data on usable FM signal propagation in the frequency band employed. Generally, FM sounds better and can theoretically be heard further than AM, but there's a cutoff point known as the improvement threshhold where the SN ratio drops dramatically and AM tends to gain the advantage there. This is why with FM radio the quality tends to be good throughout most of the usable range and then drops.

 

As of the current TARS, the lowest band on AM has the best usable range. Line of sight is the primary limiter (earth curvature).

 

Edit: I should mention that you can't actually tune down to a seriously low AM freq...so I guess that would mean the FM radio technically has the longest range at this point. Expect this to be tuned (no pun intended) when I redo the sound system in preparation for the new Teamspeak.

Edited January 25, 2011 by Headspace

[Headspace]

I have just released TARS Beta 9. A whole bunch of improvements have been made, and are listed on my site as well as in the changelog included with the file. WarriorX's issue is also fixed, and you now get multiple push to talk buttons in the A-10C. Have fun.

[Steel Jaw]

Awesome news Headspace, we're all over this.

[WarriorX]

Thanks so much Headspace!

[TRoe13]

Thanks HeadSpace, downloading now. Looking forward to using it 2morrow. Woohoo!!

[Furia]

you now get multiple push to talk buttons in the A-10C. Have fun.

 

Hi. First at all THANKS for the awesome MOD.

 

Can you please elaborate more this statement about PPT?

How does this work now?

[Muse]

Thanks Headspace !!!

[Headspace]

I have released a new beta, because Beta 9 had a critical issue affecting Black Shark players (and only Black Shark). Beta 10 fixes the issue. Please note that it is not compatible with Beta 9. Download it here.

[Heater]

Headspace...

 

Thanks for the hard work on this!!

[Cowboy10uk]

Just Installed this, Ok I havnt been able to test it with my wingman yet, Still Waiting for him to get Internet installed after he moved house, But Really looking forward to it, The protential is Hugh.

Done some messing around so now it all seems setup right, and everything is talking to each other.

 

A HUGH thanks to Headspace for taking the time to make this for us all.

 

Cowboy10uk

Edited February 7, 2011 by Cowboy10uk

[Cowboy10uk]

Hi Guys, I was just wondering if anyone knows what causes this issue, I have sent a Bug report to Headspace's site, Although Im not convinced its a bug, more a user error on my part.

 

I have Tars Beta 10 installed along with TS3 and running A10 Beta 4 on Windows 7 64bit.

 

When using my Radios I can hear my Wingman through Tars and it sounds great, When one of us is in specator mode he can hear and not speak, As it should.

 

Now My problem comes when trying to change the radio.

 

At present it seems I can only get Tars to transmit using UHF. However if I change to a different Freq than my wingman on UHF, he can still hear me and transmit as if we are on the same Channel.

 

IF I switch to AM or FM as the selected radio, and he stays on UHF, he can still hear me and transmit. If I try and transmit with only AM or FM radios on, and UHF turned off. He cant hear me.

 

I think the issue must be that I am only Transmitting and recieving on UHF.

Even if I change the selected radio.

 

I hope some can understand what im saying. I am positive this is some sort of user error, I have looked at the instructions over and over again, But I cant see what im doing wrong. I know its going to be something simple that I cant see even though its staring me in the face.

 

As to the freq change not doing anything I have no idea, I see noone else seems to be having this issue, and I have seen it working in Youtube. so It Must be me. :doh:

 

Any ideas guys.

 

Cowboy10uk

 

 

 

UPDATE : OK Im an idiot, after playing round with this a bit more, it clicked what I was doing wrong. I was trying to switch radios with my Warthog mic switch instead of the keys given in TARS. Doohhh.

I knew it was something I Had to be doing wrong. Not had a chance to check the Freq error I was getting, EG Changing Freq on UHF but my wingman could still hear me, Ill test that on Tues when ive finished work.

.

 

Update Update :) : Yep Im a complete Idiot, All works a treat now including frew change, No idea how I screwed that one up. Fingers crossed it works on the final that Ive just downloaded. Damn this really is a stunning peice of software. Thanks Headspace

 

:)

Edited February 22, 2011 by Cowboy10uk
Update

[Furia]

Headspace, any news about when you expect to release the TARS version compatible with the Release version of A-10C?

[VTJS17_Fire]

Hi Headspace,

 

first of all, thanks for this mod/ plug-in. It's awesome. I hope ED will implement such a feature in future DCS modules via VOIP or as you did it.

 

 

Q: If two teams (red and blue) fly the A-10C in multiplayer and both sides are on one TS3 server/ channel and use TARS (same radio/ frequence), can they listen to the foe?

And if this is true, could you implement the function of the KY-58 to encrypt the radio calls?

 

 

kind regards,

VJS-161 Fire

[Headspace]

If two teams (red and blue) fly the A-10C in multiplayer and both sides are on one TS3 server/ channel and use TARS (same radio/ frequence), can they listen to the foe?

And if this is true, could you implement the function of the KY-58 to encrypt the radio calls?

That's almost certainly never going to happen WRT the KY-58. The truth of the matter is that TARS is already beyond the scope of what I'd originally intended for a free product, and has eaten up so much of my time already that it's going to require additional funding if new features are to be added--which means that I will need to revise the original goal of keeping it free. Encryption is way out of scope at this time, with all of my current development efforts being focused on converting out of the old sound system and onto a custom sound system (out of necessity, due to Teamspeak 3).

[Steel Jaw]

Headspace, any news about when you expect to release the TARS version compatible with the Release version of A-10C?

 

There is a workaround courtesy of StrongHarm...

 

 

TARS is doing a version check .. to get around it you can use your old dcs.exe from beta to trick it:

*Go into \dcsa10\bin

*Rename dcs.exe to dcs.release

*Move your old beta4 dcs.exe into bin (if you deleted it, get it HERE).

*Go into TARS and point to \Eagle Dyanmics\DCSA10 as usual

*Check 'Install TARS' within TARS

*(!!IMPORTANT!!)Go back into your \ED\DCSA10\BIN folder and change dcs.exe to dcs.beta

*Change dcs.release to dcs.exe

[Headspace]

There is a workaround courtesy of StrongHarm...

 

 

TARS is doing a version check .. to get around it you can use your old dcs.exe from beta to trick it:

*Go into \dcsa10\bin

*Rename dcs.exe to dcs.release

*Move your old beta4 dcs.exe into bin (if you deleted it, get it HERE).

*Go into TARS and point to \Eagle Dyanmics\DCSA10 as usual

*Check 'Install TARS' within TARS

*(!!IMPORTANT!!)Go back into your \ED\DCSA10\BIN folder and change dcs.exe to dcs.beta

*Change dcs.release to dcs.exe

You could also follow the manual install instructions in the TARS manual. It explains where all the files need to go.

 

It doesn't appear that there is any fundamental change impacting TARS and how it works, but I am in the process of chasing down a few very minor bugs.

Edited February 25, 2011 by Headspace

[Furia]

There is a workaround courtesy of StrongHarm...

 

 

TARS is doing a version check .. to get around it you can use your old dcs.exe from beta to trick it:

*Go into \dcsa10\bin

*Rename dcs.exe to dcs.release

*Move your old beta4 dcs.exe into bin (if you deleted it, get it HERE).

*Go into TARS and point to \Eagle Dyanmics\DCSA10 as usual

*Check 'Install TARS' within TARS

*(!!IMPORTANT!!)Go back into your \ED\DCSA10\BIN folder and change dcs.exe to dcs.beta

*Change dcs.release to dcs.exe

 

 

Most Thanks!!!

Works real fine :thumbup:

[Headspace]

As promised, here is the update. The DLL and lua/luac files are exactly the same, but the control panel is updated and will search for the release version.