WIP DCS A-10C and Teamspeak 3 Integration

[Laud]

"You must spread some..."

 

;)

[Laud]

Every time one of our pilots switches to anther radio he will state "push forward, mid, or aft).

 

Is that "mid, aft, forward" A-10 specific phraseology or common air force? Just asking because we currently use the "push box 1,2,3" calls.

 

Sry for half OT...

[VTJS17_Fire]

The phantom pilot in our squadron explained it: "push 34.5" an so on. In some specific frequencies, they call "push christmas" for "push 241.2".

 

kind regards,

Fire

[Kaiza]

It differs a little amongst air forces and squadrons. As stated reference to specific boxes is normally used during formation frequency changes, so that the formation knows what box to change:

 

eg "Hawg flight: Uniform 251.3, go." pause for everyone to change "Hawg flight check uniform" "2" "3" "4".

 

or "Eagle flight: push stud 3 comm1" (stud is a preset)

 

Sometimes when contacting someone who is using multiple freqs the same as you, you may use reference to the radio you are using to avoid confusion. This is not normally needed as it should be obvious what freq you are talking on, but if there is the potential for someone to call back using the incorrect freq you can use things such as:

 

eg. "2 from 1 on uniform, you forgot to remove your pitot cover" "2, roger"

 

freqs will be designated names as well such as "interplane" for a flight common freq. This is commonly used also:

 

eg. "2 from 1 on interplane, i need to RTB asap, Ive code browned this cockpit."

Edited November 11, 2011 by Kaiza

[Snoopy]

Is that "mid, aft, forward" A-10 specific phraseology or common air force? Just asking because we currently use the "push box 1,2,3" calls.

 

Sry for half OT...

 

 

 

It depends, sometimes they may say "push 140.0 fwd" if they are already on he same channel they will just say "push fwd"

[Eddie]

Is that "mid, aft, forward" A-10 specific phraseology or common air force? Just asking because we currently use the "push box 1,2,3" calls.

 

Sry for half OT...

 

In my experience it varies between aircraft types, the obvious reason it that different airframes have different radio configurations.

 

Most fighters, for example, only have two. In the harrier for example they say push left or right. On Typhoon it's just push one or two, because both radios are UHF, VHF/AM and FM combined systems and are all controlled digitally. For the Hog FWD, MID, AFT makes perfect sense, and as Paul says is how it's done IRL.

 

Also from what I've been told by the pilots I've quizzed, it's pretty much unheard of for pilots to actually announce a fequency over comms (ie "push 150 V) when in combat. Much like the way radios are used on the ground, aircrew will have lists/tables of frequncies relevant to their mission/area of operations and code names are used for specific frequencies, in additon to pre-sets for common frequencies. For example, AWACS might instruct a flight to contact a JTAC on "TAC 36". TAC 36 would be the code for a specific radio frequency listed in their kneeboard tables. By doing this, nobody who shouldn't know can follow a flight around the radio network over unsecure comms, and it's also easier to remember a code word spoken over the radio while doing other things than a series of numbers.

 

As for TARS and having the option to chose which radio runs over which sound channel, imho even if the Hog doesn't work that way it's a great function to have. Just beause it's not 100% accurate doesn't mean it's not a good idea, they just never got round to adding the function to the Hog.

[Laud]

Thank you all for your great input on the topic! Will put the results into our squadrons procedures.

 

~S!~

[Stuka]

FYI guys. If you do a full reinstall of version 1.1.1.0, you have to manually create the "Temp" folder in the root of the DCS A-10C folder.

It's not created by default it seems, and TARS is not working without it.

Had me puzzled for a few hours yesterday to help a squadmate out.

Edited November 12, 2011 by Stuka

[Snoopy]

Thanks Stuka!

[Headspace]

FYI guys. If you do a full reinstall of version 1.1.1.0, you have to manually create the "Temp" folder in the root of the DCS A-10C folder.

It's not created by default it seems, and TARS is not working without it.

Had me puzzled for a few hours yesterday to help a squadmate out.

This is getting moved to a user-local folder.

[dikkeduif]

thanks! looking forward to the new version

[VTJS17_Fire]

How is the status of the new TARS version, Headspace? Can't wait anymore. :helpsmilie:

 

 

kind regards,

Fire

[BIGNEWY]

Would love to try this out, will the next release be compatible with TS3 3.0.1 ?

[Laud]

Geez, I hope ED plans to give the FC3 aircraft and the JTAC a TARS compatible radio system!!!

[Timmay]

@BIGNEWY

 

The last Info I got from Headspace was that he wanted to make the program TS 3.0.1. compatible.

 

I wasn't able to get TARS installed, it didn't recognize the TS Client.

 

I wrote an E-Mail and he answered very quickly with the info standing above and an individual way to install TARS anyway.

 

If you got problems installing TARS with the latest Client-Version, feel free to ask!

 

Greetz

 

Tim

[BIGNEWY]

@BIGNEWY

 

The last Info I got from Headspace was that he wanted to make the program TS 3.0.1. compatible.

 

I wasn't able to get TARS installed, it didn't recognize the TS Client.

 

I wrote an E-Mail and he answered very quickly with the info standing above and an individual way to install TARS anyway.

 

If you got problems installing TARS with the latest Client-Version, feel free to ask!

 

Greetz

 

Tim

 

 

just noticed ts3 3.0.2 has been released

 

http://teamspeak.com/?page=downloads

 

hope they do implement it, would be great to have this much depth of realism

[LostOblivion]

Does TS really change plugin interfaces that fast that TARS will simply not work with newer releases of TS? It's kinda weird...

[Timmay]

TARS DOES work with the newer versions of the TS Client, but the installer will not recognize the TS version.

 

You have to manually put some files in the corresponding folders.

 

I did it and it works like a charm. But it is a pain in the *ss if you don't know where to put the files. :cry:

 

But when it finally works, you can be proud!

 

Tim

[VTJS17_Fire]

You have to manually put some files in the corresponding folders.

 

So, please tell us, how you did it. :music_whistling:

Thanks in advance.

 

 

kind regards,

Fire

[Timmay]

I will, but I am at work right now.

As soon as I get home, I will post it here.

 

Einen schönen Tag noch! :D

[Headspace]

The process is documented in the manual that everyone has--the one that gets installed with TARS. If you have TARS you already have the instructions. The issue is with the config program not recognizing versions of TS3 it doesn't "know." Future versions will recognize unknown ones, but say they're unknown.

 

Move the plugin (the DLL in the tars deploy folder) to the Teamspeak 3 plugins folder.

 

Edit: Instructions are also at http://www.excessiveheadspace.com/tars/user-manual/advanced/

Edited November 18, 2011 by Headspace

[Timmay]

Thank you Headspace.

 

I m not home till 2100. So you all can take a look into the manual.

 

Greetz

 

Tim

[VTJS17_Fire]

Thanks. I'll try it tomorrow.

 

 

kind regards,

Fire

[Headspace]

I created a new version. Don't forget to update to Teamspeak 3.0.2 before you test it. Please submit bugs you find through the TARS website bug tool. Thanks!

[Laud]

Great Headspace! TY!