ARMA 2 Communications..

**MarineSeaknight** · 09-06-2009 01:47 PM

I stole this from Jeepo. It's great to have working VON again, hooray! Now let's find out what each channel is used for!

DIRECT All grunts should be using this channel for 99% of their communicades. Good within 80m. of a fellow soldier, it doesn't interrupt other chat and also operates on the Effects volume slider, which means it can be tailored to be louder or quieter than radio clutter.

VEHICLE This channel should normally be reserved for communication between the commander, gunner, and driver of a vehicle, and grunts should stay off this channel as much as possible. The only time a cargo troop will need to pay attention to Vehicle chat is when the commander is ordering a disembark, or informing the troops of immediate intelligence.

GROUP This channel is for the squad leader and any fireteam leaders to communicate, and should NOT be the default channel for grunts. Squad leaders can rely on this channel to include everyone he's responsible for in a pinch, and fireteam leaders can use it to communicate between each other when they're out of direct channel range.

SIDE This channel should be reserved for immediate and pressing communications ONLY. It is NOT to be used in the same respect as channel commander, as EVERYONE can hear you. Only use this channel if you need to communicate something EXTREMELY quickly, like imminent danger warnings or close contact reports that need to be conveyed between squads.

COMMAND This channel functions exactly as channel commander does in Teamspeak, so use it for this purpose. Any group leader can listen in on this channel, while grunts get to ignore the barking of orders. Ideal for the commander.

COMMANDER It seems that this is a broadcast-only channel for the 1IC of the mission. Only he can talk over it, and traffic on this channel is only 1-way.

GLOBAL Global is, by default, an ADMIN-ONLY channel. That means NO communication on it, period! There are only a few exceptions, including but not limited to TvT engagements where one side needs to speak "out of context" to the other factions.

It should be noted that VON is an extremely bandwidth-heavy application, and by enabling it we should all be more conscious of what you're transmitting. Just because Direct channel exists doesn't mean you should be SINGING, YELLING, or GOOFING OFF on VON!

**GeneralCarver** · 09-06-2009 03:58 PM

I am GeneralCarver, and I approve this message.

**Ghost02** · 09-06-2009 05:08 PM

I am Ghost and I also approve this message.

**Skin** · 09-06-2009 05:39 PM

I am uncertain whether Command and Commander channels work as described. I've tried to use Commander Channel as the CO however no one was appear to hear me. On command channel, grunts have heard communications on the channel.

That being stated, it will be interesting to see missions that are designed with limited radios in mind

**viper1986** · 09-06-2009 05:59 PM

Blackdog was able to limit radios in ArmA1. Only certain positions could use certain VON channels.

For command channel, on Inq's new mission only squad leaders and certain positions could talk on command channel and hear whats going on... or thats how it seemed.

What needs to be worked on is the use of side channel. No one should be using side channel except for emergency reasons. I believe command chatter is pinned down to the Command channel where the grunts are left out in the chatter. Side channel should be restricted to cases where a SL goes down and the 2IC needs to take his place. The idea is to limit the amount of chatter that flows down to the grunts as it's the job of the SL to keep them informed.

**Sc[ + ]pe** · 09-06-2009 06:04 PM

You stole that from ME, you punk! ; )

**viper1986** · 09-06-2009 09:02 PM

Now that we are in full use of VON, i want to catch everyone up with the procedures with TS now. If your going to be in TS, please jump into one of the Alpha or Bravo channels if your going to be playing a mission. It's very easy and prevents the public channel from getting crowded and non mission talk interrupting with the ingame talk. It already happened tonight when it shouldn't have and it's not at the fault of the sinlge player but EVERYONE who was on server alpha but not in the alpha channel.

Please everyone, think about where you should be in respect to what your doing. Public is good for pre and post mission stuff, but during the mission it should be empty. It's good for getting people organized into what server everyone wants to play on, but should be empty after everything's been sorted out.

**Hund** · 09-06-2009 09:59 PM

Hey,

I see you guys set up voip for arma 2 now (been away for a few weeks, so didn't notice). I can confirm that it does seem to be crashing me for some odd reason - the more trafic there is, the bigger the chance of a cold crash to desktop. That's about as much as I understand the problem so far.

Well, BIS will get around to saving the day eventually, they always do...

**Skin** · 09-06-2009 11:32 PM

commander channel does not work.

**Sc[ + ]pe** · 09-06-2009 11:50 PM

Agreed. There's no reason to be in the Public Lounge when you're in-game. If you get annoyed with someone talking out-of-game on TS, it's your own fault.

**Sc[ + ]pe** · 09-06-2009 11:52 PM

Yes it does, Skin. It seems to work on a per-squad basis, and I can't yet tell if it's designed by player class or squad position, but it certainly appears to be working properly.

**fuzzhead** · 09-07-2009 12:25 AM

I still would like to see the SOP for SIDE channel change..

I still dont see a valid reason to use SIDE over COMMAND channel... "urgent" "immediate" communications can be interpreted as whenever that unit is under fire and needs assistance, which happens frequently. And why cant they use COMMAND channel when its urgent, as it still gets the message across to the relevant party, instead of spamming everyone?

But other than that I agree with this and would love to see this enforced on the server once players adapt again to using VON

**Inkompetent** · 09-07-2009 06:55 AM

Also, for the mission designers, now can be the time to redesign missions so that every fire team is a squad of its own, since we have TS for squad comms, and VON for FT comms?

**Inkompetent** · 09-07-2009 07:09 AM

Originally Posted by Hund

Hey,

I see you guys set up voip for arma 2 now (been away for a few weeks, so didn't notice). I can confirm that it does seem to be crashing me for some odd reason - the more trafic there is, the bigger the chance of a cold crash to desktop. That's about as much as I understand the problem so far.

Well, BIS will get around to saving the day eventually, they always do...

Do you use beta build 58972? If using any earlier beta version, or no beta at all, then you WILL be crashing. If you do use the newest beta, then I think BIS will be really interested in your crash logs.

**Skin** · 09-07-2009 08:51 AM

Originally Posted by Sc[ + ]pe

Yes it does, Skin. It seems to work on a per-squad basis, and I can't yet tell if it's designed by player class or squad position, but it certainly appears to be working properly.

I am speaking about Commander channel (the white text) not Command channel. Every single mission I've played on TG as the CO, I have typed into the channel and now with VON spoken a simple message like "can you see this text?". To date, no one has responded.

If you have figured how to make it work let me know

Thread: ARMA 2 Communications..

Thread Tools

Display

VON Channels and their purpose

Re: VON Channels and their purpose

Re: VON Channels and their purpose

Re: VON Channels and their purpose

Re: VON Channels and their purpose

Re: VON Channels and their purpose

Re: VON Channels and their purpose

Re: ARMA 2 Communications..

Re: ARMA 2 Communications..

Re: VON Channels and their purpose

Re: ARMA 2 Communications..

Re: VON Channels and their purpose

Re: VON Channels and their purpose

Re: ARMA 2 Communications..

Re: ARMA 2 Communications..

Thread Information

Users Browsing this Thread

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions