All Activity
- Yesterday
-
ReeTired joined the community
-
flex started following AVCS Bug Report - (UNKNOWN / OTHER - See user comments in report)
-
AVCS Bug Report - (UNKNOWN / OTHER - See user comments in report)
flex replied to flex's topic in AVCS Bug Reporting
Excellent! Thank you very much for your speedy feedback. Much appreciated. Indeed I was testing the recognition rate of a few commands, as I am not a native, with VA as focus window. best flex - Last week
-
Basics of Fire and Maneuver
=VG= The_Polish_Guy posted a blog entry in Tactics & Techniques for Arma
Those two words are the foundation of infantry tactics. They can be explained with a short saying. Fire without maneuver is a waste of ammo. Maneuver without fire is a waste of lives. When facing an enemy force, maneuvers can only be made with supporting fire and only by maneuvers can the enemy be decisively defeated. This simple rule has influenced tactical decisions for centuries. Usually the implementation of this rule is carried out by having a Fire Element and a Maneuver Element. Depending on the size of the operation those elements can be anything from section/fire team size to company/battalion size. Example: In this hypothetical scenario two friendly infantry squads face off against an enemy. Both forces have some light cover/concealment helping them defend their positions (marked with approximate black lines). The BLUFOR units are tasked with defeating the enemy unit. Additionally for the purpose of the example, any flanking maneuvers are not possible. The leader of the BLUFOR has a choice. They could send both squads to assault the enemy position and hope the numerical superiority will be enough or select one squad [M] to be the maneuver element and the other [F] to provide fire support. In that case the attack will look like something like this: Both elements or just the fire element will suppress the enemy. Making it impossible for them to reposition or return effective fire. After establishing fire superiority, the maneuver element will move forward with the fire element still suppressing the enemy. After getting to the enemy position the maneuver element will secure it and communicate the fact to the fire element which will move up to the captured position to secure it against a counter attack. The role of fire elements can be fulfilled by a lot of different assets. It can be a weapons/rifle squad, a machinegun crew, artillery or vehicles. What is important to remember is that infantry is always the main force securing a position. Any other assets are to support it. Of course the example above is of a very simplified nature. What is important to take away from it is just the base idea of fire & maneuver. It is the base for everything from small unit movement to large coordinated assaults. That's why understanding it allows achieving a better tactical decision making skills. -
You have VoiceAttack as the application in focus, with the target for text interaction as the profiles list. When you issue this command which presses the "R" key (for Flight), what is happening is the profiles list is recognizing your "R" keypress to jump to and load the first profile that starts with the letter "R". If you instead open a Notepad and place the cursor there, and issue the command, "Flight Go Wedge", you would instead see the letter(s) "R" typed out followed by the number "1" as pictured below: The solution would be to test this while you are actually flying in Falcon BMS and when BMS is the active window, so that virtual keypress macros send keys to this application and NOT to the VoiceAttack application. If you have any other issues, please feel free to let me know!
-
Profile: AVCS4 BMS - Immersive Voice Control Radios Issue: (UNKNOWN / OTHER - See user comments in report) Profile Version: 2.20.0.2308 VoiceAttack Version: 1.16 Steps to reproduce: Expected Behavior: profile worked as expected for quite some time. i now wanted to use first time the command "flight go wedge". for info "element go wedge" and "wingman go wedge" do work as expected; other commands like "report airborne" work as well correctly Observed Behavior: but saying "flight go wedge" this then happened: - Command was recognized as a derived command, -profile unload "init_Main", - profile changed to Ready or Not, exciting AVCS BMS to non AVCS CORE Profile (i do have an own Ready or Not profile - NOT your version), -stopped command "flight go wedge" see attached screenshot Personal Testing: this can be reproduced. I imported again the BMS profile, renamed it and did all the steps in the VA command window but same result. restart PC did not change anything. Comments: Thx for looking into this. best flex Severity / Status: Non-issue View full bug report
-
MOKUM is attending Group Training - Falcon BMS
-
This part is dedicated strictly for Arma 3. As it is a quick manual on how to use TFAR radios. This post will contain: Installing the TS3 plugin Keybinds Radio types Using the radio Changing the frequency Setting an additional channel Installing the TS3 plugin To use TFAR you need to have a TeamSpeak client installed. I will not cover either how to install TS nor how to set it up. The only thing I will say is that for TFAR usage you should use push to talk. It is possible to stick with voice activation but if your audio setup is not perfect it will just annoy everyone around you in-game. To install the TS3 TFAR plugin you simply have to access the TFAR mod folder. The easiest way to do that is through the game launcher. Open the game launcher after subscribing and installing the mod from steam workshop. Launch TeamSpeak. Find Task Force Arrowhead Radio (BETA!!!) in the list of mods. Open the mod’s directory (image below). Go into: \@Task Force Arrowhead Radio (BETA!!!)\teamspeak Open: task_force_radio.ts3_plugin. This will open an installer for the plugin. Go through the installation process. Restart TeamSpeak if it hasn’t done it automatically and you’re good to go. To enable and disable TFAR you can go into Tools>Options>Addons and press disabled/enabled button. Keybinds Before reading through the Keybinds I suggest re-binding a few things to help with TFAR use in-game. Zeus Ping / Zeus Interface: change from “Y” to “2xY” or other more suitable key [ESC>configure>controls>Zeus>Zeus] Vanilla Push To Talk: change from “Caps Lock” to a desired button or unbind completely [ESC>configure>controls>multiplayer>Push To Talk] Push-to-talk button in TeamSpeak Direct Speech. Caps Lock To talk on personal radio. CTRL + Caps Lock To talk on a long range radio. CTRL + P To open the personal radio interface (the radio must be in the inventory slot). CTRL + [/] Cycle through available personal radios. CTRL + Up/Left/Right Arrow Rapid switching of personal radio stereo mode. NUM[1-8] Rapid switching of personal radio channels. ALT + P To open a long range radio interface (a long range radio must be put on your back, or you should be in a vehicle in a position of a driver, shooter, or pilot assistant). If a number of radios are available – you'll be offered to choose one. One of them can be set as active. CTRL + ALT + [/] Cycle through available long range radios. ALT + Up/Left/Right Arrow Rapid switching of long range stereo mode. CTRL + NUM[1-9] Rapid switching of long range radio channels. CTRL + TAB To change the direct speech volume. You can talk: Whispering, Normal or Yelling. Does not affect the signal volume in the radio transmission. CTRL + ] Select next personal radio. CTRL + [ Select previous personal radio. CTRL + ALT + ] Select next long range radio. CTRL + ALT + [ Select previous long range radio. CTRL + [←,↑,→] Change personal radio stereo mode. ALT + [←,↑,→] Change long range radio stereo mode. T Transmit on additional channel of personal radio. Y Transmit on additional channel of long range radio. ESC To exit from the radio interface. Radio types TFAR radios have two main types. Short range (personal) and long range (backpack). Additionally radios can be found integrated into some vehicles. This is mod dependent but they function like any other long range radio. Each radio in TFAR has it’s encryption key. It means that it can connect to only radios with the same encryption key. There are three main encryption keys in TFAR (BLUFOR, INIPENDENT and REDFOR). A common misconception is that short range radios cannot contact with long range and vice versa. That is not the case. As long as the frequency is set properly and both radios are in rage there should be no issues. Below you can see a list of all the radios assigned to their encryption category. (BLUFOR Radios) Radio RF-7800S-TR (rifleman): 30-512Mhz / 2 km Radio AN/PRC-152 (personal): 30-512Mhz / 5 km Radio RT-1523G (ASIP) (long range): 30-87Mhz / 20 km (30 for inbuilt) Radio AN/ARC-210 (airborne): 30-87Mhz / 40 km (INDEPENDENT Radios) Radio AN/PRC-154 (rifleman): 30-512Mhz / 2 km Radio AN/PRC148-JEM(personal): 30-512Mhz / 5 km Radio AN/PRC-155 (long range): 30-87Mhz / 20 km (30 for inbuilt) Radio AN/ARC-164 (airborne): 30-87Mhz / 40 km (REDFOR Radios) Radio PNR-1000A (rifleman): 30-512Mhz / 2 km Radio FADAK (personal): 30-512Mhz / 5 km Radio MR3000 (long range): 30-87Mhz / 20 km (30 for inbuilt) Radio MR6000L (airborne): 30-87Mhz / 40 km Additionally the list contains the base range of each radio. However you have to remember that the range can change depending on the use conditions. Biggest factor besides range is terrain. Hills, buildings or forests might limit the range of a radio. The range can also be influenced by the server addon settings set by the administrator / mission maker. Using the radio Below is a simple guide on what all of the buttons on a radio do. The images below show only the western radios (AN/PRC-152 – shortrange and RT-1523G – long range). RT-1523G Currently selected channel Frequency of the currently selected channel – this is where you input a new frequency Channel selection 1-9 Set frequency – press after inputting a new frequency Set additional channel Increase volume Decrease volume Stereo settings Speakers Clear frequency – clears the current frequency and lets you input a new one AN/PRC-152 Decrease volume (LMB) | Increase volume (RMB) Clear frequency Set frequency Next channel | Previous channel Speakers Set additional channel Stereo settings Changing the frequency Changing the frequency is the most important and the most common operation done on a radio. It’s also a very simple one. To change the frequency: Bring up the radio [ctrl/alt + P] Clear the current frequency by pressing the Clear Frequency button Input the new frequency using your keyboard Press the Set Frequency button Confirm with a radio check and you’re good to go. Remember that the frequency will not be changed from the previous one until you confirm by pressing the Set Frequency button. Setting an additional channel Additional channels are useful when communicating between different asset groups / teams. For example a squad leader will always carry only a short range radio but will have to communicate with the squad or at least section leaders and assets/HQ. For that they should set an additional radio channel. And to do that they have to: Bring up the radio [ctrl/alt + P] Switch to a different channel Input the additional channel frequency Press the Additional Channel button Now the channel marking should change from C2 to A2 or CH:2 to CA:2 signaling that the selected channel is set as additional Switch back to the main channel Now the secondary channel can be used by pressing [T – short range] or [Y – long range]. Additionally stereo settings can be adjusted to make it easier to differentiate between channels
-
=VG= Sphee started following Tactics & Techniques for Arma
-
Communication over radio seems easy enough until there is a lot of information that needs to be relayed. Chaotic comms can lead to misunderstandings and as a result poorer efficiency on the battlefield. For that reason a few ground rules of radio communication help to keep it clear. The most important rule is to only say the important thing and to do it smoothly, quickly and in a way that everyone can understand you (clearly). It helps to take some time before sending a message to organize what you want to say in your mind. To avoid talking over each other it is important to mark when our message is over and what kind of response or lack thereof we expect. So when our message is over but we expect an answer from the receiver we end our message with over. When our message is over but we don’t expect or don’t need a response, we simply end the message with out. Additionally, if we want the receiver to give us some time to respond we simply respond to their question with standby. If we have to stop the transmission but our message isn’t over, we simply end the transmission with break. And then continue after a short period of time. This call can also be used to clearly change the receiver of the communication. Additionally if we have something very important to say and want to make sure the radio chatter stops, we simply start our message with break, break, break and everyone knows to stop talking and listen to the message. The radio discipline described is obviously for the purpose of mil-sim gaming whereas IRL it might sound similar, it is often way more structured. Examples of radio communication: Alpha to HQ, over Alpha this is HQ, transmit, over HQ, Alpha requests medical supplies to grid coordinates 1 8 5 break 0 5 6 numpad 3, how copy over Alpha, HQ, good copy, medical supplies to grid coordinates 1 8 5 break 0 5 6 numpad 3, over Alpha confirms, over Alpha, in 5 mikes supplies will be delivered by helo, mark LZ with green smoke, over Alpha copies, supplies in 5 mikes, marking LZ with yellow smoke, Alpha out In this example Alpha asked HQ to organize a supply run for them. They gave their location, HQ confirmed it to make sure they heard right and told Alpha to mark an LZ which Alpha also confirmed. Anvil actual to Anvil 1-1, come in 1-1 Actual this is 1-1, over 1-1 we’ve got reports of movement around the buildings 100 meters west of your position, break… … move to the north-west to overwatch that area, how copy Actual, 1-1, good copy, moving north-west to overwatch the buildings west, over Break, break, break, Anvil 1-5 to all anvils, contact, bearing 120, distance 500 meters, two T-72s in the open moving left to right, Anvil 1-5 engaging, out This is Anvil Actual, good copy 1-5, break, all anvils reposition to engage targets, bearing 120, distance 500 meters, out Anvil 1-3, two times T-72 destroyed, bearing 130, 1-5 confirm targets destroyed This is 1-5, affirm, targets destroyed, good shooting 1-3, out The acting commander of the unit with codename Anvil was telling one of the sub-units to check out a contact report, but before the communications could be finished, Anvil 1-5 noticed two targets that could threaten friendly forces. Realizing that was the priority target, they stopped other comms and reported the contact using the 3D method. 1-3 was able to destroy the T-72s and double checked with 1-5 to make sure it was the same target and 1-5 responded with a pat on the back. Radio Checks When connecting to a new frequency or starting a mission it is important to check if our radio is working properly. Sometimes the squad leader or some other entity will request a radio check but even if they don't it's worth doing it anyways. Additionally whenever radio comms are not clear or someone is not responding to our call outs it might help to send a radio check and make sure we are indeed being ignored rather than our radio is not working. Radio checks are performed in a number of different ways, but it is important, just like with any other communications over net, to be quick and precise. That's why most use a simple procedure for radio checks. It will start with the person checking their radio saying providing their callsign and frequency they are checking and relay that it is a radio check. The recipient, being anyone on the net will respond with something along the lines of: Good check or my personal favorite: check five out of five. The second message can relay much more information to the person checking the radio. It tells them the connection is as strong as it can be or if the response is for example: two out of five, it is obvious that the signal is disrupted but still somewhat readable. Example: Bravo 2 radio check on 50, over Bravo 2, Bravo 3, five out of five. This of course are simplified prowords. We can also use terminology such as: Loud - very strong signal Good - good signal Weak - weak signal Very weak - very weak signal Fading - At times signal cuts out and Clear - excellent quality Readable - satisfactory quality Unreadable - quality so bad that the message can't be understood Usually you would combine one word from the first list with one from the second to create a message relaying all information needed for a radio check. Radio use in Arma 3 For the guide on using TFAR in Arma check out this post.
-
3D Method
=VG= The_Polish_Guy commented on =VG= The_Polish_Guy's blog entry in Tactics & Techniques for Arma
That's the plan -
You would be lifesaver if you continue this. Many need this kind of knowledge, especially in a game as tactical as arma.
-
3D Method
=VG= The_Polish_Guy commented on =VG= The_Polish_Guy's blog entry in Tactics & Techniques for Arma
Feel free to share everything here or use it in any way when teaching someone. I hope the other topics I have planned will help too. -
Rifat joined the community
-
ADKING started following Another (slightly less) lackluster PR event
-
thanks for the event
-
Another (slightly less) lackluster PR event
=VG= Sphee replied to =VG= Sphee's topic in PR Cooperative
Thank you for attending, it's been a pleasure making these layers (except Al Sbeneh STD made by Zee that I broke), I had fun seeing what new thing I broke and hadn't caught in testing. Apologies for any issues you faced like yet again, slow bot respawn rates, and some maps of questionable quality. Please provide any feedback you have for anything relating to this event in this thread, or DM me personally about it as I'd love to hear what you think. I'll lock this post likely in around 10 days. -
a_tiler joined the community
-
Another (slightly less) lackluster PR event
Cacheiro replied to =VG= Sphee's topic in PR Cooperative
i made it now thanks -
thanks