regiment / platoon / group leaders / soldiers

[cocar0]

hi teamspeak developers,

since games like battlefield and desertcombat and BF2 quite cool u need to organise ure fighters. this of course would workout for big BF clans up to 20 people and more.

you should build up something like channels in witch the regiment leaders can talk to eachother or to there platoon leaders. the platoon leaders can then comunicate with either there regiment leader or with his sargeants.

the sargeants then talk with there soldiers as group leader. itf communication like in real life.

since if u got more then 5-10 people in a channel it gets quite chaotic for me.
so we could organise our battle... :-)

greetings colin

[Peter]

This is already possible. Put all your different groups (leader + soldiers) in subchannels, make the group leader be a channel commander (red light), make all leaders assign a button to whisper to channel commanders. Now if the leaders talk using voice activation or their normal ptt key, only their group will hear what they say, if they press their special whisper to channel commanders button, only all group leaders will hear what is said.

[PantsMan]

OK, that's all well and good if you only have a single extra "layer" of interaction required ("soldiers" and "commanders" if you will), but in the online flight simulation community (ATC in particular) there are occasions when it would be very useful to have multiple side channels available.

An example; If I am controlling an Approach/Departure facility, I (potentially) need to be able to coordinate with the Ground controller to give out flightplan clearances, Tower for departure authorisation and for hand-offs of arriving and departing aircraft, and an "upstream" Center controller for hand-offs of arriving and departing aircraft to my airfield.

Currently, this is all done using text chat channels in our ATC simulator software, but if we could do all this in TS side channels (one side channel for the airfield, and a second side channel for center/radar and approach/departure controllers) it would make the entire process so much quicker and easier for everyone involved.

[PantsMan]

Currently, this is all done using text chat channels in our ATC simulator software...
Thinking a little sideways about this, assuming it's possible to run multiple instances of TS2 client, it might be possible to use two (or three) TS2 clients to get side channels in the current client.

Unfortunately, I'm at work ATM so I can't have a play with my mate's TS server to see if this is even possible...

[PantsMan]

...it might be possible to use two (or three) TS2 clients to get side channels in the current client...
Except that doesn't work... I can only get one instance of the client to run at a time.

[cocar0]

thanks pwk.linuxfan for ure answer, gona test it soon.

greez colin

[RG_Lunatic]

OK, that's all well and good if you only have a single extra "layer" of interaction required ("soldiers" and "commanders" if you will), but in the online flight simulation community (ATC in particular) there are occasions when it would be very useful to have multiple side channels available.

An example; If I am controlling an Approach/Departure facility, I (potentially) need to be able to coordinate with the Ground controller to give out flightplan clearances, Tower for departure authorisation and for hand-offs of arriving and departing aircraft, and an "upstream" Center controller for hand-offs of arriving and departing aircraft to my airfield.

Currently, this is all done using text chat channels in our ATC simulator software, but if we could do all this in TS side channels (one side channel for the airfield, and a second side channel for center/radar and approach/departure controllers) it would make the entire process so much quicker and easier for everyone involved.

Pants, I think you can do everything you wish under the current system. There are two ways this can be done.

Method 1:

Setup your channels something like this....

Command (Airmarshal and Comms officer) {channel}
Black Group {channel}
...flight1 (4-16 players) {sub-channel}
...flight2 (4-16 players) {etc...}
...flight3 (4-16 players)
...etc...
Blue Group
...flight1 (4-16 players)
...flight2 (4-16 players)
...flight3 (4-16 players)
...etc...
Red Group
...flight1 (4-16 players)
...flight2 (4-16 players)
...flight3 (4-16 players)
...etc...
Green Group
...flight1 (4-16 players)
...flight2 (4-16 players)
...flight3 (4-16 players)
...etc...
Etc......

You can now use the channel commander feature to easily create that first layer as described by pwk.linuxfan. One key can be made to talk to all channel commanders on the server, another to talk only to channel commanders within a certain "channel family", such as the Red Group and all it's sub-channels.

Alternatively you can use the "whisper player list" to assign keys to speak directly to specific players or groups of players. Using this feature, you can make your hiearchy as deep as you like. You can have a hotkey that directly talks to a specific unit commander, or to all unit commanders, or to sub-groupings of unit commanders. Or if you like, you can use non-generic naming for the sub-channels (shown above is "generic"), by giving each sub-channel a unique name such as "Red_Flight1" for the Red channel flight1 sub-channel, which will allow you to assign whispers that go directly to all members of that sub-channel. I prefer generic because it allows fewer keys to be used to provide moving capability (see http://forum.goteamspeak.com/showthread.php?t=21146 for a description of why).

Method 2:

Create a set of "move" hotkeys to facilitate players moving between channels. As described in http://forum.goteamspeak.com/showthread.php?t=21146, 81 subchannels can be negotiated with 18 hotkeys (user first moves to a channel, then to a generically named subchannel within that channel). When the players arrive at the Airfield, they must know to move from their operational channel to a staging channel and await orders, which would include a new channel assignment. This is actually more historically correct/realistic, it is like everyone tuning to a new radio channel to listen for orders.

For this kind of operations, you'd probably want to use a numbered system something like:

100
..101
..102
..etc...
200
..201
..202
etc...

And assign the hotkeys somethinig like:

<right ctrl + numpad1> = move to channel 100
<right shift + numpad1> = move to subchannel x01 (within the current channel).
<right shift + numpad2> = move to subchannel x02 (within the current channel).
....etc...

Players would then movet to an assigned "frequency" to await orders and a new operational frequency.

Also, your command personel can physically move players between channels (if the server is setup to allow it - normally this is limited to SA's at the server level, CA's at the channel level). If the server is properly setup for it (or the commanders are all SA's), they can just move the players to the desired channels by drag and drop via the TS interface. Often it is easier to just move the players than to direct their movement (but it might require two commanders to faclitiate this, one in-game and one at the desktop).

Hope this helps,

=S=

Lunatic

[PantsMan]

Pants, I think you can do everything you wish under the current system. There are two ways this can be done.

<SNIP>

Hope this helps,

=S=

Lunatic
Wow, thanks for the very precise (and long) answer Lunatic. I'm not sure that either of those would be applicable (although I'm prepared to give it a try...) with the way our network is currently working. Perhaps I should have been far more precise in my first post.

Given the world-wide nature of our community, we have TS servers around the world (f.e. gb.ts.domain.com, cn.ts.domain.com, ca.ts.domain.com and so on...). ATC create channels at the 'root' level of a chosen server (f.e. gb.ts.domain.com/EGLL_GND, de2.ts.domain.com/EGLL_TWR, fr.ts.domain.com/EGLL_APP) and the choice of server is entirely in the hands of the individual controller (although we controllers in the GB division are asked to congregate on one server if possible, as that makes it easier for the pilots). The pilot client software gets the ATC channel string from the first line of the controller's ATIS (which is generated by our controller software) and automatically switches TS server/channel as required.

Given that whispers can only work across a single server, there is no easy way to operate as you suggest, hence the request for side-channels (or whispers across networks, if you will).

But, you'd then run into the "monitoring what voice traffic is on channel A for everyone on channel B" that you have currently with whispering; i.e. avoiding walloping someone else's conversation... The more I think this through, the harder it becomes...

[m&m's]

till ts can seperate the sounds to the right channel and the left channel wisper mode will never be worth a darn . what ts needs to do is make it so if your hot keyed to a channel you can hear whats being said in your left ear and hear whats being said in your channel in the right , this way you can hear and respond and wate to talk when wispering into a diferant channel . or at least bind the wispers to the right speaker / headset and it cuts off your normal channel sound and lets the wisper in the right . the latter would most likey be the way to do it . so you dont have to worry about eass dropers sitting back hearing whats going on in your private conversations .

[PantsMan]

till ts can seperate the sounds to the right channel and the left channel wisper mode will never be worth a darn<SNIP>.
Now there's a suggestion that would never have occured to me, and it makes perfect sense.

I'll second m&m's suggestion since it fixes the flaw in my own request. How to do it is going to be an interesting puzzle (obvious way would be have the server process the two sound streams... another can of worms gets opened...)