Mumble: Difference between revisions

Line 49:

In the Setting screen Configure>Settings you can find Advanced settings checkbox in the bottom left corner. With it checked you can access the Messages settings. From there you can disable popup and sound notifications about events you don't care about.

== Key Bindings for Fleetchannels ==

~~Check the channel descriptions in-game for current instructions.~~

~~Feel free~~ to ~~write~~ them up ~~here~~.

One of the great advantages of Mumble over Teamspeak is the ability for squad members and their SC to talk amongst themselves, without clogging up comms for the rest of the fleet. This can be invaluable for baitsquads and instructing new members. In order for this to work however, it requires people to be in the right channel and everyone should have their keys set up correctly. This part of the Mumble setup guide focuses on setting up your key shortcuts for the structured fleet channels. To start, you go to Configure -> Settings -> Shortcuts.

[[File:Mumble3.png]]

There you will see this screen (sans the whisper keys, because we are going to set them up for you now!). Press the Add button in the bottom of the screen.

After you’ve clicked Add, a new empty key setup appears. For Function, choose Whisper. After you chose Whisper, click on the empty field under Data and click the (…) button. We’ll first set up the key that enables squad members to talk to their squad commander.

[[File:Mumble1.png]]

First, click Whisper (or Shout if you’ve got the RC2 version) to Channel at the top. Next, choose Parent and check Whisper to subchannels. What this does is it sends a message to your SC and your squad members, to call out points for example. Be aware that this message is not relayed directly to the rest of the fleet! This means you can chatter with your squad without cluttering up fleet comms, but it also means your information will not be available to the rest of the commanders or the whole fleet directly! Especially SC’s need to be aware of this as they need to relay important information to command.

Click OK and set a key binding by clicking the empty field under Shortcut. Next, add a another key. This key will be for commanders to talk to their subordinates. This enables bait squad SC’s to coordinate with their squad without confusing the rest of the fleet and it lets WC’s talk to just their wing members.

[[File:Mumble2.png]]

Again, set the Function field to Whisper and click the (…) key. Click Whisper to Channel, select Current and check Whisper to subchannels. Be aware that giving orders by using this key does not transmit your message to other commanders in the same or higher level. So when an SC talks using this key, he needs to communicate his actions separately with the rest of the commanders. But, being the good SC he is, he should have been doing that from the start anyway. There is one big note that should be made when using this setup, however. Setting up your keys like this makes sure information is only streamed to those that need to know. On the other hand, SC’s are required to be a lot more active in relaying information to the rest of command. This information then needs to be relayed by the FC to the rest of the fleet, if he deems it important for the rest of the fleet to know it also.

In short, the structured fleet channels enable great streamlining and filtering of information. This way, fleet commanders can focus on leading the fleet rather than having to process endless streams of information and squad members and their commanders can coordinate more efficiently amongst themselves. On the other hand, all this requires a great deal more communication and discretion in doing so from SC’s to the rest of command.

One last note: when you are in one of the command positions, you can just use your push-to-talk key to address commanders directly. In this sense, Mumble is set up backwards from Teamspeak as you now need a separate key to talk to the fleet instead of to command.

== Overlay ==

@@ Line 49: / Line 49: @@
 In the Setting screen Configure&gt;Settings you can find Advanced settings checkbox in the bottom left corner. With it checked you can access the Messages settings. From there you can disable popup and sound notifications about events you don't care about.
-== Key Bindings for Fleetchannels ==
+== Key Bindings for Fleetchannels  ==
-Check the channel descriptions in-game for current instructions.
-Feel free to write them up here.
+One of the great advantages of Mumble over Teamspeak is the ability for squad members and their SC to talk amongst themselves, without clogging up comms for the rest of the fleet. This can be invaluable for baitsquads and instructing new members. In order for this to work however, it requires people to be in the right channel and everyone should have their keys set up correctly. This part of the Mumble setup guide focuses on setting up your key shortcuts for the structured fleet channels. To start, you go to Configure -&gt; Settings -&gt; Shortcuts.
+[[File:Mumble3.png]]
+There you will see this screen (sans the whisper keys, because we are going to set them up for you now!). Press the Add button in the bottom of the screen.
+After you’ve clicked Add, a new empty key setup appears. For Function, choose Whisper. After you chose Whisper, click on the empty field under Data and click the (…) button. We’ll first set up the key that enables squad members to talk to their squad commander.
+[[File:Mumble1.png]]
+First, click Whisper (or Shout if you’ve got the RC2 version) to Channel at the top. Next, choose Parent and check Whisper to subchannels. What this does is it sends a message to your SC and your squad members, to call out points for example. Be aware that this message is not relayed directly to the rest of the fleet! This means you can chatter with your squad without cluttering up fleet comms, but it also means your information will not be available to the rest of the commanders or the whole fleet directly! Especially SC’s need to be aware of this as they need to relay important information to command.
+Click OK and set a key binding by clicking the empty field under Shortcut. Next, add a another key. This key will be for commanders to talk to their subordinates. This enables bait squad SC’s to coordinate with their squad without confusing the rest of the fleet and it lets WC’s talk to just their wing members.
+[[File:Mumble2.png]]
+Again, set the Function field to Whisper and click the (…) key. Click Whisper to Channel, select Current and check Whisper to subchannels. Be aware that giving orders by using this key does not transmit your message to other commanders in the same or higher level. So when an SC talks using this key, he needs to communicate his actions separately with the rest of the commanders. But, being the good SC he is, he should have been doing that from the start anyway. There is one big note that should be made when using this setup, however. Setting up your keys like this makes sure information is only streamed to those that need to know. On the other hand, SC’s are required to be a lot more active in relaying information to the rest of command. This information then needs to be relayed by the FC to the rest of the fleet, if he deems it important for the rest of the fleet to know it also.
+In short, the structured fleet channels enable great streamlining and filtering of information. This way, fleet commanders can focus on leading the fleet rather than having to process endless streams of information and squad members and their commanders can coordinate more efficiently amongst themselves. On the other hand, all this requires a great deal more communication and discretion in doing so from SC’s to the rest of command.
+One last note: when you are in one of the command positions, you can just use your push-to-talk key to address commanders directly. In this sense, Mumble is set up backwards from Teamspeak as you now need a separate key to talk to the fleet instead of to command.
 == Overlay ==