So squad leaders and the commander have the 117F. A squad leader dies. The team can to command simply by switching to a different channel if they are not in range. Do we give fire team leaders a back up 117F each so they can assume command or do make them recover the radio from their former leaders hideous corpse?
I'd also suggest that the commander use the last channel on his 343 by default (channel 16?) so that people can reach him on that in an emergency if they're close enough.
Radio Contingencies
Re: Radio Contingencies
It would be good to have some sort of Radio split, but that's just not happening. We only use 343 and everybody is on Channel 1 there. I definitely recommend 148 (midrange) for FTLs and SLs. It is a pain to communicate with only 343s when we have 3 Fireteams but all over the place. This costs valuable time (in the form of the SL having to catch up to his men and even then he's only guaranteed to reach half of them with he 343) and forces the SL to be on the frontline when he should be commanding instead.
Also better splitting for 343, more situational. Example from last session below:
A1 + A2 assault Cache 1 = 343 Radio Channel 1, FTLs 148 Channel 1.
A3 + MMG assault Cache 2 = 343 Radio Channel 2, FTLs 148 Channel 1.
This would allow for decent communication between assigned teams and yet allow people to call in support from MMG if it's needed via 148. A 148 is absolutely enough as we're kinda almost always within 1-2km of eachother.
Also to get back onto 343 / Squad Level = Not always. In the example above we had clear teams and using split 343s would have been much more efficient, allowing for teams that were SUPPOSED to stay together to communicate more effectively, avoiding the clusterfuck that happens when everybody is on 1 channel. If there are limited numbers such as only 2 Fireteams then it's fine to be on 148 channel 1 or 343 channel 1 depending on range. However if we're on 148 channel 1 each Fireteam may aswell occupy their own 343 channel.
Also better splitting for 343, more situational. Example from last session below:
A1 + A2 assault Cache 1 = 343 Radio Channel 1, FTLs 148 Channel 1.
A3 + MMG assault Cache 2 = 343 Radio Channel 2, FTLs 148 Channel 1.
This would allow for decent communication between assigned teams and yet allow people to call in support from MMG if it's needed via 148. A 148 is absolutely enough as we're kinda almost always within 1-2km of eachother.
Also to get back onto 343 / Squad Level = Not always. In the example above we had clear teams and using split 343s would have been much more efficient, allowing for teams that were SUPPOSED to stay together to communicate more effectively, avoiding the clusterfuck that happens when everybody is on 1 channel. If there are limited numbers such as only 2 Fireteams then it's fine to be on 148 channel 1 or 343 channel 1 depending on range. However if we're on 148 channel 1 each Fireteam may aswell occupy their own 343 channel.
Re: Radio Contingencies
I think a lot of the issues we've had were caused by people refusing to adapt to a new method of handling comms (and trying to find a direct equivalent to the vanilla system). Admittedly, the 343's lack of capability on maps like Podagorsk was pretty annoying, and it wasn't something I was expecting, due to a lack of experience with the map. I still don't believe that 148s are needed for SL/FTL communication, but it's something that we can try next session, for a few missions.
However, assuming we get to larger player counts, for example, multiple squads, we will return to the squad-level 343 approach. Admittedly, the "148s for FTL/SL" method may be something that's needed for smaller player counts, due to the necessity of splitting squads further than would normally be needed with larger player counts, and isn't something I'd previously considered, but for anything larger than 1 squad + attachments that methodology tends to cause a massive delay in orders being passed down the chain of command.
Regardless, appreciate the comments/suggestions.
However, assuming we get to larger player counts, for example, multiple squads, we will return to the squad-level 343 approach. Admittedly, the "148s for FTL/SL" method may be something that's needed for smaller player counts, due to the necessity of splitting squads further than would normally be needed with larger player counts, and isn't something I'd previously considered, but for anything larger than 1 squad + attachments that methodology tends to cause a massive delay in orders being passed down the chain of command.
Regardless, appreciate the comments/suggestions.
Re: Radio Contingencies
The problem with 1 channel 343 is range. If we go back to the first mission where I was CO it was impossible to hear me as I was staying back, and we all had 1 343 channel. This forced me to go directly to the front line, and even then I could not hear Alpha 2 who were on the other side of town. I also got shot as I was forced to be kinda directly next to Alpha 2 and close to Alpha 1. That's the main reason why I support 148s for FTLs and SLs. FTLs can brief their guys in their own 343.
Re: Radio Contingencies
Pretty sure that wasn't due to range, it was due to ACRE's calculation of signal loss with mountains and dense forests. I've seen 343's go up to about 1 km without issue on maps like Taki.
Re: Radio Contingencies
This is not Vanilla, if you don't like ACRE then Vanilla+ is not for you.
That said, I think it's largely a communication problem. I've watched the United Operations tutorial, read the wiki, tried all the radios on my own in the editor. I don't think everyone wants to put in that kind of time.
So I have two suggestions. Firstly; we need to include radio protocol and a short how to in the mission notes. It needs to cover the standard communication hierarchy, how to use ACRE as a grunt or FTL and how to use it if you're an SL and up. Secondly; we might need to do a monthly workshop to test tactics, techniques and educate anyone who wants to be.. Ferrard's workshop style would be something to aim for.
About the the radio hierarchy:
FTs don't usually need to communicate via radio. The whole point is that they stay together. I think that we can assume that in general direct channel is the most useful for FTs.
We then use 343s for inter-fireteam comms. This let's the FTLs and SLs quickly communicate without having to change channel.
For intersquad comms I suggest we use the 117F and not the 148. The 117F is overkill but it does completely remove range problems from most situations. Whatever we use, we need still need to consider what FTLs who've lost their SL will do when they need to communicate with their commander, even to just confirm that his SL just bit the dirt.
That said, I think it's largely a communication problem. I've watched the United Operations tutorial, read the wiki, tried all the radios on my own in the editor. I don't think everyone wants to put in that kind of time.
So I have two suggestions. Firstly; we need to include radio protocol and a short how to in the mission notes. It needs to cover the standard communication hierarchy, how to use ACRE as a grunt or FTL and how to use it if you're an SL and up. Secondly; we might need to do a monthly workshop to test tactics, techniques and educate anyone who wants to be.. Ferrard's workshop style would be something to aim for.
About the the radio hierarchy:
FTs don't usually need to communicate via radio. The whole point is that they stay together. I think that we can assume that in general direct channel is the most useful for FTs.
We then use 343s for inter-fireteam comms. This let's the FTLs and SLs quickly communicate without having to change channel.
For intersquad comms I suggest we use the 117F and not the 148. The 117F is overkill but it does completely remove range problems from most situations. Whatever we use, we need still need to consider what FTLs who've lost their SL will do when they need to communicate with their commander, even to just confirm that his SL just bit the dirt.
Re: Radio Contingencies
feanix wrote:This is not Vanilla, if you don't like ACRE then Vanilla+ is not for you.
That said, I think it's largely a communication problem. I've watched the United Operations tutorial, read the wiki, tried all the radios on my own in the editor. I don't think everyone wants to put in that kind of time. (If someone took the time to watch my tutorial videos or any of the other you can grasp the radios in about 20min)
So I have two suggestions. Firstly; we need to include radio protocol and a short how to in the mission notes. It needs to cover the standard communication hierarchy, how to use ACRE as a grunt or FTL and how to use it if you're an SL and up. Secondly; we might need to do a monthly workshop to test tactics, techniques and educate anyone who wants to be.. Ferrard's workshop style would be something to aim for.
( Would be enough if folks stick to the pretty standard ME, \YOUWHOIWANTTOTALKTO\)
example:
ASL,Alpha 1 move to alpha 1 marker and be ready to move SOUTH EAST
Alpha 1, ASL copy that, moving to alpha 1 marker
About the the radio hierarchy:
FTs don't usually need to communicate via radio. The whole point is that they stay together. I think that we can assume that in general direct channel is the most useful for FTs. (Yes)
We then use 343s for inter-fireteam comms. This let's the FTLs and SLs quickly communicate without having to change channel.
(Agreed if we had more squads)
Better to just roll with 148's for FT until we have enough squads
For intersquad comms I suggest we use the 117F and not the 148. The 117F is overkill but it does completely remove range problems from most situations. Whatever we use, we need still need to consider what FTLs who've lost their SL will do when they need to communicate with their commander, even to just confirm that his SL just bit the dirt.
Last edited by head on Sun Apr 07, 2013 3:10 pm, edited 1 time in total.
Re: Radio Contingencies
In conclusion, to those of you who want a quick summary, we're going to have FTLs and SLs carry 148s, and have each fire-team on a separate radio, up until we reach enough players to warrant two squads, at which point we'll move into the system explained in the V+: ACRE sticky.
