All Activity

Hello Operators. Here is a guide on how to install and verify your ACRE installation 1. Subscribe to the ACRE mod on the steam workshop | Link 2. Open the ArmA 3 Launcher, Load ACRE2 and it's dependancies. Alternatively you can load the BigD Operation Mod Preset. Once completed, launch the game. 3. When launching ArmA 3 with ACRE for the first time, you will get the notification that the ACRE plugin has been installed. This is an automatic installation, if you do not get this prompt; you either have ACRE already installed or it has failed. You can verify with the later steps of this guide to see if it is installed correctly. 4. You now need to verify if the ACRE plugin is installed correctly in your TeamSpeak 3 client. Open TeamSpeak 3, select 'Tools' from the toolbar and select 'Options' 5. Select the 'Addons' menu option. 6. Now on the right hand side, you should see your installed plugins. You can verify that ACRE is installed and enabled if it's entry appears in this list and says 'Enabled' as shown. You can also verify if the plugin is loaded by checking your user status on the right hand side after selecting your name in the connected TeamSpeak 3 client. This will say 'Arma Connected: Yes' when in game. . If you have installed ACRE, for additional troubleshooting, please log a ticket in the BigD Discord for ArmA 3.

Hello Everyone. Here is a basic guide on how to utilise TeamSpeak for ArmA 3. Communications is such an important aspect to any successful operation. TeamSpeak gives us a modifiable and immersive way of expanding our methods of communication in game using mods such as ACRE and TFAR. The guide below will demonstrate how to install TeamSpeak 3 for use in BigD ArmA 3 operations! 1. Open a web browser and navigate to teamspeak.com/en/downloads/ 2. Select the TeamSpeak 3 Tab 3. Download the x64 version for Windows. 4. After download and installation is completed, now it time to connect to the BigD TeamSpeak. You can do this by clicking "Connections" then "Connect" (Alternatively you can press Ctrl+S). 5. At the connection screen, You'll be prompted with what shows below. The BigD TeamSpeak server does not have a password, so all you need to do is enter the server address as shown below, and your own Nickname in the Nickname field. Once completed, hit connect. (TeamSpeak will remember the last entered server details in this window.) 6. Success! You've connected to the BigD TeamSpeak! -----------------------------------Additional Information------------------------------------ For Ease of Use, you can also setup bookmarks for your servers. You can add the BigD Server to your bookmarks quickly by clicking the "bookmarks" tab. Selecting "Add to Bookmarks" This will bring up your Bookmark window. On the right hand side, review the information. This will all be the same information listed when you first connected to the server. When finished, click "Apply" The server will now appear in your bookmarks list for quick connection!

Our BigD Gaming Squad Tournament is ready to kick off this weekend! We are thrilled to have 7 teams prepared to battle for the coveted title of the best Squad! Our teams are composed of members from affiliate clans, public players, and a mix of various clans. We are also having our friends from ZSU coming and joining in the fun too! Starting this weekend, the first round of games will launch us into 4 weeks of intense action and tactical game play. The teams have been training hard, and we can’t wait to see them in action! If you didn’t make it into a team but still want to enjoy the tournament, TraumaStoo will be streaming all the matches on Twitch with a slight delay. He will be joined by the fantastic Azza and Badger for some exciting commentary, bringing all the action right to your living room! https://www.twitch.tv/traumastoo https://www.twitch.tv/azzagamespc https://www.twitch.tv/anobesebadger123 ttps://www.bigd.com.au/clubs/6-only-clans/ https://www.bigd.com.au/clubs/18-taiwan-cloud-leopard-squad-tcls/ https://www.bigd.com.au/clubs/11-grim-reapers/ https://www.bigd.com.au/clubs/14-the-vanguards/ https://www.bigd.com.au/clubs/1-laughs-and-games/ https://www.bigd.com.au/clubs/13-phuc-clan-gaming/

Hi Everyone! Operation Name: Operation Northern Storm Date Run: 05/05/2024 Players in Attendance: 11 Squad Performance: Leadership team are very impressed with how the squad operated inside of mission, kept things tight and everyone performed well together. Recon: Given the scope of the mission, some extra time to scope out tasks and objectives pre-assault would have made a couple of things more smoothly. Senior Admins with take this on further with more detailed mission planning in the brief, prior to the operation. Delay with mission step off: We had a slight issue with a number of people joining late, which delayed step off time. If we can try to join at connection time so we are ready to go by step off to keep making sure the night is smooth. We are aware that we are only a couple of ops in and are still getting into the swing of things and that sometimes there are other factors such as technical issues or a delayed briefing that can cause delays as well. In-game debrief: While we would typically be able to do this one in-game to give us more of an immersive feel as well as getting it all out as we go, due to a couple of technical issues, we were unable to have that happen as intended. We are still investigating if it is linked to the performance hick ups that we had during operation of if it is something seperate. Have anything else to share? You can have your say HERE Otherwise, see you in the next one!

Hi Everyone! Operation Name: Operation Backhand Date Run: 19/04/2024 Players in Attendance: 14 First Operation: Our first official operation for BigD! Very exciting for us Senior Admins as a couple of months of back end work has led to this point. We had a pretty good turn out for what I expected, being new to operations in BigD it does take a few steps before we can start running but all in all I am personally happy with everyone who turned up, showed support and had a good night. So a deep hearted thank you from us to all who attended to make the night happen. These kind of things wouldn't happen without you guys! The Civilians: Starting with something a little light hearted, we fortunately are aware of what was causing the issue as the script that was causing the civilian vehicle traffic specifically was running 1x per client without an interface. That being the server and three headless clients. So when the server asked for 1x vehicle to be spawned, it spawned 4x. While comical, we do understand that this could have had quite a negative aspect to the mission as the civilians stopping in combat zones and their wonderful driving ability to ram into ALPHA's vehicles on their way to objective leading to a few casualties over the course of the night. There were attempts to fix it during mission, but this was unsuccessful. However the issue has since been resolved going forward. Coordination and Communications Being our first operation, I do believe a lot of these issues will be fixed with time and experience, but they are still worth bringing up now so we can all have a think. Firstly, a reminder to Platoon Leaders, Squad Leaders and Fireteam Leaders that the players likely lack significant Arma Operation experience, let alone tactical/milsim knowledge. It's crucial for them to provide exceptionally clear and precise directions in light of this to ensure that orders and directives are clear to all receiving and can be successfully passed down the chain. A few things we noticed in this regard: There was no established leadership hierarchy (e.g., if the SL is incapacitated, FTL Blue should assume command). Convoy briefing lacked a defined order of march; only general instructions were given for Blue team to take point. (Just a small note on this, convoys is something that even the most experienced MILSIM groups can struggle with so don't feel like this is a unique issue to us) Issues such as enemy contact during movement were not addressed. This is somewhat important to the cohesion of the squad, as if a fireteam member doesn't report contact then not only are the rest of the fireteam not able to react to it, but the Squad Leader is unable to reorg the squad into combating the threat if needed. A secondary issue, is if members don't report contact and are taken out by them, then you may be facing the respawn screen instead of quickly being picked up. Contact reports don't need to be anything too crazy, just mainly on squad net "Contact - Infantry/Vehicle/Etc - Direction or Compass" While teams were assigned positions by the SL, specific arcs and designated areas for observation were not clearly communicated by FTLs, resulting in suboptimal coverage. This wasn't a huge issue due to the enemy force and the terrain, but without covering arcs of fire, the squad/s are at risk of being outflanked by hostile forces. Have anything else to share? You can have your say HERE Otherwise, see you in the next one!