Colsta

Everyone is forced PTT on the TFAR channel. It's not a problem, it's a necessity, because people aren't responsible enough to use voice activation properly. Therefore, all you need to do is set a PTT. You're forced to use it in the channel. I really don't see the issue. All you need to do is use the key. You don't need to change anything.

Yes, you're correct. I misunderstood you, and it was an error on the channel. It's all fixed now.

Hello.
 
We bring you this poll to learn what maps the players prefer to play on in AWE.
We ask you take two minutes of your time to reply so we can get a better idea of where to go with the server.
 
https://docs.google.com/forms/d/1WZyA0uwkcWCSa07-xbQAcz3eMP8x7hdaNij8ojxhoYQ/
 
Thank you.

I've read in many places Ryzen is more of a competitor for Intel's video editing processors. I'm sure an i5 or i7 would suffice. But if you have the money, go for it. That said, don't get an i3.

No Problem. But still thanks also for your help!

Yes, you're correct. I misunderstood you, and it was an error on the channel. It's all fixed now.

You'll never see yourself as locally muted. It only transmits when the blue icon lights up. I don't see the problem.

With the last repo update for EU3 AWE, we had 16 GB of updated stuff thrown at us.
 
How A3Sync works is that it checks for folder names, so when it can't find the one from the repo server in your Arma directory, it is blind to everything else, even if it's just a tiny revision. So if you had ACE 3.6.0.0, then 3.6.1.0 comes along and changes a couple PBOs, the rest should be unaffected and the download would be a few MB at most to replace just those. But if the version number were in the folder name, A3Sync would look for @ACE_3.6.1.0, but only find @ACE_3.6.0.0, ignore it and proceed to download the entire mod again.
 
That's mildly annoying for small mods such as ACE, but absolutely infuriating in the case of RHS or CUP.
 
If you know about this, you can rename the mods in question yourself, but most players will either not be aware of it or do not comprehend the procedure. It's tedious as, if you mix up your dashes and your underscores, you'll have achieved nothing.
My proposal thus is to rename all mods with version numbers or otherwise variable names on the repo server itself. @CUP_Terrains_Core-1.3.0, for example, will then become @CUP_Terrains_Core. @ProjectOPFOR was re-downloaded because it now has an underscore in it, so if things like that remained consistent from now on, we could save a bit of traffic.
All future repo downloads of this week's magnitude would be cut down by gigabytes with a quick global change.
 
That's not to say to go out of your way to do so now. Perhaps just bear it in mind for the next update cycle.
 
Cheers.

It isn't because players don't make it so or don't care. I personally care a lot about radio protocol. But this discussion's for another time.

Read and I approve. Something that we may see as rather trivial on first glance may actually be meaningful to others, so in that respect I'm happy to put it to a vote, as long as you reserve the right to veto it.

Hi folks,
 
So it turns out that many of you don't like the new TS Tags, and that's fair.  This is a classic case of starting with a small task (fix the AWE moderator tag) that snowballed into a larger task (design something that makes sense across all the icons) and exploded into a big thing (create a whole new theme).
 
And it was done in isolation, assuming that it was such a small thing that no one would care or perhaps even notice.  Boy was I wrong!
 
So, here's how I'd like to go forward from here:
 
1) We'll go back to the older tags for now.
2) I'd like to start a design competition where everyone can submit their concepts for what new tags could be, with an actual prize.
3) When people have made submissions, we'd submit them to a vote, in addition to the current legacy tags.
4) If a new set of tags is chosen by majority vote, that person would win the actual prize. If the old legacy tags are chosen, then a random person who submitted tags will win.
 
and in general, any changes to all aspects of the site, no matter how small, will be conducted with consultation. I appreciate that you people care about how we do things here, and if you didn't, it wouldn't be the great place that it is.
 
Discussion in this thread, thanks!
 
Details of the competition to follow, we will reserve the right to veto a design (No Boaty McBoatface!)
 
- R

Best term I can use is:
 
R.I.P.
AhoyWorld
We've Had A Few Good
Years,
But It's Over Now

Scar, you cannot possibly expect any Admin to tell a player to leave a vehicle because you simply called dibs on it. Whoever gets the vehicle first means it is theirs. You might forget but the side missions arent designed specifically for you.
 
EU1 is a public server, you should expect people to not have any awareness (you've mentioned stuff like this before on many occasions) and take any vehicle they see regardless of whether you did the side mission all by yourself. 

Thanks for the reply @Colsta, made a correction to my message above with what I meant by the servers.
 
In any case, I'm slowly coming to the conclusion that playing heavily modded Arma online may be beyond my capability and the time I have available to put into learning all the intricacies of solving bugs, connection issues, running .bat files, allocating memory, etc.
 
Have received great help from everyone here and much appreciate that!

For anyone who's wondering, you sign up here for the first session.
 

Ambassadors XML is up and running http://armasquads.com/user/squads/xml/JCEilpdzl8SFhnUspe9KdiIhFas7eMll/squad.xml
 
Let me see what we can do
 

#ModsLikeSquadTagsToo

#ModsLikeSquadTagsToo

I think the most useful thing you can do with an entrenchment tool is either make a foxhole or if the need arises, a cover wall that can be used as a stable firing platform.
 
Other than that, leave em, if you're building these fortifications you spend too much time being on the back foot and not enough time moving up and taking the fight to the enemy, if people get around to using more formations, bounding, pincer and flank style maneuvers, you won't find the need to sit on a hill for 30 minutes shooting at enemies at distance.
 
I can think of many things that are most likely not being used, go ahead and get creative, you'll find it more fun and probably more useful than just using an entrenchment tool to build Fort Knox. 

Did somebody say AWE?

Did somebody say AWE?

For anyone who's wondering, you sign up here for the first session.
 

Problem is, often if a tank crew holds fire, or waits for explicit permission, whatever they're seeing might start shooting at them.
 
It's far less cut-and-dried than an aerial vehicle which can bug out fairly quickly if it sees a threat to itself.
 
If you have armor in the field, expect to use it extensively, or expect to lose it quickly.
 
Incidentally, this is also why I dislike using it outside of specifically tailored missions.

Weeeeeeeeeell, it IS in the AWE subforum........ : D

In testing, the faulty model is the BRM-1K. I'm removing it from the list of OPFOR units for the time being.  I've also posted the bug report on RHS's issue tracker.